Sparkfun Edge bootloader problems

Finally the sparkfun board edge boards arrived today

Following this well written guide : 3 i am stuck with the following NoResponseError when trying to flash the code on the Ambiq, with the uart_wired_update.pyscript, that comes with tensorflow examples

[Official DGCustomerFirst Survey

MOJ/Connecting with Corvette over serial port /dev/cu.usbserial-1430…

Sending Hello.

No response for command 0x00000000

Traceback (most recent call last):

File “tensorflow/lite/experimental/micro/tools/make/downloads/AmbiqSuite-Rel2.0.0/tools/apollo3_scripts/uart_wired_update.py”, line 336, in

main()

File “tensorflow/lite/experimental/micro/tools/make/downloads/AmbiqSuite-Rel2.0.0/tools/apollo3_scripts/uart_wired_update.py”, line 38, in main

connect_device(ser)

File “tensorflow/lite/experimental/micro/tools/make/downloads/AmbiqSuite-Rel2.0.0/tools/apollo3_scripts/uart_wired_update.py”, line 58, in connect_device

response = send_command(hello, 88, ser)

File “tensorflow/lite/experimental/micro/tools/make/downloads/AmbiqSuite-Rel2.0.0/tools/apollo3_scripts/uart_wired_update.py”, line 235, in send_command

raise NoResponseError

main.NoResponseError

My setup:

Macbook pro, tried both old 15" & new 13"

Sparkfun serial basic breakout, USBC version (default jumped to 3v3)

FTDI 3v3 serial cable

I have tried

two different edge boards, with the correct Key14 & reset combo + misc variants and timing

legacy USB on old Macbook

new Macbook w USB C

FTDI 3v3 serial cable as alternative to sparkfun serial board

Running an alternative uart_boot_host.py script in tensorflow/lite/experimental/micro/tools/make/downloads/AmbiqSuite-Rel2.0.0/tools/bootloader_scripts/uart_boot_host.py, also no response

I can measure, with a scope, the handshake bytes ‘0x14’, ‘0x55’, ‘0x9d’, ‘0xe9’ ‘0x0’, ‘0x0’, ‘0x8’, ‘0x0’ being transmitted initially at 115200 on the TXO pin on the programming header - but the ambiq is not replying anything.

btw. The onboard demo is running, blue led flashing, an some “yes’s” are being recognized.

Any inputs welcome.

Does anyone know the protocol for the corvette bootloader ?

Are there any CPU revision changes from the first batch of boards, or possibly any lock bits programmed accidentally from sparkfun ?

rgds from an eager TF lite user](https://www.dgcustomerfirst.run/)

It looks like that might be due to a timing error with the USB drivers; check out the 2nd answer here https://stackoverflow.com/questions/554 … r-problems with steps on how to update/ensure those aren’t the issue