9 years, 7 months ago.

No hex file for nRF51822

As posted in the following questions, the compiler is not producing hex files, in my case for nRF51822. The file produced actually looks like a binary file. What determines whether the compiler produces a binary file or hex file? Is this bug being worked on by the mbed team?

https://developer.mbed.org/questions/7999/Compiler-producing-different-or-corrupt-/

https://developer.mbed.org/questions/7996/Compiler-messed-up/

https://developer.mbed.org/questions/7998/Compiler-not-producing-a-hex-file-when-c/

https://developer.mbed.org/questions/8028/Problems-with-compiling-for-nRF51-random/

I tried posting this in the Bugs section of the forum, but kept getting Page Error, so there's a bug with that as well!

Some more information: this only seems to affect programs using mbed_src. If I use mbed.bld, all works fine.

posted by Tim Barry 06 May 2015

1 Answer

9 years, 7 months ago.

Hi All,

mbed-src is really the cutting edge of our development. Ideally there should be a separate develop branch for that repository containing experimental work, with the master being ready for use as a replacement of the binary 'mbed' library. This is our fault. We are transitioning to a new package management and build system, and we lack the motivation or time to invest in the older system.

THe present mbed-src repository contains goodness from an updated Nordic softdevice: the S130. It is not a direct replacement for the official 'mbed' SDK library.

You could roll your mbed-src back to revision 516 (or before) and continue with your work for now. https://developer.mbed.org/users/mbed_official/code/mbed-src/rev/b3fb5c6901a6

The next mbed SDK is expected to arrive early next week; and then you'll be able to sync forward to the latest of the mbed-src without any trouble.