RE: Bus Fault - Precise Data bus Error

Sriharsha Desai — Wed, 02 Feb 2022 17:37:38 GMT

Hi Edvin, problem is solved. It is indeed because of accessing the BAD Pointer.

Thank you for the support.

RE: Bus Fault - Precise Data bus Error

Edvin — Fri, 28 Jan 2022 13:37:50 GMT

Hello,

Bus faults are a bit tricky debug, but I suspect that this is caused by a bad pointer somewhere.

You probably have gcc installed somewhere on your computer (in my case it is located under C:/Program files(x86)/GNU Tools ARM Embedded\9 2019-q4-major/

Inside there, there is a tool found in bin/ called arm-none-eabi-addr2line.exe Add the path to this folder to your environment variables. We will use it later.

Now, if you have recompiled your project since you posted this log, please check what the log says again. Some addresses may have changed.

[quote user=""]Faulting instruction address (r15/pc): 0x00049350
[/quote]

Check what address this line is pointing to. If it is still the same address, then open a cmd window in your build folder, and use the following command:

arm-none-eabi-addr2line -e _build/zephyr/zephyr.elf 0x49350

This will give you a file name and a line number.

You can also check addr2line on the address in your link register (LR/R14):

arm-none-eabi-addr2line -e _build/zephyr/zephyr.elf 0x0004934b

What you should see is that your link register will point to one function that calls the function in your r15/pc.

What functions do you find here? Do you see anything that could cause the application to fault? A bad pointer? A callback function that hasn't been set properly? Something trying to access a pointer that is out of bands?

Perhaps you can add some logging around that place, and see whether you get some log info before the crash?

Best regards,

Edvin