-
Notifications
You must be signed in to change notification settings - Fork 943
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
add file @specified address to uf2 #1300
Comments
It sounds like in your use case you want 1 (since you just want it embedded anywhere) (or 2) |
@kilograham Thank you for reply the 1. would not work for my use case as I can not specify the exact location of the data on the flash. Reason I want to add file X at 1MB boundary in the flash is later I want the runtime to rewrite that location using the flash API. Therefore I wanted it to be at exact location and away from rest of the binary. I will investigate the other options given here as comments as they seem viadble. |
Why 1MB? Wouldn't 1 page be enough? This issue discusses an interesting technique for "reserving" an area in flash that you can update later #1278 |
Well it (address being 1MB from start of flash) is mostly an example but idea was: The program itself is not expected to grow over 1MB so that kind of nice (round) place to put it |
Hello, I somehow seem to fail at googling this.
What is the proper way to add arbitrary binary data to the uf2 image to be flashed.
What imagine is something like:
so that this file is flashed together with firmware and then I can access it by something like
const char *bitmap = (char*)XIP_BASE + 1024*1024
or ideally that address offset would even be defined as some named symbol in C source (instead of calculating it)
The text was updated successfully, but these errors were encountered: