RE: Hardfault happening in the SDK with BLE

Salmat — Thu, 16 Jan 2020 11:32:02 GMT

Hi,

I did not really tried to understand, but in the mean time I detected a function on my application not verifying the length of data I corrected, and I have not seen the bug any more ... witch could be what you explained.

Thanks for your response/time,

Regards,

RE: Hardfault happening in the SDK with BLE

Håkon Alseth — Mon, 13 Jan 2020 09:22:34 GMT

Hi,

The sections are located in RO data (ie: in flash), and the section_var library would then fetch a pointer to these and execute it.

Since you see a corruption in the p_observer (thus, possibly the "iter" variable), it points to a stack corruption of some kind.

Q1: Do you have a log / picture of the cpu registers when this occurred? In your screenshot, I am not seeing the SP (R13) content.

Since this occurs quite early in the process, it might not be a stack corruption, but a free running pointer (array going out-of-bounds or something) that happens to corrupt global memory.

Q2: Is the sections handled in the linker script? Could you share your linker script?

Kind regards,

Håkon