Dear Members,
How can I find the cause of
<error> app: Fatal error ?
I can't see an error code ?
Is it possible hardware error because voltage surge ? Can capacitor rectify it ?
Thanks
Dear Members,
How can I find the cause of
<error> app: Fatal error ?
I can't see an error code ?
Is it possible hardware error because voltage surge ? Can capacitor rectify it ?
Thanks
Hi,
I can't see an error code ?
You will get more information (file name, line number and error code) by testing with a debug build. If you use a Segger embedded studio project from the SDK, simply select "Debug" from the build configurations dropdown menu. If using something else, define "DEBUG" and "DEBUG_NRF".
Is it possible hardware error because voltage surge ? Can capacitor rectify it ?
We need to know what the error code was and from where it was returned before we can consider what caused it and how it can be fixed.
I get a clue just now, when the board lost connection with the sensor, ANT HRM sensor, it's giving me
If I used Keil, how can set "Debug" build ?
With Keil, go to Project -> Options for Target ...., and then select the C/C++ tab. There add "DEBUG" and "DEBUG_NRF" to the preprocessor define list as shown here:
If you want to debug (break in code, inspect with a debugger etc.) it makes sense to also set the optimization level to 0. That is not related to logging, though.
Thanks Einar, I'm compiling and uploading now, I'll keep posted
I got this error :
<error> app: ERROR 0 [NRF_SUCCESS] at ..\..\..\..\..\..\..\..\components\librari
\libuarte\nrf_libuarte_async.c:230
at: 0x000390A3
rror> app: End of error report
How can I rectify it ? thanks