• State Verified Answer
  • Replies 4 replies
  • Subscribers 63 subscribers
  • Views 483 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 304846
Options

Bluetooth init failure in Peripheral LBS sample on Thingy 53

DougR

When I use nRF Programmer on my laptop (v3.0.7) to update firmware on my Thingy53 with a USB cable and SW2, the programming seems to finish normally, but it prints "Bluetooth Init Failed (err -11)" on the nRF console in VS Studio, is not visible in Bluetooth scanners and doesn't blink the LED or do the other things. I get the same behavior whether I use a precompiled firmware (v2.0.0) or compile it myself from nrf/samples/bluetooth/peripheral_lbs in nRF SDK 2.3.0, using a build configuration for board thingy53_nrf5340_cpuapp, and no modifications to the generated config or code. I get similar results from other bluetooth samples programmed the same way on the same board. I've had success with updating the firmware to the builtin sample through the nRF Programmer iOS app using a separate Thingy53, and also success programming  onto an Arduino Nano 33 BLE Sense (using the board config and flashing with bossac). But I'd like to be able to compile and run Bluetooth apps on the Thingy53. Any suggestions for next steps? I don't have immediate access to a debug probe.

Parents
  • 0

    Hello,

    Sorry for the late reply. There seems to be some issues updating the network core via the serial bootloader, which is used in the nRF Connect for Desktop. 

    You can try to use an older version of NCS (so that the network core doesn't need to be updated), or you need to use a debugger to update the FW on the Thingy. I am sorry for the inconvenience.

    BR,
    Edvin

  • 0 in reply to Edvin

    I tried NCS downgrades (v 2.2.0, v 2.1.3) but the behavior was the same. I'm waiting on a debugger, which will hopefully be able fix that unit. I am having success with over the air firmware updates using the nRF Connect app and my other Thingy53 which had never been programmed using the serial bootloader, so I do have one unit which I can program. Thank you for your help!

  • +1 in reply to DougR

    Hello,

    I spoke to some of the Thingy developers. There was a bug, so downgrading will not work either. They are working on a fix, but unfortunately, it will not fix already programmed devices.

    You either need to re-flash the device using a programmer, or you can try to use mcumgr to flash the devices using the serial bootloader. I have not tried the latter for the thingy. They weren't sure whether you could upload a merged image, or if you had to do one core at the time. Also, they said that you need to wait for 2 minutes (!) after issuing the command "image test" before resetting / power cycling the device.

    BR,
    Edvin

Reply
  • +1 in reply to DougR

    Hello,

    I spoke to some of the Thingy developers. There was a bug, so downgrading will not work either. They are working on a fix, but unfortunately, it will not fix already programmed devices.

    You either need to re-flash the device using a programmer, or you can try to use mcumgr to flash the devices using the serial bootloader. I have not tried the latter for the thingy. They weren't sure whether you could upload a merged image, or if you had to do one core at the time. Also, they said that you need to wait for 2 minutes (!) after issuing the command "image test" before resetting / power cycling the device.

    BR,
    Edvin

Children
Related