This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf52832 segger "Build and Debug" download failed

Hi Nordic,

Why I cannot directly use segger's "Build and Debug" to download file to nrf52832, after I modify some code?

After I use nrfGo Studio first to program the hex file into nrf52832.

Then I can use Segger to "Build and Debug".

But next time I modify my code and do "Build and Debug", there's still the same problem(download failed).

Is my code size too big? or flash not setting right? or jlink dll version not pair the SDK16.0.0? 

Parents
  • Hello,

    Perhaps nRFgo studio is using the COM port, so that SES can't program the device?

    I have not seen this error before. Can you try to power cycle the DK before you program it with SES? Can you also try to erase the chip using nrfjprog (nRF Command line tools). You can use the command "nrfjprog --eraseall"

    Does it happen every time you re-compile the project, or only sometimes? What sort of hardware do you have? Is it the nRF52832 DK from Nordic? Or some 3rd party Development kit?

    BR,
    Edvin

  • I am using nRF52832 DK and our product using nrf52832 chip. Both board have the same problem. First I test ble_app_uart_pca10040_s132(peripheral), there is no problem. To add few code, there is no problem. But when I add more code, the problem happened. Once the problem happened, it happens every time I re-compile the project.

    After erasing the chip, it have trouble to download s132_nrf52_7.0.1_softdevice.hex.

    I have the same problem when I develop ble_app_uart_c_pca10040_s132(central).

Reply
  • I am using nRF52832 DK and our product using nrf52832 chip. Both board have the same problem. First I test ble_app_uart_pca10040_s132(peripheral), there is no problem. To add few code, there is no problem. But when I add more code, the problem happened. Once the problem happened, it happens every time I re-compile the project.

    After erasing the chip, it have trouble to download s132_nrf52_7.0.1_softdevice.hex.

    I have the same problem when I develop ble_app_uart_c_pca10040_s132(central).

Children
Related