THingy:53 not able to detected in nRF Programmer

Hello,

Initially I was flashing software for peripheral_LBS by connecting Thingy directly through USB.

Later as per project requirement I tried to flash the code using VSC and somehow after that if I want to flash a precompiled firmware file to thingy USB then nRF programmer no longer detecting the Thingy.Even Though I am pressing the SW1 and SW2 together as mentioned here:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy53_gs.html#getting-started-with-precompiled-firmware-samples

but still it is not showing the device.

What do you think could be the reason of this issue?

Regards,

Divya

Parents Reply
  • Hello Marte,

    I do not know how to check if "peripheral_lbs include MCUboot when I programmed" but Now it is working for me. But I have few queries:

    1. How can I check that my code include MCUboot? 

    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. 

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

    Thanks & Regards,

    Divya

Children
  • Hi Divya,

    Divya_uni_ulm said:
    1. How can I check that my code include MCUboot? 

    You can check in the build folder where your project is built. If your application is built with MCUboot enabled you should have an mcuboot folder inside the build folder.

    Divya_uni_ulm said:

    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. 

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

    When you use thingy53_nrf5340_cpuapp_ns as build target you are building for the non-secure domain. If the sample has support for non-secure it should still work, as then the sample should automatically include the Trusted Firmware-M. Which sample are you seeing this in?

    Best regards,

    Marte

  • Hello Marte,

    Thanks for the reply, 

    I found that. Also,

    I am using peripheral_lbs sample code here and my device is not detectable when I am using thingy53_nrf5340_cpuapp_ns as in build configuration.

    Regards,

    Divya

  • Hi Divya,

    Edit: I believed I had reproduced the issue, but it seemed like my issue was related to something else. So I am able to use MCUboot to program the Thingy even when building as non-secure.

    Do you see this happen with other samples as well?

    Best regard

    Marte

  • Hello Marte,

    I have tried testing with the Thingy:UART sample using thingy53_nrf5340_cpuapp configuration.

    But now it is showing me the error like:

    Also, it is showing an error in the source file of UART sample:

    Can you please help me to resolve this issue? because I can try with other configuration until I will resolve these issues.

    Thank you in advance.

    Regards,

    Divya

  • Also, When I have tried the Thingy:UART sample using thingy53_nrf5340_cpuapp_ns configuration then it is successfully flashing the code but on the other hand the problem with thingy53_nrf5340_cpuapp_ns configuration is same. Again my device is not my device is not detectable when I am using thingy53_nrf5340_cpuapp_ns as in build configuration.

Related