hardfault issue with modified ble_app_uart_c example

[maxpmillion]

Greetings!

I have modified the "ble_app_uart_c" example from SDK v17.1.0 to be used to scan for and control our BLE-enabled devices via a terminal emulator. When we use the nRF52-DK as a simple UART-to-BLE bridge, we don't have any issues, but we also use the DK to send a firmware file over-the-air to upgrade our devices, and that's when I discovered this issue. Here's a brief overview of the update procedure:

A custom PC application reads 32-bit words from a text file and sends them one at a time to the nRF52-DK. The DK stores these values in a buffer until one page of data (264 bytes) is received. At that point the DK divides the page into 17 BLE packets, each containing 3 bytes of header data and 4 words of firmware data (except for the 17th one, which contains 2 words), and sends each packet to the device. The device then writes the page to flash and sends an acknowledgement, after which the process begins again until the entire firmware file is transferred. 

I am experiencing a hardfault during the OTA update at a consistent point (it gets ~20% of the way through the transfer, maybe 100 pages of data), and I am having trouble determining the root cause. Attached is a stack dump of when the fault occurs. If I am understanding this post  correctly, then the offending line of code is at 0x2'BB48, which, when cross-referencing the map file, is within nrf_queue_generic_pop(). I also attached the top-level application (see link below). I am using gcc, so the map file is under ble_app_uart_c/pca10040/s132/armgcc/_build/. I'm assuming this will eventually end up being my application code mishandling Nordic's libraries in some manner, but I was hoping that someone else might be able to take a look and offer some guidance for debugging this further. I tried to follow the hardfault handling instruction on the SDK InfoCenter page, but I don't think it made a difference. 

Any help would be greatly appreciated, at this point I'm out of ideas.

Thanks in advance,

Max

8863.ble_app_uart_c.zip

[Einar Thorsrud]

Hi,

I see you have logging enabled and HARDFAULT_HANDLER_ENABLED set to 1 in your sdk_config.h (assuming you are using the s132 project). Then we should get a sensible log output when a hardfault occurs. Can you check the log and upload it here?

[maxpmillion]

Good morning! 

I am indeed using the S132 project. Attached is the log from Segger's RTT Viewer. Let me know if that's sufficient.

Edit: I'm not seeing any additional messages regarding the hardfault reg dump in the log file. I'm also not seeing any objects named "hardfault", etc., in the map file. Is there another macro in sdk_config.h that I need to set? Or perhaps something I need to define in the makefile?

Upload1.log

[Einar Thorsrud]

Hi,

The log show a bus fault at 0x600832F4 which is not within a valid memory range for the nRF52832. Perhaps a buffer overflow somewhere or similar that has corrupted some data so that a pointer points to this invalid memory (0x600832F4 in this case)?

[maxpmillion]

Sorry for the delay. I have a curious development in this case. I asked another member of our software group to try to capture when this issue occurs and get his insight on reading the trace log. Long story short, we found that disabling optimizations (by removing the "-O3" flag from the gcc makefile) alleviated the symptoms. My coworker has set up a debugging environment in Visual Studio Code, and we found that the crash was occurring at line 255 in the attached screenshot. The value of "read_pos" was 0x20040000. Perhaps a dereference operation was not performed correctly? I think our next move will be to try to generate assembly listings to try to gain more insight.

For more data points, we also tried building with IAR, and we saw the crash no matter what the optimization level was (though we're not sure that the crash occurred in the same location in the binary). For now, we at least have a working solution, but we will continue to investigate.

[Einar Thorsrud]

Thanks for keeping me posted. It would be interesting to know the root cause of this.

[maxpmillion]

Hey Einar,

So just to close this loop - it turns out that the root cause is actually not that interesting. You were right in your suspicion that it was a buffer overflow issue. We were mishandling incoming BLE data in the case of OTA updates, and overrunning a buffer. Thanks for all your help and patience! 

[Einar Thorsrud]

Hi Max,

Thanks for letting me know what the root cause turned out to be.