HardFault while using the DEBUGOUT function

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HardFault while using the DEBUGOUT function

306 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by run on Wed Dec 18 15:42:36 MST 2013
Hi,

I am porting the CC3000 to LPC4337, everything is working if I disable the debugging or I remove all the DEBUGOUT macro from the code otherwise I am getting a HardFault. I am using FREERTOS. What can be the problem.
Labels (1)
0 Kudos
3 Replies

282 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by run on Thu Dec 19 13:19:52 MST 2013
There was a problem with the stack size, after I increased it is working
0 Kudos

282 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by wellsk on Thu Dec 19 10:57:16 MST 2013
A FAQ was just added - minutes ago - for DEBUG* function support in LPCOpen (this is LPCOpen?). http://www.lpcware.com/content/faq/lpcopen-debug-inputoutput-support

I would guess your trying to use the DEBUGOUT function and the UART or device used in that function is not correctly setup. You may need to call DEBUGINIT() if you aren't calling Board_Init().
I hope the FAQ will help.
0 Kudos

282 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Thu Dec 19 06:04:31 MST 2013
I don't know what DEBUGOUT does. However, I would start by looking at your stack usage. If you are using FreeRTOS, every task will have a stack, and maybe the use of this macro increases the stack usage, so that it blows the stack on starts overwriting other memory.
0 Kudos