No Connected Deivce for Thingy:53 board

[Divya_uni_ulm]

Hello,

So, as per the requirement for my project I need to program the Thing:53 using Visual Studio code programmer following the instruction as provided in the below link:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy53.html#thingy53-compatible-applications

As I am new to thingy:53, I tried to run the sample code for theThingy as provided on the link:

I have tried to set the build configuration as mentioned for the desired sample (Bluetooth: Peripheral LBS):

changes for the build are as mentioned below:

After finishing up the build configuration I tried to connect my device to the laptop but even after the build the software is not able to detect Thingy:53 in the connected device section

So, I have a query that do you know why am I not able to find out the device?

It would be highly appreciable if you can help me out to solve this problem.

Regards,

Divya

[Divya_uni_ulm]

Hello Elfving,

No there is no other error.

1. For the first time I programmed the Thingy with the sample code for peripheral_LBS provided in the “2022-08-03-precompiled-application-firmware”.
2. And this time sample code worked perfectly and provide the desired output.
3. But next time when I tried to build the Thingy with the sample code provided in the https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/peripheral_lbs
4. Using the build with Thingy Board

 

 

And then when I tried to flash the Thingy then the code has been programmed but then my phone is not able to connect with Thingy and also I am not able to monitor the output and print messages:

 

 

So, in conclusion, what I have understood so far is that if I am flashing the code using the sample code provided in precompiled-application-firmware then only Thingy is responding correctly but when I am trying to upload the sample code from https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/peripheral_lbs then it is not working correctly and monitoring the output as desired.

I am a bit confused now, what is the correct method to program Thingy with the sample code then?

Maybe I am missing some steps here. Please correct me and guide me what is the correct method to resolve this issue. It seems like.

 Regards,

Divya

[Elfving]

Hi,

Divya_uni_ulm said:

No, I do not have DK, is it a compulsion to use DK?

You can for instance take a look here on the documentation page on working with the DK. It mentions getting a debugger, and that is what I'd recommend.

By using a DK you would have an easier time flashing it, and debugging it. Note that the documentation does not mention how to go ahead by not using one.

Divya_uni_ulm said:

So, in conclusion, what I have understood so far is that if I am flashing the code using the sample code provided in precompiled-application-firmware then only Thingy is responding correctly but when I am trying to upload the sample code from https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/peripheral_lbs then it is not working correctly and monitoring the output as desired.

I believe the difference is that the nRF Connect Programmer can program using MCUBoot, which comes preinstalled on the Thingy (essentially doing a DFU). If you for instance find that you are able to flash using VSC then I assume the newer versions of the VSC extension allows for that as well.

How are you seeing that the building and flashing is successful?

Regards,

Elfving

[Divya_uni_ulm]

Hello Elfving,

So, in my project right now I am able to build and program on Thingy using J-Link debugger but there is still some issues I am facing after flashing:

For Peripheral_LBS sample

1. Whenever I am trying to connect my phone with Thingy, and then when I am pressing the button on Thingy then in the phone and in the nRF connect app, the log section is not showing the messages “Button pressed” or “Button Released”.
2. Also, after flashing the code in Thingy through VSC, the LED is not blinking. So is it normal behavior?
3. To verify if the code that I am building is flashing or not I have done a very small change, in the source file ”main.c” code I have changed the printk(“Connected\n”) message with a the below print message:

And then tried to build the code again and tried to check the behavior on phone over a Bluetooth connection but it is still showing a “connected”, message on phone rather than showing “Connected testing”.

It seems like the I code I am building has not flashed into the microcontroller.

4. Is the main.c file is not responsible for the message on phone and on serial port?

 

Regards,

Divya

[Elfving]

Divya_uni_ulm said:

Also, after flashing the code in Thingy through VSC, the LED is not blinking. So is it normal behavior?

Divya_uni_ulm said:

It seems like the I code I am building has not flashed into the microcontroller.

Divya_uni_ulm said:

Whenever I am trying to connect my phone with Thingy, and then when I am pressing the button on Thingy then in the phone and in the nRF connect app, the log section is not showing the messages “Button pressed” or “Button Released”.

I agree, all of these statements seem to point to that it is not being flashed. Are you seeing any error messages from VSC when flashing?

Regards,

Elfving

[Divya_uni_ulm]

Hello Elfving,

My code has been flashed now, and showing the results as desired.

But still I have some doubts, according to my observations:

I have noticed that when I am using "thingy53_nrf5340_cpuapp" then for build then it is working perfectly. whereas when I am using "thingy53_nrf5340_cpuapp_ns" for build then it build and flashed the code but my decide was not able to detect and this problem has been raised. 

1. Can you please clarify and help me to understand that why it is happening?

Also, in this ticket

 THingy:53 not able to detected in nRF Programmer 

mentioned that 

2. So, I want to ask  How can I check that my code include MCUboot? 

Thanks & Regards,

Divya