nrf52832 reset continuously.

RE: nrf52832 reset continuously.

Einar Thorsrud — Thu, 17 Jan 2019 14:38:23 GMT

Hi,

[quote user="ronak"]But when debug session stop and unplug device and plug it again than code not run. [/quote]

Can you elaborate? Is it at this point you reach the error handler which you posted code snippets from in the initial question? If so, have you checked the state of the system and backtracked to see what proceeded this? Was it an error check?

[quote user="ronak"]After loading code through IDE or nrfgo studio, code does not work. No service named "Nordic Uart" found during scan of device in Mobile app.[/quote]

Essentially this tells us that "it does not work". As already mentioned there is a need to use the debugger more to understand what is going on. I do not see any way around it.

RE: nrf52832 reset continuously.

1979 — Thu, 17 Jan 2019 13:06:46 GMT

Hi,

Using Nordic Development Kit of nrf52832 and compiler Segger Embedded Studio for development.

Case 1: Build and Debug mode

Service named "Nordic UART" found during scan mode in Mobile APP. After connecting with this service, Data communication between board and BLE works ok in debug mode.

But when debug session stop and unplug device and plug it again than code not run.

Case 2: Build and Run mode

After loading code through IDE or nrfgo studio, code does not work. No service named "Nordic Uart" found during scan of device in Mobile app.

Reply me with solution for this issue. Thanks for your previous reply.

RE: nrf52832 reset continuously.

Einar Thorsrud — Wed, 16 Jan 2019 13:48:41 GMT

Hi,

Some error occurred (was detected) and caused the error handler to be run (which you have pasted some code for). You should be able to see more about what caused the error by building the Debug version (choose Debug instead of Release in the build configuration drop down menu) and running again. When you build with DEBUG the system will not reset but will instead trigger a breakpoint so that you can inspect the state with a debugger. In most cases the problem is that an APP_ERROR_CHECK has detected an error, and if so you can see the file name, line number and error code. You may also find this blog post interesting: An introduction to error handling in nRF5 projects.