-
Notifications
You must be signed in to change notification settings - Fork 1
feat: flash sketch in ram #12
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
base: main
Are you sure you want to change the base?
Conversation
d2ca4a0 to
c38ef12
Compare
Is this something that should be notified to the user before the removal? |
How to test it
expected result: the led matrix should be off till you start again the app previus result: the les matrix will be on right after the animation. |
Motivation
Arduino apps require that the micro is in sync with the orchestration handled by
arduino-app-cli. In particular, at boot, we need the micro to wait for thearduino-app-cli, and start only to execute the sketch of the default app or some other app decided by the user.For this reason, we need to use the flash on RAM feature of the
zephyrplatform, which allows. In this way, the micro loses the code at every boot, and thearduino-app-clican reflash it with the correct app at boot.Change description
Update the flash mode to RAM, and handle the case in which the micro was previously flashed from the IDE2 with an in-flash sketch.
As a general note, a sketch could be flashed in RAM only if the micro is waiting for a sketch, which means that if there is a sketch already running from the flash, it should be removed by flashing an empty one.
Change description
Additional Notes
Reviewer checklist
main.