No log on fatal error

[GilDev]

Hello,

I’m using the aws_iot sample with the nRF9160DK-nRF9160 target. When I introduce a bug (calling `net_if_up()` on a wrong interface), the system crashes and halts but I get no log on the console. If I enable `CONFIG_RESET_ON_FATAL_ERROR`, I only get the boot logs continuously, no dump or reset reason:

*** Booting My Application v2.1.0-dev-9b4ae4cbc9e2 ***
*** Using nRF Connect SDK v3.1.1-e2a97fe2578a ***
*** Using Zephyr OS v4.1.99-ff8f0c579eeb ***

*** Booting My Application v2.1.0-dev-9b4ae4cbc9e2 ***
*** Using nRF Connect SDK v3.1.1-e2a97fe2578a ***
*** Using Zephyr OS v4.1.99-ff8f0c579eeb ***

…

I have enabled CONFIG_ASSERT, CONFIG_DEBUG_COREDUMP, CONFIG_COREDUMP_DEBUG_BACKEND_LOGGING, NET_LOG, LOG and such but it didn’t help.

Do you please have any idea on how to get some crash logs on the console when having a fatal error?

[mackz]

You might need to add CONFIG_LOG_IMMEDIATE so it logs before rebooting

[GilDev]

Thanks for your reply, that doesn’t help though, same logs printed. I asked on the Zephyr’s Discord but someone redirected me here.

[Elfving]

Hi,

So you are not otherwise seeing this, ie. when building without net_if_up used? Can you show me where you placed it, so that I can try to reproduce this?

Regards,

Elfving