This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can't select logging as the coredump backend in Zephyr

I'm trying to debug a usage fault in my NCS project using an nRF52833 DK. I can't seem to select the logging backend for coredumps. I have the following lines in my prj.conf:

CONFIG_DEBUG_COREDUMP=y
CONFIG_DEBUG_COREDUMP_BACKEND_LOGGING=y
However, I still need to add a coredump partition to make the build succeed. When the usage fault happens, it still tries to write the coredump to flash, but then a Zephyr assertion fails due to the fact that it wants to take a semaphore from ISR context.
I'm using NCS 1.6.0. What am I doing wrong?
Parents
  • Can you try to get the test zephyr/tests/subsys/debug/coredump up and running? Set CONFIG_RESET_ON_FATAL_ERROR=n (to make it not restart continuously)  and CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_MIN=n (if you want more that the bare minimum content) in the prj.conf. For me it built and run fine, and the dump showed up in the terminal.

    You may take a look at the NCS tutorial-->Error handling as well.

    Best regards,

    Simon

Reply
  • Can you try to get the test zephyr/tests/subsys/debug/coredump up and running? Set CONFIG_RESET_ON_FATAL_ERROR=n (to make it not restart continuously)  and CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_MIN=n (if you want more that the bare minimum content) in the prj.conf. For me it built and run fine, and the dump showed up in the terminal.

    You may take a look at the NCS tutorial-->Error handling as well.

    Best regards,

    Simon

Children
Related