-
Notifications
You must be signed in to change notification settings - Fork 3k
Updated hal & cmsis support for MTS Dragonfly and MTS mDot #1001
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
Updated hal & cmsis support for MTS Dragonfly and MTS mDot #1001
Conversation
…ader. changed linker files to put application at 32kB offset added VECT_TAB_OFFSET define in targets.py so application runs properly after jump from bootloader
… 9de96dce). add support for automatically generating bootloader+application binary
…t one for each toolchain
… upgrade support including CRC32 checksum
…ision 80ff13fc47f41e758441af83259755580cae7bfb
…ith custom VECT_TAB_OFFSET
…rnal serial RX/TX/RTS/CTS
…m VECT_TAB_OFFSET, allow for override of VECT_TAB_OFFSET
…nt name in IAR export. necessary for post-build script
…export template for MTS_DRAGONFLY_F411RE
…b679ac2b8ddd30420eddd695eef91bef5fc1a7
…elease doesn't seem to work at all
…radio & external port
…72bf3b2b3d3f22a516e of bootloader
…rger stack and heap
…vision 53f849fca694138b944a3e4518e63a2881167cff
</option> | ||
<option> | ||
<name>OOCOutputFile</name> | ||
<state>{{name}}.bin</state> | ||
<state>application.bin</state> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why {{name}} was changed to predefined appliation name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The predefined application name is referenced by the post-build script, which combines the bootloader and application binaries into a single image. I was unable to figure out how to reference {{name}} (or find out if it is stored as an IAR environment variable) from my post-build batch script.
I added my comments, please review them |
One of our requirements for the MTS Dragonfly is support for remote firmware updates. To do this we wrote a bootloader that resides in the first 64kB of flash. Because we wanted to allow users to update firmware via the bootloader or via normal flashing over USB, we're combining the bootloader and application binaries into a single image (bootloader.bin + padding to 64kB + application.bin) so that there's no possibility of losing the bootloader when updating firmware. |
Thanks for your comment, I'll merge this soon. You can patch IAR via a new pull request. |
…uest Updated hal & cmsis support for MTS Dragonfly and MTS mDot
No description provided.