Service discovery error after reconnect

Hi. 

I working a central and peripheral device which will connected with 4 sensors. sometime after disconnect and reconnect. the device will got fatal error in service discovery. I'm not sure the root cause. do you have any idea on it, there is the fatal error message 

[00:02:15.627,899] <err> os: ***** BUS FAULT *****
[00:02:15.627,899] <err> os:   Precise data bus error
[00:02:15.627,929] <err> os:   BFAR Address: 0x180024
[00:02:15.627,929] <err> os: r0/a1:  0x00000001  r1/a2:  0xfffffffe  r2/a3:  0x00000000
[00:02:15.627,960] <err> os: r3/a4:  0x00180020 r12/ip:  0x00000000 r14/lr:  0x00036d93
[00:02:15.627,960] <err> os:  xpsr:  0x61000000
[00:02:15.627,960] <err> os: Faulting instruction address (r15/pc): 0x00036d96
[00:02:15.627,990] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:02:15.628,021] <err> os: Current thread: 0x20002c78 (unknown)
[00:02:15.881,866] <err> os: Halting system

and there is my code for service discovery. 

 

Parents
  • Hello,

    The busfault is raised because the program is trying to access 0x180024 which is outside the valid memory range for FLASH on this chip (52833). You can look up the faulting address (Faulting instruction address (r15/pc): 0x00036d96) to find out where in the code this invalid memory access occurred.

    You can select this option in your build configuration to make debugging easier:

    Then start a debug session and use the call stack view after the crash is triggered to trace back to where the problem occurred.

    Best regards,

    Vidar

Reply
  • Hello,

    The busfault is raised because the program is trying to access 0x180024 which is outside the valid memory range for FLASH on this chip (52833). You can look up the faulting address (Faulting instruction address (r15/pc): 0x00036d96) to find out where in the code this invalid memory access occurred.

    You can select this option in your build configuration to make debugging easier:

    Then start a debug session and use the call stack view after the crash is triggered to trace back to where the problem occurred.

    Best regards,

    Vidar

Children
No Data
Related