Secure bootloader timeout not working on S132 15.3 SDK with logging disabled

RE: Secure bootloader timeout not working on S132 15.3 SDK with logging disabled

nemik — Sat, 10 Aug 2019 18:24:01 GMT

I've solved this by checking the NRF_POWER->RESETREAS register in dfu_check. If it's 0 it means it work up from total system off and I'll start the bootloader. For anything else I'd want application to start, which includes the reset issued by the bootloader after its inactivity timeout.

RE: Secure bootloader timeout not working on S132 15.3 SDK with logging disabled

nemik — Sat, 10 Aug 2019 15:27:59 GMT

Thank you for this information. I switched to use Segger Studio and was able to debug a bit easier. I think the problem I'm running into is that when I try to do 'nrf_bootloader_app_start();' inside the activity timeout handler, after dfu_check already returned true, that it does not jump to the application code properly and encounters some errors. However I can't seem to hit breakpoints within the code that does that.

I'm still stuck but hopefully will figure this out. I'm surprised starting bootloader on power up then timing out to the app isn't a more common use case. I really did not expect this to be so difficult.

RE: Secure bootloader timeout not working on S132 15.3 SDK with logging disabled

Turbo J — Fri, 09 Aug 2019 18:00:57 GMT

One possible problem might be code with side effects inside an NRF_LOG_xxx statement - this would be eliminated in the release build.

You CAN debug release code by turning on debugging symbols.The optimizer will shuffle the code around quite a bit, but GDB is still somewhat usable. Oh, and being able to read the disassembly helps a lot.

Just remember to put breakpoints before you enable and after you disabled the softdevice, as a running SD must not be halted.