Programming Thingy:53 with Bluetooth Mesh sensor_server example

[alwalker]

I have successfully built the Bluetooth Mesh sensor_server example, using the thingy53_nrf5340_cpuspp_ns build configuration.

But when I come to try and program the Thingy:53, it does not appear in the Connected Devices list, when connected to an nRF5340-DK board with a standard 10-pin cable (I used one from a STLink-V3). The RGB LED on the Thingy:53 illuminates on power up and cycles through the three colours a couple of times before going out, as it does when not connected via the 10-pin cable. When the Thingy:53 is connected via the 10-pin cable to the nRF5340-DK, the LEDs on the latter are not illuminated and neither appear in the Connected Devices list.

When I unplug and replug the USB cable to the nRF5340-DK board without the Thingy:53 connected, then the nRF5340-DK is detected and does appear in the Connected Devices list.

What else do I need to do for the Thingy:53 to be detected please?

I am using nRF Connect SDK v2.3.0 on Windows 11.

[Elfving]

alwalker said:

I do not see NRF5340_xxAA_ENGD on the Connected Devices list when the Thingy:53 is switched off and/or disconnected from the nRF5340DK.

So you do not see this exact part on the connected devices list, but I assume the rest of the section belonging to that DK is still there? Could you show me a screenshot of how this looks?

What is the version of your Thingy:53? You should be able to see this number underneath the NFC tag, right below "PCA20053".

alwalker said:

and also to check using the same hardware setup?

I haven't tried using your exact versions, but yeah I have tried it. The interface chip on the DK should read the UICR of the chip its programming and give it to you there. NRF5340_xxAA_ENGD should be referring to the SoC on the Thingy. I do not know exactly what you mean by selecting it though, would you mind expanding a bit on that?

You could in a way select something using the symbol in the image on the left, or after flashing when there are multiple options available. Though when making this selection you choose an id of the interface chips, not the name of the SoC.

 

Regards,

Elfving

[alwalker]

Hi Elfving,

This is what I see on the list of Connected Devices without the Thingy:53 connected/powered on:

This is what I get with the Thingy:53 connected via the 10-pin cable and powered on:

I select the NRF5340_xxAA_ENGD option in the normal way using the mouse pointer and right-clicking.

[Hung Bui]

Hi Al, 

Is there any chance you know how exact the board stopped working, was it when you did anything ? 

Could you try the following command: 

nrfjprog --recover --family NRF53 --log

And send us your log.log file created (in the same folder).

Also please run this: nrfjprog --version and let us know the version of nrfjprog and Jlink. 

[alwalker]

Hi Hung Bui,

Unfortunately due to the lack of indication that the Thingy:53 had been programmed in the first place and the resulting confusion with all the multiple attempts to get it working, I can't say when the nRF5340 DK was bricked.

Results with nrfjprog, it can't create the log file.

Kind regards,

Al

[Hung Bui]

Hi Al, 

It seems that nrfjprog can not create the file in the folder it run from. Could you try to run cmd with administrator right and try to run it in a different folder, maybe on different harddrive not C. 

nrfjprog should be put into system PATH so that it can run on any folder. 

Do you have any other Dev Kit that still working. I'm asking because it could be an Jlink problem. 

[alwalker]

Hi Hung Bui,

I need to look at how I can run nrfjprog in another location or drive under Windows 11 to produce the log file. I have admin rights for this PC but that doesn't appear to be sufficient to allow the log file to be written.

There is a difference in the error message reporting between the non-working and working nRF5340 DK boards. For the three instances shown of running the nrfjprog command, the first and third instances are with the non-working board and the second is with the working board. As you can see in the case of the non-working board it says that JLinkARM DLL reported an error both times.

Kind regards,

Al

[Hung Bui]

Could you please try copy the whole nrf-command-line-tools folder to another folder (drive) to test ?