This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

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.

Parents

0 jimlin over 10 years ago

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.

Reply

0 jimlin over 10 years ago

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.

Children

No Data