Skip to content

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

Merged
merged 30 commits into from
Mar 27, 2015

Conversation

mfiore02
Copy link
Contributor

No description provided.

mfiore02 and others added 30 commits March 25, 2015 11:41
…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
…ision 80ff13fc47f41e758441af83259755580cae7bfb
…m VECT_TAB_OFFSET, allow for override of VECT_TAB_OFFSET
…nt name in IAR export. necessary for post-build script
…vision 53f849fca694138b944a3e4518e63a2881167cff
</option>
<option>
<name>OOCOutputFile</name>
<state>{{name}}.bin</state>
<state>application.bin</state>
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 26, 2015

I added my comments, please review them

@mfiore02
Copy link
Contributor Author

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.
Our desire is for this process to be invisible to the user as much as possible. We've achieved that in the context of the MBED build environment, but we're not quite there yet with IAR.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 27, 2015

Thanks for your comment, I'll merge this soon. You can patch IAR via a new pull request.

0xc0170 added a commit that referenced this pull request Mar 27, 2015
…uest

Updated hal & cmsis support for MTS Dragonfly and MTS mDot
@0xc0170 0xc0170 merged commit cfb9dd1 into ARMmbed:master Mar 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants