Hardfault for simple freeRTOS application

RE: Hardfault for simple freeRTOS application

himanshu pande — Fri, 24 Mar 2017 10:11:34 GMT

Hi Aryan, I did lot of mix and match with all the above options and its CFLAGS += -DSOFTDEVICE_PRESENT option that causes the trap. Rest all options don't affect the system at all. Is this a bug or is this normal behavior? i.e. dont enable softdevice when we don't use it.

RE: Hardfault for simple freeRTOS application

himanshu pande — Fri, 24 Mar 2017 09:56:56 GMT

How is the option -D__STACK_SIZE related to configTOTAL_HEAP_SIZE parameter in FreeRTOS?

RE: Hardfault for simple freeRTOS application

Susheel Nuguru — Thu, 23 Mar 2017 21:14:38 GMT

seems like you are getting memory corruption in the stack. Set the heap size to 0 and increase the stack by 1KB and enable back these options to see what happens.

RE: Hardfault for simple freeRTOS application

himanshu pande — Thu, 23 Mar 2017 08:50:02 GMT

I have got the software working. It was with the compiler options.

I had following compiler option other than blinky freeRTOS project:

CFLAGS += -DSOFTDEVICE_PRESENT

I removed this option and the tasks arrive without glitches.

(Similarly for ASMFLAGS)

So, in conclusion, do not enable softdevice if your project doesn't use it.

RE: Hardfault for simple freeRTOS application

himanshu pande — Thu, 23 Mar 2017 08:46:53 GMT

I have already added that code to hard fault handler which generated additional log like stacked registers and trap related registers in cortex m4.

RE: Hardfault for simple freeRTOS application

butch — Wed, 22 Mar 2017 15:58:43 GMT

I think there is code on the web for a hard fault handler that gives more information about the fault by putting the PC and other info (even a full stack trace?) in memory where you can examine it from the debugger. Does the hard fault handler from Nordic (in their /library directory of the SDK?) give more information than the default hard fault handler? Its not simple and it is tedious, but it is possible to examine the stack from the debugger.

RE: Hardfault for simple freeRTOS application

Petter Myhre — Wed, 22 Mar 2017 14:55:25 GMT

What chipset and SDK version are you using?

RE: Hardfault for simple freeRTOS application

himanshu pande — Tue, 21 Mar 2017 10:42:26 GMT

Here is some further insight into the issue as I refer this FreeRTOS_Debug link.

HARDFAULT:ERROR:START OF FULL LOG

HARDFAULT:ERROR:R0 R1 R2 R3 R12 : 0x0 0x20001950 0x10000 0x200020c8 0xa5a5a5a5 HARDFAULT:ERROR:LR PC PSR BFSR : 0x8 0x8 0x6000000b 0x200 HARDFAULT:ERROR:CFSR HFSR DFSR AFSR MMAR BFAR : 0x20000 0x40000000 0x0 0x0 0xe000ed34 0xe000ed38

HARDFAULT:ERROR:END OF FULL LOG