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

Device Restart with reset reason 4 after connecting BLE and on Mobile Application restart

Hello Everyone,

I am using NRF52840 with Custom board, SES v5.20, SDK 15.1.0, IONIC android App(as Central)

1)My problem is, our nrf52840 board will restart once after successful BLE connection then again it will connect and then no restart just work normal and fine and the reset reason will be 4

2)and also controller restart suddenly(not every time, only sometimes) when i do clear data in my android application on that time also we get reset reason 4 only.

i found that reset reason 4 means- soft reset from https://devzone.nordicsemi.com/f/nordic-q-a/48446/how-to-detect-cause-of-reset but i am not able to understand what is soft reset means exactly  

and how i can solve this issue, 

Thanks in advance

Best Regards,

Raj.

Parents
  • Hello Raj,

    A soft reset means that the application called NVIC_SystemReset() somewhere, which will reset the chip. A hard reset would be powering the chip off and on.

    Most likely, it is the application error handler that triggers the reset. Can you try to add DEBUG to your preprocessor definitions? It looks like you are using Segger Embedded Studio, is that correct?

    If so, you will find your preprocessor definitions here:

    (Note the "Common" selected from the drop down menu).

    After you set this, the error handler shouldn't reset, but rather print some error reason in the log. Can you test this and see if the log says anything right before you would normally see the reset?

    Best regards,

    Edvin

Reply
  • Hello Raj,

    A soft reset means that the application called NVIC_SystemReset() somewhere, which will reset the chip. A hard reset would be powering the chip off and on.

    Most likely, it is the application error handler that triggers the reset. Can you try to add DEBUG to your preprocessor definitions? It looks like you are using Segger Embedded Studio, is that correct?

    If so, you will find your preprocessor definitions here:

    (Note the "Common" selected from the drop down menu).

    After you set this, the error handler shouldn't reset, but rather print some error reason in the log. Can you test this and see if the log says anything right before you would normally see the reset?

    Best regards,

    Edvin

Children
Related