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

No Cortex-M SW Device Found after program softdevice

Hello, the chip I use is nrf52810 QCAA, when I use j-flash lite to earse the whole chip, it success, then I program the flash_s112_nrf52_7.2.0_softdevice into the chip by keil5, it also success, but when I program my code into chip, it failed and shows No Cortex-M SW Device Found. After that, I can't earse the whole chip by j-flash lite which shows "could not connect  to target" and I even can't program the flash_s112_nrf52_7.2.0_softdevice which shows No Cortex-M SW Device Found. what should I do, the example I use is nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_hids_keyboard. Thank you!

Parents
  • Hi

    After a look at your log file, it seems like the application you flash onto the device throws the chip into a reset-loop/assertion loop in the beginning of your firmware, thus the debugger isn't able to successfully attach before the CPU core resets again. This is very hard to recover from, and the only thing we can recommend is to try running nrfjprog --recover while power cycling your board. You can for instance use a batch file on Windows:

    :loop
    nrfjprog --recover -f nrf52
    goto loop

    During development it's recommended to add blocking assertions by adding the preprocessor define "DEBUG" to avoid this issue. More details on that here.

    Best regards,

    Simon

Reply
  • Hi

    After a look at your log file, it seems like the application you flash onto the device throws the chip into a reset-loop/assertion loop in the beginning of your firmware, thus the debugger isn't able to successfully attach before the CPU core resets again. This is very hard to recover from, and the only thing we can recommend is to try running nrfjprog --recover while power cycling your board. You can for instance use a batch file on Windows:

    :loop
    nrfjprog --recover -f nrf52
    goto loop

    During development it's recommended to add blocking assertions by adding the preprocessor define "DEBUG" to avoid this issue. More details on that here.

    Best regards,

    Simon

Children
No Data
Related