The firmware has hard fault and hung some times


I'm working on a project that uses RA6M5 MCU. The FSP version is 3.5.0. The FreeRTOS version is 10.4.3.

I found there is a hard fault after the firmware running a few hours. From the memory dump, the R14(LR) shows a function address. I found the function from the generated map file by IAR. Other than this R14, is there any other info that I can use from the hard fault dump print-outs?

Hard Fault

   R0 : 00032595   R1 : fffffff1
   R2 : 00000000   R3 : 2003f804
   R4 : 00000000   R5 : 2003f274
   R6 : 00000000   R7 : 2003f804
   R8 : a5a5a5a5   R9 : a5a5a5a5
   R10: a5a5a5a5   R11: a5a5a5a5
   R12: 00000002   R13: 200003c8
   R14: 00032595   R15: a5a5a5a5

                  0002516a 6100001e 
2003f804 000253c3 00000000 20001878 
2003d804 a5a5a5a5 a5a5a5a5 000221cb

Another problem is, after running a few hours, the firmware can be hung. As the watch dog timer isn't kicked, after about 30 seconds, the firmware will be reset. I tried to run the firmware from IAR. When it is hung, I pause the exection. I found it falls to prvIdleTask in "\Renesas\aws\amazon-freertos\freertos_kernel\task.c". I'm wondering what's the reason that the firmware runs into the Idle task. Is there a way to avoid it?


Parents Reply Children