Got it. Giving the rationale for the request would help us understand. Nobody else in the Udoo Team to take this one? I can help, but I will need instructions. How one with the board could do the test you are requesting? i.e., "add a "sync" between lines 154 and 155 in udooneo-m4uploader" Thanks, -Jack
First you need to find that file. For example run: find /usr | grep m4uploader in a terminal. The open the file for editing: sudo leafpad /path/to/the/file Add the sync statement , save the file and reboot using sudo reboot Then try to reproduce the bug again. Thank you !
use "which udooneo-m4uploader" in place of "find /usr | grep m4uploader" (that's shorter) you can even find and open it in one line: sudo leafpad `which udooneo-m4uploader`
Hey fellows, Good news. It seems to work. I placed "sync" before the line 155 "fi" Uploaded a new code using the Arduino 1.6.12. MacOSX Yosemite. Waited ~5s Reset NEO The Arduino code on the M4 still runs. Few more tests Even when I press the reset , or remove the power (USB cable), on the Neo as soon as the Arudino IDE show the Done Uploading and M4 Sketch is running, it seems to work. Good job! Now to the Udoo Team to document this and hopefully an Ubuntu 2.1.1 release... Thanks, -Jack
@Francesco I tested it too with the added sync in /usr/bin/udooneo-m4uploader and that seems to do the trick! No more empty m4last.fw files and running last compiled file every time after a hard reset. It also worked now for internal programming.
Thank you guys for the all tests you did! I have fixed it in git. On Wednesday when I'll be back we will release it on the apt-get repo.
I've found that if the script takes time to start the mqx_upload_on_m4SoloX returns an error (even if the script is working correctly): UDOONeo - Waiting M4 Run, m4TraceFlags: 0000027F UDOONeo - Waiting M4 Run, m4TraceFlags: 0000027F UDOONeo - Waiting M4 Run, m4TraceFlags: 0000027F UDOONeo - Waiting M4 Run, m4TraceFlags: 0000027F UDOONeo - Failed to Start M4 sketch: reboot system ! as the copy of the binary in /var/opt/m4/m4last.fw is done after flashing this is never called. I've moved the copy part before flashing and now all work fine (as the script has passed compilation i don't care about flashing errors).
I did the udo apt-get dist-upgrade. The program of M4 is not being lost after a reboot. Assuming the the correct files are being replaced, this is done. Will a new Ubuntu release come so fresh installs work out of the box? Thanks, -Jack