nrf9160 nvs controller crash

RE: nrf9160 nvs controller crash

JBroemmling — Tue, 02 Nov 2021 09:35:50 GMT

Hi Håkon,

I've now disabled the log function because we have generally deleted most logs and will not use them later in the application.

Thanks for your help!

Kind regards,

Joshua

RE: nrf9160 nvs controller crash

Håkon Alseth — Fri, 29 Oct 2021 08:18:09 GMT

Hi Joshua,

It seems that the logging assert is a red herring.

Could you try adjusting the MAIN_STACK_SIZE to see if this is the culprit?

You can also run addr2line on the faulting content in R3 and LR register as well, which might tell us a bit more on where it came from. If possible, you can also attach your project (if it does not include any secret stuff).

Kind regards,

Håkon

RE: nrf9160 nvs controller crash

JBroemmling — Thu, 28 Oct 2021 09:31:39 GMT

Thanks for your answer Håkon,

the configuration was

CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=2048

before and now I tried it with

CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=4096

but it still crashes.

And you are right, it crashes in

zephyr/subsys/logging/log_core.c:1193

Best regards

Joshua

RE: nrf9160 nvs controller crash

Håkon Alseth — Thu, 28 Oct 2021 08:40:05 GMT

Hi,

15:33:11.975 -> [4D[J[00:01:18.517,730] [1;31m<err> os: r0/a1:  0x00000004  r1/a2:  0x0000006d  r2/a3:  0x00000000[0m
15:33:12.113 -> [4D[J[00:01:18.517,730] [1;31m<err> os: r3/a4:  0x0002bc5d r12/ip:  0x20016f10 r14/lr:  0x00029c0f[0m
15:33:12.205 -> [4D[J[00:01:18.517,761] [1;31m<err> os:  xpsr:  0x41000000[0m
15:33:12.297 -> [4D[J[00:01:18.517,761] [1;31m<err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000[0m
15:33:12.435 -> [4D[J[00:01:18.517,761] [1;31m<err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000[0m
15:33:12.572 -> [4D[J[00:01:18.517,791] [1;31m<err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000[0m
15:33:12.664 -> [4D[J[00:01:18.517,791] [1;31m<err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000[0m
15:33:12.803 -> [4D[J[00:01:18.517,822] [1;31m<err> os: fpscr:  0x00000000[0m
15:33:12.895 -> [4D[J[00:01:18.517,852] [1;31m<err> os: Faulting instruction address (r15/pc): 0x0004c748[0m
15:33:12.988 -> [4D[J[00:01:18.517,852] [1;31m<err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0[0m
15:33:13.080 -> [4D[J[00:01:18.517,913] [1;31m<err> os: Current thread: 0x20016988 (logging)[0m
15:33:13.174 -> [4D[J[00:01:20.992,645] [1;31m<err> fatal_error: Resetting system[0m

This shows that it is your logging thread that is causing the fault.

In general, you can use arm-none-eabi-addr2line -e build-folder/zephyr/zephyr.elf 0xFAULTINGADDR to resolve the address to a source file and line number. In this case, I suspect the logging thread is running out of memory.

Could you try adjusting the logging thread stack via this config?

CONFIG_LOG_PROCESS_THREAD_STACK_SIZE=2048

Kind regards,

Håkon