• State Verified Answer
  • Replies 2 replies
  • Subscribers 68 subscribers
  • Views 65 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 333935
Options

Flashing via SWD not recognising Thingy:53

HoovinSchoovin

Hello,

I am running into a problem with my Thingy:53 device where I am unable to load up the bootloader. I has the edge inpulse application working well yesterday, after trying to follow this, i ran into an issue.

Core issue

When trying to flash the thingy53 through the nRF5340 DK using the SWD, i do not think it is being recognised and instead is flashing the DK.

Things ive checked.

  1. I’ve checked the voltages of the Li-po, the 3v pin and the 3v3 pin on the thingy and they are all nominal.
  2. I’ve checked the SWD connector for continuity and it appears connection between thingy and dk is fine
  3. I built firmware for the DK (blinky) and with the thingy powered and plugged in through SWD, i tried flashing the application to the thingy to test if the DK was recognizing it as the target chip. After flashing, the DK’s nRF53 ran the application code and started blinking. This suggests the DK doesn’t recognize the thingy as the target.

I set up in the following way:

1. I set up the devices like the following:


2.Successfully ran the following command (from this question: .: RE: Thingy:53: Programming) I tried this, but obviously it only did so to the DK.

nrfjprog -f NRF53 --program merged.hex --chiperase --verify --reset

3. Turned on the board while pressing SW2

 

4. No lights turn on and cannot find the bootloader in nrf programmer. 

I've also tried the following:

- Tired flashing via the programmer, but get this issue

 

 

Would very much appreciate any suggestions Slight smile

  • +1

    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). 

    I tried this, but obviously it only did so to the DK.

    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.

    Tired flashing via the programmer, but get this issue

    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

Related