karma0

Member Since: January 11, 2012

Country: United States

  • If you're using Arch Linux, I can confirm that I got it working using the drivers and instructions here: https://github.com/juliagoda/CH341SER

  • Some issues:

    • +1 @Dave21 with the updating extra permissions. I wound up just changing permissions on all Python files with find $AMB_ROOT -iname '*.py' -exec chmod 755 {} \;.
    • There's duplicate information about downloading the board project from GitHub in both the Adding SparkFun Edge Support section and the 3rd paragraph in the Example Applications section.
    • There's no information on the 921600 baud rate that we apparently should be using (if we ordered our boards from SparkFun and didn't receive them at some Tensorflow promo event).
    • There's no information about updating the baud rate in the examples and accompanying code. I did a global grep/sed replace in Bash. Did that break things? Couldn't tell you.
    • The GitHub repo is referenced as SparkFun_Edge_BSP, and later incorrectly as SparkFun_Edge_AmbiqSDK_BSP.
    • The file paths in the Housekeeping section are a mix of relative and (incorrectly) absolute while none are described as being relative to $AMB_ROOT, which makes things very confusing. Further, there are other relative paths throughout the document that confuse the reader, leading a person to believe that they should be in example1_edge_test instead of example1_edge_test/gcc while running make for example.
    • Under the Download the SDK section, the Ambiq SDK 2.0.0 is referencing both, an invalid link and a valid link, each referencing different builds of the same version of the SDK.
    • It's mentioned that on *nix systems, the TTY device will be /dev/cu* and Mac would be /dev/tty.*. Mac is /dev/cu.* and *nix would be /dev/tty*.
    • There doesn't seem to be much of a reason to be using version Ambiq SDK release 2.0.0. Once this issue is resolved, this document should be updated.
    • Under the Introduction section, the link "How to install FTDI Drivers" is irrelevant. This uses the CH340C board and its corresponding drivers.

    Further, I'm still having issues getting these examples to work. Any help is appreciated.

    UPDATE: Issue resolved. Seems the CH341 drivers may need to be updated.

  • After following the hookup guide, this device streams out seemingly random numbers when I put it in listen mode, even with the device in the dark. This happens no matter which firmware I use.

    Copying and pasting the numbers after an attempt to record a remote command, the IR LED is outputting something, but it definitely isn't the same thing that my remote is putting out.

    Help?

  • No matter what you do for encrypting all your traffic, you're still stuck with trusting the provider and their ISP. I personally use SSH tunnels (with autossh) as socks 5 proxies, which can be a bit more configurable and dependable on these devices, and easier than implementing SSL. Additionally, for DNS, I use DNS SEC, which tunnels your DNS requests over a secure channel to a remote provider. The challenge then becomes having a server to route the SOCKS5 connections and to act as DNS cache. Having a proxy and cache setup on your LAN with the free tier on AWS can help with all of this, and it's not likely that AWS is looking to sell information on "surfing" type traffic.

  • Is it safe to assume that this uses I2C or SPI for configuration and sensor output? Also, what are the other pin headers that don't have connectors pre-soldered in the image? (DEN, AG, INT2, AG, INT1, M, etc.)

  • I am new to programming with an FTDI BOB, what do I set 'board' to in my development environment?

  • Is it possible to get a schematic? I have a number of these that went bad when I bought a batch of cables from Spark Fun with several mis-wired connectors (red and black were swapped). I was thinking initially that it was the 555 timers that went bad, but now I'm not so sure.

No public wish lists :(