• State Not Answered
  • Replies 5 replies
  • Subscribers 74 subscribers
  • Views 765 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 271158
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SD raises AppError with no details occasionally

Oleg Z

We're getting this strange AppError that is supposedly coming from the SD (considering the PC is correct)

App error: id: 0x00000001, pc: 0x0001505C, code: 0x00000715

I do not currently have an application that would reproduce the problem, nor do I have any special steps to reproduce the problem since there is no special pattern on when the app error happens.

The device is scanning BLE beacons 99.9% of the time. Disabling the scanning definitely helps, the error doesn't happen when BLE is off.
We're using FreeRTOS, SD (s140_nrf52_7.0.1_softdevice) and SDK v16.0.0.

My colleague was able to trace through the Cortex-M core registers, the Radio (BLE) interrupt is active when the app error occurs. 3 other interrupts are also pending at that time: SWI5 (software interrupt, no direct code references to it, so assumed to be used internally by softdevice), GPIOE and RTC1.

Parents
  • 0

    Hello,

    I do not currently have an application that would reproduce the problem, nor do I have any special steps to reproduce the problem since there is no special pattern on when the app error happens.

    The transient nature of this error makes it very hard to debug. You mention that this happens occasionally, could you elaborate on what you mean by this - every hour, or every week?
    Could you also elaborate on the behavior you are seeing when this error occurs - does the device reset, for instance?
    Are you using a custom board, or and nRF52840 DK? If custom board, do you have access to a debugger, so you may run the code and see where it gets stuck or fail?

    Furthermore, you mention that this only happens when the SoftDevice is active. Could you tell me some more about what the SoftDevice is doing at this time - is it only scanning for beacons? What does it do with the information it receives from the scanning?
    Could it be that a buffer overflows, or otherwise causes a function to return a non-NRF_SUCCESS error code directly following the scanning?

    Looking forward to resolving this issue together!

    Best regards,
    Karl

Reply
  • 0

    Hello,

    I do not currently have an application that would reproduce the problem, nor do I have any special steps to reproduce the problem since there is no special pattern on when the app error happens.

    The transient nature of this error makes it very hard to debug. You mention that this happens occasionally, could you elaborate on what you mean by this - every hour, or every week?
    Could you also elaborate on the behavior you are seeing when this error occurs - does the device reset, for instance?
    Are you using a custom board, or and nRF52840 DK? If custom board, do you have access to a debugger, so you may run the code and see where it gets stuck or fail?

    Furthermore, you mention that this only happens when the SoftDevice is active. Could you tell me some more about what the SoftDevice is doing at this time - is it only scanning for beacons? What does it do with the information it receives from the scanning?
    Could it be that a buffer overflows, or otherwise causes a function to return a non-NRF_SUCCESS error code directly following the scanning?

    Looking forward to resolving this issue together!

    Best regards,
    Karl

Children
No Data
Related
Terms of service