FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [March 2007 Threads] Unexpected Breakpoint on a HCS12Posted by JimK3038 on March 3, 2007 I’m running FreeRTOS on a Freescale HCS12 processor. I’m living in constant fear of the “Illegal Breakpoint” as my application gets larger and larger (pushing 64k). Usually I can revert to an older version of my source code to get my application working again.
My questions is, is there a way to look at the stack area after the illegal breakpoint for clues? At a minimum, it would be nice to know which was the active task when the problem occurred.
Thanks, Jim
RE: Unexpected Breakpoint on a HCS12Posted by Nobody/Anonymous on March 3, 2007 Inspect the pxCurrentTCB variable in the debugger. This will tell you info on the currently running task. You can inspect pxCurrentTCB->pxStack to see the stack used by the task. The stack is set to all 0xa5 when the task is created so if there are no 0xa5 left then overflow has happened.
RE: Unexpected Breakpoint on a HCS12Posted by Jeff Smith on March 6, 2007 I also use HCS12 (GCC version), and the thing I notice most is that a stack has overflown. Remember that when a stack is overwritten, it is likely that you don't notice until a task swap. The most useful thing I've done is to track where the bottom (start) of each stack is, so I can see which ones are running (or already ran) out of space.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|