DFU and Bootloader Debugging

[WestCoastDaz]

What's the best way to debug an application that is not starting after an OTA DFU update. The app said the update was successful but nothing booted and it didn't even seem like the CPU was running. The boot loader wasn't even advertising DFUTarg. I checked the boot loader settings at 0x7F000 and the app was marked valid but the CRC didn't match the one in the init file. This isn't correct right?

Also I noticed that all example DFU applications have the end of FLASH in the link scripts at 0x7FFFF not 0x79FFFF.

Thanks

[bjorn-spockeli]

I would start by debugging the bootloader and verifying that it reaches bootloader_app_start(DFU_BANK_0_REGION_START) and executes without asserting. If the bootloader_app_start() function executes without asserting, then the bootloader has successfully branched to the application, suggesting that the issue lies in the application. If this is the case, then I would start a debug session with the application and see if it ended up in the hardfault handler.

[AnnaSBX]

But how I can debug it? In my case I think that the bootloader didnt recognize the app and stay in DFU mode. I can not succses to put a breakpoint and no have an idea how to debug it :(

[bjorn-spockeli]

@AnnaSBX: Can you create a separate question where you describe your issue in detail?