NCS catch crashing app

[eyalasko]

Hello,

I'm pretty new to NCS (though an naRFcsdk5 veteran) so bear with me...

I've set up a new app based on peripheral_uart (nus) sample (nrf82540dk, NCS2. 5)

I've added another thread that sends  out a string over UARTE1 (the NUS thread uses UARTE0)

In the new thread I run the very same init code (uart_init) as in the sample's original thread and uart_tx() in the thread's loop.

For some reason the app crashes.

I tried to debug by commenting out the advertising so I can (more) easily breakpoint/single step, for no avail.

What is the best way to catch such a system crash in NCS?

What's NCS' equivalent to nrf sdk5 app_fault_handler (triggered from APP_ERROR_CHECK)?

Thanks

[Simonr]

Hi

There are quite a few resources available on "how to" debug in NCS already, so I'm just starting by sharing these: 

• Thread aware debugging with NCS
• Logging concepts in NCS. A DevZone ticket with an excellent reply from one of my colleagues.
• Testing and debugging an application in the NCS documentation.

Additionally, there should be some information in the logging when something faults on what the fault is (BUS fault, hard fault, etc.) and some register values that point you to where to look in the code. Generally only log messages with an err defined for the function to return error values is used for debugging in NCS I believe.

Let me know if you need more in-depth assistance and I'll see what I can do.

Best regards,

Simon