• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 73 subscribers
  • Views 2025 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

    No, I am not aware of any issues with the WDT, it is identical to that of the nRF52832. Could you try to add the following line before you call the NRF_WDT->TASKS_START = 1;

    NRF_WDT->INTENSET = 1;

    If that does not solve the issue, then please you debug the bootloader and use the peripheral viewer to check the RUNSTATUS,INTENSET,CONFIG and RREN registers of the WDT to verify that the WDT is running, the TIMEOUT interrupt is enabled, it is configured and that the reload register is enabled.

Reply
  • 0

    No, I am not aware of any issues with the WDT, it is identical to that of the nRF52832. Could you try to add the following line before you call the NRF_WDT->TASKS_START = 1;

    NRF_WDT->INTENSET = 1;

    If that does not solve the issue, then please you debug the bootloader and use the peripheral viewer to check the RUNSTATUS,INTENSET,CONFIG and RREN registers of the WDT to verify that the WDT is running, the TIMEOUT interrupt is enabled, it is configured and that the reload register is enabled.

Children
No Data
Related
Terms of service