RE: Bus fault sometimes when reading ADC

Håkon Alseth — Fri, 04 Dec 2020 11:01:44 GMT

Hi,

When you get a fault print out, you can map the addresses to actual code lines, atleast the values that are located in flash (from 0 -> 1MB).

The 0x19??? range is in the non-secure application space, which would be the ELF file in build-folder/zephyr/zephyr.elf.

If you use arm-none-eabi-addr2line (or manually check the zephyr/zephyr.map file), you can highly likely (but not always) get a file/line from the program if the lookup address is in flash.

Example:

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

R14 (LR = link register = 0x1940f) can also be interesting to look up.

[quote user="turboj"]Buffer overflow..?[/quote]

This is the most common one.

[quote user=""]E: Current thread: 0x20025b7c (unknown)[/quote]

Which thread is running on this memory address? You can check this in your map file.

If it is the main thread, you can try to increase the stack size in your prj.conf:

CONFIG_MAIN_STACK_SIZE=HIGHER_THAN_YOUR_CURRENT_VALUE_FOR_INSTANCE_8192

Kind regards,

Håkon

RE: Bus fault sometimes when reading ADC

Turbo J — Thu, 03 Dec 2020 20:36:24 GMT

[quote userid="54993" url="~/f/nordic-q-a/69072/bus-fault-sometimes-when-reading-adc"]the BFAR address is located in the SRAM (my assumption).[/quote]

Wrong assumtion. Those addresses are outside the SRAM address space.

Buffer overflow..?