Data access violation in Zephyr when accessing nPM1300 with nRF52832

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

Kampino — Fri, 03 Nov 2023 07:49:34 GMT

Hi,

we´ve figured out the issue. I used the wrong device for the regulator. I have to use

static const struct device* regulators = DEVICE_DT_GET(DT_NODELABEL(npm1300_ek_buck1));

With that, the code is working.

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

helsing — Thu, 02 Nov 2023 10:43:43 GMT

[quote user="Kampino"]C:/ncs/v2.5.0-rc2/modules/hal/nordic/nrfx/hal/nrf_clock.h:948[/quote][quote user="Kampino"]C:/ncs/v2.5.0-rc2/zephyr/kernel/sched.c:195[/quote]

What do you find when opening these files, checking line 948 and 195?

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

Kampino — Tue, 31 Oct 2023 10:50:36 GMT

Hi,

no. I tested the latest versions to make sure that this is not an issue of a specific SDK. I had the same issue at the same place with 2.4.1, 2.5.0-rc2 and 2.5.0.

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

helsing — Tue, 31 Oct 2023 09:30:55 GMT

What do you find if you go to that file and line 948?

[quote user="Kampino"]C:/ncs/v2.5.0-rc2[/quote]

Are you using any special features from c2.5.0-rc2, or could you perhaps try using v2.5.0?

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

Kampino — Fri, 27 Oct 2023 16:31:46 GMT

I get this output

\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line.exe -e zephyr.elf 0x0000c3fd
C:/ncs/v2.5.0-rc2/modules/hal/nordic/nrfx/hal/nrf_clock.h:948

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

helsing — Fri, 27 Oct 2023 16:25:40 GMT

And what do you get with

\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line.exe -e zephyr.elf 0x0000c3fd

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

helsing — Fri, 27 Oct 2023 16:23:57 GMT

Great. What happens if you check line 195 in C:/ncs/v2.5.0-rc2/zephyr/kernel/sched.c?

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

Kampino — Thu, 26 Oct 2023 16:54:05 GMT

Hi,

I got the following output:

..\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line.exe -e zephyr.elf 0x00008cf4
C:/ncs/v2.5.0-rc2/zephyr/kernel/sched.c:195

\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line.exe -e zephyr.elf 0x000211a8
??:0
\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-addr2line.exe -e zephyr.elf 0x00018b3d
??:0

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

helsing — Thu, 26 Oct 2023 13:28:00 GMT

Here is a description from another ticket showing how to use addr2line:

Also for errors like this you can do some investigating with arm-none-eabi-addr2line:

Check if you have arm-none-eabi-addr2line set up by running "where arm-none-eabi-addr2line" in a cmd window.

This should return something like "C:\Program Files (x86)\GNU Tools ARM Embedded\4.9 2015q3\bin\arm-none-eabi-addr2line.exe"

If it does not return this, then there might be some issues with the gnuarmemb path configuration

Next step is to investigate what is in the R15/pc and R14/lr addresses

arm-none-eabi-addr2line -e <path to _build\zephyr\zephyr.elf> <0x000211a8> for r15/pc

arm-none-eabi-addr2line -e <path to _build\zephyr\zephyr.elf> <0x00018b3d> for r14/lr

2. Should give you what function call that causes the kernel panic deep down in the stack. Remember to replace "<path to _build\zephyr\zephyr.elf>" with your actual path

RE: Data access violation in Zephyr when accessing nPM1300 with nRF52832

helsing — Thu, 26 Oct 2023 13:27:31 GMT

Hi Daniel,

Have you tried arm-none-eabi-addr2line to get the code location?

For example:

arm-none-eabi-addr2line -e build/zephyr/zephyr.elf 0xFAULTING_ADDRESS

And insert 0x00008cf4 like this:

arm-none-eabi-addr2line -e build/zephyr/zephyr.elf 0x00008cf4

That should give you the code location. What is there should hopefully give us a clue.

https://manpages.debian.org/testing/binutils-arm-none-eabi/arm-none-eabi-addr2line.1.en.html

Please also see this ticket on how to handle fatal errors in zephyr.