• State Not Answered
  • Replies 4 replies
  • Subscribers 65 subscribers
  • Views 385 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 314798
Options

nRF5340 BLE DFU, unable to Enable Bluetooth after initial reset

Mike Pulice

We have been living with the workaround of pulling the battery after a BLE DFU update to the App core.  

Custom board with nRF5340, DFU to the App Core using MCUBoot and nRF Connect for Mobile on iOS or Android. 

The product resets fine, nRF app on mobile says Success, Clear.  However, enabling Bluetooth does not work without fully pulling power.  

Just a guess here but I feel like the Net core does not get reset in the MCUBoot/nRF Connect Reset process.  

Any ideas about this?  Search of DevZone yielded no results. 

Thank you

Parents
  • 0

    Hi,

    Do you just update with nRF Connect for mobile (so that the app resets as part of the upgrade procedure), and that triggers the issue? Or does it happen in another way? Also, do you see the same if you perform a soft reset in another way? And do you see the same behavior with different devices?

    Without knowing more it sounds like this could be caused by erratum 161. This will be properly handled in nRF Connect SDK 2.5.0 when that is released.

  • 0 in reply to Einar Thorsrud
    Einar Thorsrud said:
    Do you just update with nRF Connect for mobile (so that the app resets as part of the upgrade procedure), and that triggers the issue?

    Yes, the regular reset that the app performs as part of the upgrade procedure.

    Einar Thorsrud said:
    Also, do you see the same if you perform a soft reset in another way? And do you see the same behavior with different devices?

    Only with MCUBoot BLE DFU and other devices meaning our devices?  All of our devices behave the same way.

    Einar Thorsrud said:
    Also, do you see the same if you perform a soft reset in another way?

    I did experiments with soft resets with the command line tool and segger tools and this did not happen, which led me to believe it is something with how the device is reset by the nRF Connect for mobile doing MCUBoot DFU. 

    That erratum seems to be an issue, depending on how nRF Connect for Mobile performs the reset. 

  • 0 in reply to Mike Pulice

    I see. I have not seen any reports of this before, nor am I able to reproduce when I test with a nRF5340 DK and the SMP Server Sample with Bluetooth transport. Can you explain more detail about how you do DFU and which SDK version you are using? Do you see the same if you test on a DK instead of your custom board?

Reply Children
Related