Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Creating ble_app_beacon HEX file using ARM Keil MDK524a for NRF52 DK.

I am working with nRF5_SDK_14.2.0 ble_app_beacon example using NRF52 DK. If I have directly copy pated the readily available examples\ble_peripheral\ble_app_beacon\hex\ble_app_beacon_pca10040_s132.Hex (431 KB) file into NRF52 DK USB drive, application is working fine. If I compile the project (arm5_no_packs\ble_app_beacon_pca10040_s132) and copy paste the newly created HEX file (49 KB) from build folder into NRF52 DK USB drive then application is not working.

I am using ARM Keil MDK524a.
Readily available HEX file size is high and after build the HEX file size is low. Please help am I missing anything here during build?

Parents
  • Hi!

    So the examples\ble_peripheral\ble_app_beacon\hex\ble_app_beacon_pca10040_s132.hex file contains both the application AND the softdevice.

    The hex file from your build folder will only contain the application.

    One way to solve this is by downloading the softdevice to your nRF52 DK before the application.  Or you can merge the softdevice hex file and your application hex file to one hex file and then download it to your DK.

    Best regards,
    Joakim.

     

Reply
  • Hi!

    So the examples\ble_peripheral\ble_app_beacon\hex\ble_app_beacon_pca10040_s132.hex file contains both the application AND the softdevice.

    The hex file from your build folder will only contain the application.

    One way to solve this is by downloading the softdevice to your nRF52 DK before the application.  Or you can merge the softdevice hex file and your application hex file to one hex file and then download it to your DK.

    Best regards,
    Joakim.

     

Children
Related