Hang with nRF5 SDK 17.1.0 Bootloader and nRF Connect SDK 2.1.0 application

Question

I have an existing product that is using the nRF5 SDK 17.1.0 Bootloader. I have updated the application to use nRF Connect SDK 2.1.0. The new application also has an implementation of the buttonless DFU service, so that the nRF Connect app on iOS can be used to do the updates. 
 Most of this is working. The application runs fine when built to run without a boot loader. When build to run with the boot loader ( CONFIG_FLASH_LOAD_OFFSET =0x27000) there is an issue that I'm having trouble debugging. This is what is happening: 
 
 I erase the device and program in the nRF5 SDK 17.1.0 Bootloader. After reset the boot loader starts up normally. 
 I use the nRF Connect app on iOS to transfer over the nRF Connect SDK 2.1.0 application. I get a success message from the nRF Connect app. 
 The application does not start BLE advertising and the device appears to be hung. 
 If I attach the VScode debugger, it usually halts inside the boot loader startup sequence where it is checking the CRC. 
 Looking at the RESETREAS register I see the expected SREQ, but I also see LOCKUP. 
 If I continue code execution then the application starts up and works fine. 
 
 The hang happens every time I run the above sequence. It happens with or without a debug probe attached. None of the nrfjprog resets (--reset, --debugreset, --pinreset) have any effect - the device remains hung. If I attach the debugger before step 2 above then the halt doesn't happen. The application starts up fine without any hang. 
 Anyone have any ideas on what might be happening? Any tips on how to debug this type of issue where simply having the debugger attached avoids the issue?

Vidar Berg · Accepted Answer

Yes, the DK starts advertiding when using my version. But it enters a reset loop if I DFU your app. Writing the settings page is a quicker way to test this. And it&rsquo;s the only way for me if I&rsquo;m going to run my app with your bootloader. 
 Did you move the settings partition in your lbs project. If not, it will go in a boot loop like I mentioned in my first reply here.

denis · Answer

Sorry, I missed that. I see, the change is in the peripheral_lbs/nrf52840dk_nrf52840.overlay. Using the nRF52840-DK board I can now DFU with that change and the app starts up. And if I remove the config changes to not use the DC/DC and to use the RC the app also starts up. 
 I then tried the same boot loader and peripheral_lbs dfu on my custom board without the RC changes. And it does hang. Until I attach debugger and hit continue. 
 So the behavior on the nRF52840-DK and our custom board is different. 
 I then checked the schematics and sure enough the inductors are not in this design for the DC/DC converter. Adding CONFIG_BOARD_ENABLE_DCDC=n to my app fixed the issue. The app starts up properly now. 
 Thank you for all the help! Obviously I should have seen this when setting up the custom dts. What I still don't understand is how that manifested in all these other odd things happening, working from the debugger, etc... 
 BTW: I don't have a storage partition defined in my custom board dts that my app uses. 
 CONFIG_BT_SETTINGS=y CONFIG_SETTINGS_RUNTIME=y CONFIG_SETTINGS=y CONFIG_SETTINGS_NONE=y

denis · Answer

Ah, so the switch to LDO when attaching the debugger explains why the firmware works after the attach. 
 BTW: The peripheral_lbs build does fail with my custom dts. I built it for the nRF52840-DK and ran that on my custom board as it is somewhat compatible, at least for that simple example.

Hang with nRF5 SDK 17.1.0 Bootloader and nRF Connect SDK 2.1.0 application

Top Replies