Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Sending Hello. No response for command 0x00000000 #3
Following the instructions on the SparkFun Apollo3 SDK page leads me to the following failure on image upload to the device:
This is after a long pause at the
This failed me from two different computers with two different Edge boards. I'm running on Arch Linux on both machines. The only other commonality between these setups is that I'm using the same FTDI board.
Additionally, following the instructions here yield the same result: https://codelabs.developers.google.com/codelabs/sparkfun-tensorflow/#5
According to the troubleshooting section on the next page of the codelabs instructions, this is happening because I need to follow the "hold down the button marked 14 while running the script. Hold down button 14, hit the RST button, then run the script, while holding the button marked 14 the whole time."
Just to confirm: this is exactly what I'm doing.
referenced this issue
Apr 16, 2019
@karma0 - since you're using a unix-like OS I wanted to double check that you've seen this: https://stackoverflow.com/questions/55463159/sparkfun-edge-bootloader-problems
Additionally I have found that if the executing code has a lot of serial communication that it can cause the bootloader to miss the initial reset request. To avoid this problem my upload sequence is:
Here's a simplified makefile that I wrote to simply upload a bin, and avoid any compilation (requires a binary file to upload)
And here's a binary to try with it:
Please let me know how this turns out for you - we'd like to be able to solve this problem for everyone else too. And thank you a lot for taking the time to report this to us!
I had the same problem and changed the Makefile to correct the baud rate that is by default 115200 but is set too high at 921600 in the Makefile:
Thanks for the help! Here's the output, seems identical:
I just ran that modified makefile to get some example output that you can target... I notice that after 'Sending Hello' I get 'Received Response' and 'length = 0x58' where in your output we're seeing 'received bytes 48'
That mismatch in length makes me think that the UART communication is off -- either by using the incorrect baud setting ( but you've tried both 115200 and 921600 if I recall correctly ) or the USB-serial bridge is misbehaving (possibly due to the same kind of driver issues as in the Stack Overflow post?).
Can you verify the accuracy of your UART output from the FTDI converter?
(p.s. the above makefile text is in
Following the suspicion that there may be driver issues with Arch Linux, I was able to find some other people having similar issues with the Linux kernel built-in drivers with various knock-off Arduinos coming from China. That eventually led me to this project that overrides the Linux
That being said, if you are getting the
Thanks for the help! I'll leave it up to you if you want to close out this issue or leave it open for others to post their solutions.