Hardfault in FreeRTOS button code

RE: Hardfault in FreeRTOS button code

Pandurang Chauhan — Tue, 07 Dec 2021 04:39:33 GMT

This is resolved. May be the code was not properly modified for the button.

RE: Hardfault in FreeRTOS button code

Susheel Nuguru — Tue, 10 Aug 2021 06:09:10 GMT

So the strange behavior is seen when you change the name of the files/project only? The code compiles OK?

This is very strange, Seems like a Segger issue but I am curious, can you please attach your project so that I can test it out?

RE: Hardfault in FreeRTOS button code

Pandurang Chauhan — Mon, 09 Aug 2021 06:04:28 GMT

Thanks Susheel for your reply.

button interrupt priority is set as below (in sdk_config.h)

#ifndef NRFX_GPIOTE_CONFIG_IRQ_PRIORITY
#define NRFX_GPIOTE_CONFIG_IRQ_PRIORITY 6
#endif

By the way, there is one good news. Earlier I have added USB MIDI functionality and then modified for buttons. Now, I have started again. In that, I have first checked button functionality in usbd_ble_uart_freertos example and found working. After that I have modified the main.c file for USB MIDI related changes and found that two buttons are working as expected.

Next I was changing the name of project, solution, project and folders. I have changed all at once and to my surprise, the code has same behavior (not working) as mentioned in my first (main) post.

So, I changed again and kept all the names same as earlier and found working again when checked. So, I changed the names one by one, and found that when I changed the project name from "usbd_ble_uart_freertos_pca10056_s140.emProject" to some other, the code was not working. So, for now, I have kept the project name as default.

What can be the reason? There should not be project name dependency, right?

One more thing, when I gave my code to my colleague, the same code is not working. He has Segger version 5.50b and I have 5.50d.

Is there any dependency? What can be the reason?

RE: Hardfault in FreeRTOS button code

Susheel Nuguru — Fri, 06 Aug 2021 13:49:31 GMT

What is the priority of the button interrupt handler you have? (Check NRFX_GPIOTE_CONFIG_IRQ_PRIORITY in sdk_config.h file)

You are seeing an assert inside the softdevice at address at 0XA06. This normally should forward this handling to the application app_error_fault_handler (second argument to sd_softdevice_enable) function. If you are using the default fault handler from the SDK, it should throw out some more information regarding the assert on the log output (depending on whether you have enabled logs and built the code with DEBUG macro enabled)