Hardfault ble_nus_send_data

[Sergy]

Hello!

Im getting a hardfault when trying to send 10 bytes data via NUS. I receive the data, but the app crashes:

0> <error> hardfault: HARD FAULT at 0x00000000
0> <error> hardfault: R0: 0x20008170 R1: 0x00000000 R2: 0x00000000 R3: 0x00000002
0> <error> hardfault: R12: 0x000001F4 LR: 0x0003F75F PSR: 0x00000000
0> <error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.

Im using FreeRTOs + SD132 v 6.1.1 and SDK 15.3

Any idea where to look at?

[Susheel Nuguru]

This looks like a POP instruction gone wrong, mostly happens when the POP instruction put garbage values in PC to return to the previous context. Hard to say what caused the stack corruption with the information you provided. Can you run your program on nRF52840 to see if this problem goes away. If it does, then we can be sure that this is caused by a stack overflow

[Sergy]

Unfortunately cant run on nrf52840 since its our own device with plenty peripherals. any other suggestions?

Im thinking to remove DFUS and may be this would provide enough memory?

[Susheel Nuguru]

with FreeRTOS you can attempt to catch a stack overflow using these two methods. They are not 100% effective but still are good ways to catch stack overflow a few times.

First try the above method to see if the RTOS can catch an overflow, if not, then please remove the modules that you do not need to reduce the stack usage of your app.

[Sergy]

I actually had this configured to method 2 already. I tried with method 1, but no stack overflow was detected.

I just also removed DFU service, but it didnt help.

Would you have more suggestions?

Additional piece of info: Im using device as Central and Peripheral with 2 links maximum.

[Susheel Nuguru]

Can you give me the project after you disable the DFU and as minimalistic as possible to be able to try to dig a bit deeper on my desk out of my own curiosity?

Can you comment out all places where you have __WFE() instruction and let the device run in full power? 

If that helps then I can discuss the reason for that behavior and the workaround.