• State Not Answered
  • Replies 2 replies
  • Subscribers 73 subscribers
  • Views 1090 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110816
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

mbed with nrf51 dk

rushin

hello i want To use mbed for nrf51 dk. i used this link developer.mbed.org/.../. i am following steps but i can't copy hex file into bootloader. i got error message "There is not enough space on BOOTLOADER.You need an additional 168 KB to copy these files"

Parents
  • 0

    Hi, Rushin. You should not copy .hex files into the bootloader of the nRF51-DK. The bootloader (invoked by powering on the DK while holding down the reset button) is meant for updating the interface firmware on the on-board debugger (you can have either JLINK or MBED debugger firmware). If you want to program a .hex to the nRF device, you should drag-and-drop the .hex file to the normal MSD which is either named JLINK or MBED. If it is named BOOTLOADER, that means you are trying to update the on board debugger, not the nRF. Hope this clarifies it.

Reply
  • 0

    Hi, Rushin. You should not copy .hex files into the bootloader of the nRF51-DK. The bootloader (invoked by powering on the DK while holding down the reset button) is meant for updating the interface firmware on the on-board debugger (you can have either JLINK or MBED debugger firmware). If you want to program a .hex to the nRF device, you should drag-and-drop the .hex file to the normal MSD which is either named JLINK or MBED. If it is named BOOTLOADER, that means you are trying to update the on board debugger, not the nRF. Hope this clarifies it.

Children
No Data
Related
Terms of service