Skip to content

avoid 03/05 intel-hex records for nordic devices #4276

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 1 commit into from
May 8, 2017

Conversation

nvlsianpu
Copy link
Contributor

@nvlsianpu nvlsianpu commented May 5, 2017

Use Intelhex::write_hex_file instead of IntelHex::tofile do the work.
Mentioned records types has no sense for nordic devices.
Sucha a record comes from *.hex file from the mbed-os sources build.

This PR solves #4237

use Intelhex::write_hex_file instead of IntelHex::tofile
@theotherjimmy
Copy link
Contributor

I'm curious: why don't you need the start address?

@nvlsianpu
Copy link
Contributor Author

For NRF5 any of mbed-os app has a SoftDevice (SD) incorporated. SoftDevice is a BlackBox - the SoC run it thanks to the its reset handler (as for any else cortex-m device) and after some magic Softdevice call the user application. So for Nordic devices we expected run using reset - practical we even don't know where is the reset handler or the main of the SoftDevice.

Copy link
Member

@pan- pan- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@0xc0170
Copy link
Contributor

0xc0170 commented May 8, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented May 8, 2017

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 166

All builds and test passed!

@theotherjimmy
Copy link
Contributor

? @sg- did something go awry?

@sg-
Copy link
Contributor

sg- commented May 8, 2017

not sure!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants