RE: Flashing via SWD not recognising Thingy:53

HoovinSchoovin — Thu, 03 Oct 2024 14:35:54 GMT

Thanks that is super helpful.

RE: Flashing via SWD not recognising Thingy:53

Einar Thorsrud — Wed, 02 Oct 2024 11:39:17 GMT

Hi,

From the photo it seems you have connected the cable between the DK and Thingy properly, so with this in place the onboard debugger on the DK should program/debug the external board (Thingy in this case).

[quote user=""]I tried this, but obviously it only did so to the DK.[/quote]

Was this with the cable in place? How od you see tha tit programmed the DK and not the Thingy? One simple way of checking which I use in such cases is to read out part of the device ID with the following command, and observe that I get a different value with and without the external board connected. If you do, that means that you are debugging the external board.

nrfjprog --memrd 0x00FF0204 --n 8

However, this will not work if AP protect is enabled, so you may need to first do a "nrfjprog --recover" operation.

[quote user=""]Tired flashing via the programmer, but get this issue[/quote]

This indicate that AP protect is enabled. Note that this is separate for the app and network core so you may need to do the following (the application core is implicit when no core is specified):

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover