always in DFU state..........

[jimlin]

Hello,

I use the bootloader in SDK v5.2.0 and could not run APP after DFU completed. It always stay in the DFU state. After checking the memory by J-Link commander, something seem wrong in mem 0x3FC800, shown as attached picture. I modify the source code, use 'if(!bootloader_app_is_valid(DFU_BANK_0_REGION_START))' instead of 'if(bootloader_button_is_pushed) || (!bootloader_app_is_valid(DFU_BANK_0_REGION_START)))', and the result is , the return by bootloader_app_is_valid() is always 0 so that it stays in DFU state. Why will it be here? My hardware version is G0 whlie softdeve is 6.0.

Thanks.

[jimlin]

Checking the memory 0x14000 and found it all 0xFF which means the app firmware does not be programmed success. But the MCP display the DFU successfully???

[Balaji Srinivasan]

Hi,

Indeed it looks like something went wrong during the firmware image transfer.

Could you please attach the Master Control Panel Log? It will be located in the folder [i]C:\ProgramData\Nordic Semiconductor\Master Control Panel[/i] in your PC.

Cheers, Balaji

[jimlin]

Hi Balaji,

Thanks for your remind.
It does not appear 'DFU successfully' after updating the MCP to 3.6.0. In fact, the application HEX does not be programmed at all by MCP 3.5.0. Maybe this is a display bug for MCP 3.5.0.

However, this problem has been killed.

Thanks again.

[Petter Myhre]

If you were able to answer your own question, I would appreciate if you could answer it yourself and accept it. It could be useful to others. Thank you.