-
Notifications
You must be signed in to change notification settings - Fork 39
cannot upload on board #310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ok, got it to work, the 1 value of baudrate I had not tested worked. I had to choose "Sparkfun variable loader boadrate: 230400" and then it worked. Any idea why this exact value was needed / should this maybe be part of the documentation? |
Mmmh, this gets really confusing. On the next sketch I upload, I need to use "57600". Any idea why the baudrate change from upload to upload / how to set it or know which value to expect? It is quite time consuming to try one after the other until being lucky... |
Mmmh, on the next upload I had to plug in and out altogether and use 57600. Quite confusing. |
Now I do not manage to upload anything any longer. |
And now I manage, after trying randomly different baudrates several times in rows. Any idea about the logics behind? |
Probably related to: https://forum.sparkfun.com/viewtopic.php?f=171&t=53923&p=221527#p221527 . At this location people mention using another bootloader or something like this to fix the issues; any feedback on that? :) |
Is it possible that using this way of uploading instead may help? https://github.com/sparkfun/Artemis-Firmware-Upload-GUI |
@jerabaul29
Try uploading a few times and let me know your success rate. Note: Do NOT switch to the Ambiq Secure Bootloader (ASB) in between trials, this will blow away the SparkFun Variable Loader (SVL). When we released the new version of the core, we thought the ASB would be sufficient for most users. Through more testing we have seen that users have had a lot of problems with this bootloader (Especially if you are leaving the arduino COM window open when attempting to upload). In v2.0.3, I pushed a change that should allow the SVL to be used successfully, however the bootloader has to be burned using the aforementioned ASB, once this succeeds we would expect a much better experience using exclusively the SVL. |
Sounds good, many thanks for the explanations! I am away from my board just now, will try later on today. Many thanks for taking the time to look at this problem. I really hope this helps, because at the moment the board is not very usable. Crossing fingers :) |
I think I was able to upload the bootloader (that took quite a few tries):
But then I never managed to upload the sketch (tried at least 20 times):
|
Rectification: I was never able to upload with baudrate 921600 in at least 20 tries. I just tried with baudrate 115200, that worked without any issues 5 times in a row. A bit slow, but at least it works :) . Tried a few times 460800, seems to work too. |
Good to hear you were able to get it uploading! Nice call reducing the baud rate until it worked. |
I was quite happy when I saw I could get reliable updates :) . Any idea why the Ambiq bootloader is problematic, and why the baudrate 921600 is problematic? But the important is that it seems to work fine now. Maybe some documentation / guideline updates would be useful? Do you know if this is reproducible across users? :) . |
I can confirm that this works reliably: I have been playing around all day without issue uploading. |
On Ubuntu 20.04, after fixing the
chmod +x
of #309 , I bump into a new issue: the upload fails. Detailed log:Any idea where the problem comes from and how to fix it? I am using v2.0.3, "Red board Artemis", "Ambiq Secure Bootloader", I have tried several baud rates without success, and I am quite very sure that the USB port in use is the right one.
The text was updated successfully, but these errors were encountered: