cant detect nrf52 with segger once I flashed the bootloader (sdk11)

RE: cant detect nrf52 with segger once I flashed the bootloader (sdk11)

makouda — Tue, 11 Oct 2016 13:09:32 GMT

nrfjprog --recover worked but after changing FAMILY to NRF52 in nrfjprog.ini file

RE: cant detect nrf52 with segger once I flashed the bootloader (sdk11)

Hung Bui — Fri, 26 Aug 2016 13:02:45 GMT

@makouda: I compiled your code and worked fine here, no problem with Jlink , the device advertises. I suggest to test on other board. Also make sure you have powered the chip on the board you are testing (for example if you cut SB9 on the nRF52DK you would need a jumper on P22)

RE: cant detect nrf52 with segger once I flashed the bootloader (sdk11)

makouda — Fri, 26 Aug 2016 12:39:22 GMT

@Hung also I noticed when I deleted all the ble functions including ble_stack_init the bootloader is always detected

RE: cant detect nrf52 with segger once I flashed the bootloader (sdk11)

makouda — Fri, 26 Aug 2016 12:32:35 GMT

I attached the bootloader project to the question

RE: cant detect nrf52 with segger once I flashed the bootloader (sdk11)

makouda — Fri, 26 Aug 2016 12:28:49 GMT

Jo Hung, this is what I get tring to run the command above

$ nrfjprog --recover
Recovering device. This operation might take 30s.
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.

RE: cant detect nrf52 with segger once I flashed the bootloader (sdk11)

Hung Bui — Fri, 26 Aug 2016 11:01:29 GMT

@makouda: Could you clarify that the broad is bricked now ? Or it still work and you can see it's printing out RTT log ?

Do you see the board in nRFGo Studio when you plug it in ? If you still can see the Segger chip in the list, you can try to use nrfjprog to do a recover :

nrfjprog --recover

Could you edit the question and attach the bootloader project source ?