Hello,
I am currently dealing with an annoying bug that is consistently causing a hard fault, and breaks at the k_sys_fatal_error_handler function.
When investigating this issue online, I see lots of log messages that look like this:
[20210106144935][00:00:41.808,959] <err> os: ***** BUS FAULT *****[20210106144935][00:00:41.808,959] <err> os: Precise data bus error[20210106144935][00:00:41.808,990] <err> os: BFAR Address: 0xe39b7d52[20210106144935][00:00:41.808,990] <err> os: r0/a1: 0xffffffff r1/a2: 0x200098e4 r2/a3: 0xffffffff[20210106144935][00:00:41.808,990] <err> os: r3/a4: 0xe39b7d52 r12/ip: 0x00000000 r14/lr: 0x000270c5[20210106144935][00:00:41.808,990] <err> os: xpsr: 0x61000000[20210106144935][00:00:41.809,020] <err> os: Faulting instruction address (r15/pc): 0x0002714c[20210106144935][00:00:41.809,020] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0[20210106144935][00:00:41.809,020] <err> os: Current thread: 0x20002c48 (unknown)
that reveals the address where the fault occurred. This would obviously be very useful information for me, but I have no idea how to enable logs for the 'os' module, and could not find any documentation for how to do so.
Please let me know how I could do this.
Thanks,
Alex
