• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 88 subscribers
  • Views 563 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281637
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hex files to program

dilbert168

I am using the following example to load the code with Segger debugger and it works.

nRF5_SDK_17.0.2_d674dde\examples\ble_central\ble_app_blinky_c\pca10040\s132\ses

Now, when using "nRF Programmer" to flash the chip,  

- Application is "ble_app_blinky_c_pca10040_s132.hex" from "\examples\ble_central\ble_app_blinky_c\pca10040\s132\ses\Output\Debug\Exe\"

- where do I locate files to load "SoftDevice" and "MBR" sectors ? 

  • +1

    Hi

    The SoftDevice .hex files can be found in ...\YOUR_SDK_FOLDER\components\softdevice

    It will be sufficient to add the S132 SoftDevice .hex and your application .hex files in nRF Programmer to flash your device correctly.

    Best regards,

    Simon

    PS: We will be short on staff during the Holiday period, and delayed replies must be expected. We will be back to full staff on January 3rd. Happy holidays and happy new year!

  • 0 in reply to Simonr

    Thanks.  it works.

    Have another question, I am using the nRF52_DK to program my own target board which has same nRF52 chip.

    I have tried both cases connect/disconnect my target board.  But programmer is showing same device ID.

    Is there a way to confirm that correct chip is programmed ??

Related