Francis Schumacher

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

9 years, 6 months ago.

Problems with compiling for nRF51 - random .hex files?

Is anyone else having problems with compiling for nRF51? I started getting a directory with an "Info.plist" file and an accompanying .hex file where previously I've just gotten a .hex file (and no directory). The .hex file doesn't work when copied to the mbed disk, and it appears to be of a random size: I can compile the same thing multiple times and I get various random sizes.

I am able to compile for the KL46Z normally, so I'm guessing this is limited to the nRF51. I've waited and retried a few times, but it's been 3 hours and the behavior for the nRF51 compilations is the same.

Any pointers?

1 Answer

Martin Kojtal
9 years, 6 months ago.

Hi,

there are few similar reports. What revision of mbed library are you using? Switch back to the previous one, you should be fine. Looks like scripts in the online IDE are not up to date.

Accepted Answer

Thanks for the response. Unfortunately, no joy. I was using the latest mbed rev98, so I switched back to rev97 (and also went back to earlier revs of nrf51822 rev11 and ble_api rev341 to get it to compile). I also tried on firefox instead of safari, but the behavior is similar (although firefox doesn't create the extra directory with the Info.plist file, it does create a .hex file of a random size). Any other suggestions?

posted by Francis Schumacher 04 May 2015

Hi Martin. I have the same problem and rolling back to a previous revision isn't an option for me as I need the bug fix from the latest nrf51822 library (https://developer.mbed.org/questions/7962/Multiply-defined-symbols-in-nRF51822-lib/). Also, I think this problem has been around for a while as I received my BLE nano on 24th April and kept getting "SWD Error" when I downloaded the hex file from mbed blinky. I've since had a look at the hex file and it is corrupted. Any idea when we can get a fix for this? Thanks, Tim

posted by Tim Barry 05 May 2015

Martin: all is well with the compiler now. I'm getting correct & consistent output using all the latest library versions. Please pass on my thanks to the folks behind the curtains who made all the magic work again.

posted by Francis Schumacher 07 May 2015

Cool !

posted by Martin Kojtal 07 May 2015