-
Notifications
You must be signed in to change notification settings - Fork 1k
VECT_TAB_OFFSET patch #2134
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
VECT_TAB_OFFSET patch #2134
Conversation
Hi there, thanks for pinging me. While @thijses work was made with the best interests of the project in mind, the changes seem quite project specific to me and can be handled simply by using the combination of the |
Thanks @valeros for the quick feedback, |
That's right, the PR I'm working on should simplify this issue in a bit more generic way. |
impressively fast response, and fair enough conclusion. Looking forward to @valeros's future update. P.S., for posterity:
My platformio scripting has been slowly improving, so i genuinely did not know how to make it work with just |
yes indeed, thank you :) |
Mainly thanks to @valeros who was very reactive 😉 |
Summary
fix LD_FLASH_OFFSET build flag in platformio-build.py. Previously, setting LD_FLASH_OFFSET or VECT_TAB_OFFSET would be overridden by the builder. This small patch allows you to actually set the build flag manually (e.g. for custom bootloader applications). I also added a little warning for when the aforementioned parameters get overridden by the builder.
This PR fixes/implements the following features
motivation
i am implementing my own BLE OTA bootloader for the STM32WB55, so i need to compile code with a vector table (VTOR) offset. For an applied example, see this example sketch
Validation
i'm not entirely sure how to demonstrate that it's working, so here is an excerpt of builder output after setting:
where the line of important is:
Code formatting
(i couldn't find the style guide?)