-
Notifications
You must be signed in to change notification settings - Fork 39
SparkFun RedBoard Artemis Nano - Upload fails from Linux #94
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
@nigelb Thnks for the detailed report. It is surprising to see an As for the other case (simply uploading from Linux) we've had many other reports about UART bootloader instability on Linux platforms in the past. That is actually why we created the SVL. So first I'd recommend trying a few other baud rate options (460800, 230400, 115200). If that doesn't work then please try checking / patching your CH340 drivers as described in these links: Please let us know how those efforts work out! |
Thanks for the hints @oclyke, I tried different baud rates with no success. I will have a look at updating my CH341SER driver when I am back in the office. I suspect that the |
@nigelb I just ran into the
I wonder - have you uploaded code using the ASB? That might explain some of this behavior. Perhaps one of your development computers has remembered some changes or old settings that causes it to try the ASB. I'd recommend checking Arduino's Tools options on any computer you are using. Please let me know what you discover! |
Hey @oclyke, pretty sure the bootloader is correct, see below: I installed the updated driver from: https://github.com/juliagoda/CH341SER:
Then in dmesg after I plugged in my board:
Then I can, with some trouble, upload the sketch:
Now by some trouble I mean I sometimes have to do the "spam the reset button" or "unplug and plug it back in at exactly the right time" tricks mentioned in the links you provided. However decreasing the I will also note that the test sketch above, that is continuously writing to the Serial Port, is particularly problematic once it is on the device. |
@nigelb I'm glad it is sort of working for you. Thanks for the report on your troubles too - we are definitely keeping an eye on this and trying to come up with improvements for the future. It has been surprisingly difficult to make this work reliably across all combinations of host systems and USB-serial bridges. Until we can get back to the bootloader issues You might consider simply using the Ambiq Secure Bootloader option - it is slow (115200) but pretty reliable. The exception being that it is not great when there is a lot of UART data being transmitted. We built the SVL to address the fixed-speed and poor UART hammering tolerance of the ASB but obviously we still have some work to do on it. In fact if you are interested you could check out the code and maybe make some improvements! The SVL is available as an example in the BSPs repo. You can build it for your board of choice like this:
This, of course, requires some prerequisites to be installed on your machine. Perhaps the easiest way to get started is to use the artemis_dev_platform |
Thanks @oclyke, I will check it out. |
@nigelb How has this issue progressed for you? We've recently updated the SVL bootloader to v5 which offers speed and reliability improvements. (In v1.0.23 of the core) You should upgrade the bootloader on the board using the |
Closing stale issue. Can re-open if issue persists |
Subject of the issue
I have a SparkFun RedBoard Artemis Nano. I followed the instillation instructions from the README on both Windows and Linux. Everything works fine from windows but when I use Linux the uploader fails.
Your workbench
Linux (Ubuntu 18.04.3 LTS): ardunio-1.8.10
Windows 10 Pro: ardunio-1.8.10
SparkFun RedBoard Artemis Nano
USB-C Cable from PC to device.
USB-C Cable from PC to device.
Steps to reproduce
Expected behaviour
When I compile and upload from windows:
Actual behaviour
When I compile and upload from Linux:
When I compile and upload from Linux, after I have uploaded the same sketch from Windows I get this different error:
The text was updated successfully, but these errors were encountered: