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

How to flash Nordic Thingy through programming/debugging connector

Hey Dev Zone! I'm attempting to flash FW onto the Thingy via the nrf52840 dev board (which includes JLink). I connected P19 header on nrf52840 to P9 on the Thingy. I downloaded the Thingy source code, followed instructions to build project/pca20020_s132 (github.com/.../Nordic-Thingy52-FW). The hex file I was left with was nrf52832_xxaa_s132.hex. I ran the following commands to flash the hex file onto Thingy: ./nrfjprog -f nrf52 --reset --log ./nrfjprog --eraseall -f nrf52 --log ./nrfjprog --program ../../nrf52832_xxaa_s132.hex -f nrf52 --log But I saw the errors: ERROR: JLinkARM DLL reported an error. Try again. If error condition ERROR: persists, run the same command again with argument --log, contact Nordic ERROR: Semiconductor and provide the generated log.log file to them.

Attaching log.log. Could you help? Could it be that I need to reflash the bootloader? Thanks very much in advance, Shubhangir

Last contents of log.log:: Halt core after reset via DEMCR.VC_CORERESET. Reset: Reset device via AIRCR.VECTRESET. Reset: CPU may have not been reset (DHCSR.S_RESET_ST never gets set). Reset: Using fallback: Reset pin. Reset: Halt core after reset via DEMCR.VC_CORERESET. Reset: Reset device via reset pin DAP error while reading DP-Ctrl-Stat register. JLinkARM.dll reported error -1 at line 1421. FUNCTION: close_dll. FUNCTION: close_dll.

Parents Reply Children
No Data
Related