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

NRF52832 adafruit feather - flash error (ESB low-power example)

Hello.
I 've got such problem with flashing some of the ESB protocol examples of NRF5 SDK.
I use Adafruit Feather NRF52832 board with ST-LINK V2 debugger.
https://www.adafruit.com/product/3406
I work in Keil 5 IDE.

When Ii try to load some of BLE examples (Periph Blinky, etc.), everything is ok. First I flash the Sortdevice and than directly an example.
App works no problem.

But when I try to flash ESB examples (like ESB low power prx) I've got such error.

I use default flash algorithm in debug settings.
But once when I change smth I got it flashing, but than I again try to flash SoftDevice and BLE and after that again can't flash ESB...


Any ideas what am I doing wrong?

All my best.
Ivan.

Parents
  • Hi,

    Did you remember to erase the chip before you programmed the example? 

    Use this nrfjprog command before you try to program it:

    Fullscreen
    1
    nrfjprog -e
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Best regards

    Jared 

  • So flash erase via Keil doesn't seems to be correct?

  • again, have you tried with the ST-Link Utility - to rule Keil out of the issue?

  • st-link utility gives an error to flash.
    But directly via Keil I can flash Soft Device and BLE examples no problem.
    Once I was lucky to flash ESB example, maybe that was correct erase of the chip.

  • Whoops! I read this one a bit too quick and missed the part about the ST-LINK. As has already suggested, I would recommend using a debugger that is supported by us. I think the source of your issue is that a proper erase isn't performed before you try to reprogram the device. 

    best regards

    Jared

Reply
  • Whoops! I read this one a bit too quick and missed the part about the ST-LINK. As has already suggested, I would recommend using a debugger that is supported by us. I think the source of your issue is that a proper erase isn't performed before you try to reprogram the device. 

    best regards

    Jared

Children
No Data