Hard fault in ipc_trace_handle (proprietary Nordic library)

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

jbrzozoski — Thu, 26 Sep 2019 13:25:29 GMT

I have not been able to recreate this in the month+ since upgrading to the newer NRF and MFW. I'm willing to say something in one of those helped resolve this...

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

jbrzozoski — Wed, 14 Aug 2019 14:54:13 GMT

Haven't hit this one again since last week. I've still got some extra debug code in place to hopefully provide more useful info if it happens again, but I can't reproduce it at this point and I'm focusing on other things.

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

EvenFL — Wed, 14 Aug 2019 06:58:11 GMT

Have you had any progress with the issue?

You can also try to capture a trace using the Trace Collector in the nRF Connect Desktop

www.nordicsemi.com/.../nRF-Connect-for-desktop

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

jbrzozoski — Mon, 12 Aug 2019 16:07:17 GMT

My application is compiled in NS mode with UARTE1 setup as NS, so nothing should be writing to the secure address. That's an interesting bit of insight I missed. Thank you.

If the failure is related to the UARTE, then any printk or UART logging may not work. Thankfully, I just got the RTT logging back-end working! So a LOG_ERR in immediate mode should at least produce something through there.

I haven't hit this error in the past week, though, so it's just a waiting game at this point...

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

EvenFL — Mon, 12 Aug 2019 07:23:26 GMT

I know that the ipc trace handler is in a code path that may trigger any of these handler if an error is detected as it's used in that parts of the BSD library. It may be that must run in a debug session and break inside this functions to be sure to capture the error code

The 0x50008120 address is pointing the first UARTE instance on this devices, so I guesstimate that something is trying to print something on your console. However I am not sure why it fails, maybe because it's trying to access a non-secure peripheral using the secure peripheral address.

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

jbrzozoski — Fri, 09 Aug 2019 13:54:19 GMT

I already have the error handlers implemented, but have them report via LOG_ERR instead of printk. And (unfortunately) I run with deferred logging instead of immediate logging, so they might have been triggered but the hard fault went off before the logging thread had a chance to process/display them,

I'll stick a log_panic() in those handlers to force it into immediate mode on failures... However, I can't reproduce this fault reliably. It may be a while before I get anything.

Why do you think a BSD error is likely to be related to a fault in the IPC handler?

RE: Hard fault in ipc_trace_handle (proprietary Nordic library)

EvenFL — Fri, 09 Aug 2019 08:17:03 GMT

Hi,

Try to implement these functions in your main application (for instance in main.c):

void bsd_recoverable_error_handler(uint32_t error)                                                                                                                                                                                                                             
{                                                                                                                                                                                                                                                                              
    printf("Err: %lu\n", (unsigned long)error);                                                                                                                                                                                                                            
}                                                                                                                                                                                                                                                                              

void bsd_irrecoverable_error_handler(uint32_t error)                                                                                                                                                                                                                           
{                                                                                                                                                                                                                                                                              
    printf("Irrecoverable: %lu\n", (unsigned long)error);                                                                                                                                                                                                                  
}

And check if they are triggered before you get the HARD FAULT? I would like to know what the error parameter is set to.