• State Verified Answer
  • Replies 3 replies
  • Subscribers 71 subscribers
  • Views 2156 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 114514
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Failed to read hex file - problem with uploading nRF51 bed hex to production hardware.

seajayshore

We are trying to get an mBed-compiled hex file uploaded to production hardware but it is throwing the error "failed to read hex file".

The code is compiled for the nRF51-DK target and the production chipset is the nRF51822. We are using a Segger J-Link to upload to the board. The app does use the BLE softdevice (incase this matters).

I've read problems related to not getting the code to run due to getting the internal/external clock settings wrong (especially with running BLE code).

I've not seen problems related to just not being able to read the hex file on 1st instance... Any ideas would be massively appreciated.

Have I selected the wrong target for the compiler? I noticed the nRF51-DK board is actually an nRF51422 and we are using an nRF51822 chip...

Parents
  • 0

    Hi Hung, This issue has actually been solved. I failed to mention that we were using nRFgo Studio to do the programming and I instructed the factory to check their software version. On Nordic's downloads page for nRFgo they state that with versions 1.12.1 (and above) they "Fixed an issue related verification of large hex files". I instructed the factory to update the nRFgo software and, hey presto, it's working now. :-)

    For anyone who has similar problems in the future I outlined my tests/adventure on this cross-post question on the mbed forum: developer.mbed.org/.../

    There's a bit more detail on other things that could go wrong there (incase it helps someone).

    Thanks again Hung for offering to help. :-)

Reply
  • 0

    Hi Hung, This issue has actually been solved. I failed to mention that we were using nRFgo Studio to do the programming and I instructed the factory to check their software version. On Nordic's downloads page for nRFgo they state that with versions 1.12.1 (and above) they "Fixed an issue related verification of large hex files". I instructed the factory to update the nRFgo software and, hey presto, it's working now. :-)

    For anyone who has similar problems in the future I outlined my tests/adventure on this cross-post question on the mbed forum: developer.mbed.org/.../

    There's a bit more detail on other things that could go wrong there (incase it helps someone).

    Thanks again Hung for offering to help. :-)

Children
No Data
Related
Terms of service