• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 73 subscribers
  • Views 2092 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 122223
Options
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

S140 bootloader,no timeout?

Alice

Hi,

I use the bootloader in the SDK V13.0, I found that no timeout as the SDK v12.x. However, I have added the WDT to the bootloader refer to the link link text it still stay at the bootloader and never switch to the application from bootloader when the WDT timeout.

image description

Parents
  • 0

    How are you generating the bootloader settings hex? Can you post the nrfutil command and the output in the terminal? Also can you debug your bootloader project after you have flashed the combined hex file and check if you reach the if (nrf_dfu_app_is_valid()) statement( line 197) in nrf_dfu.c in the function nrf_dfu_init(). If so what does nrf_dfu_app_is_valid() return?

Reply
  • 0

    How are you generating the bootloader settings hex? Can you post the nrfutil command and the output in the terminal? Also can you debug your bootloader project after you have flashed the combined hex file and check if you reach the if (nrf_dfu_app_is_valid()) statement( line 197) in nrf_dfu.c in the function nrf_dfu_init(). If so what does nrf_dfu_app_is_valid() return?

Children
No Data
Related
Terms of service