# Trace Utility on HCS12 C32

**URL:** <https://forums.freertos.org/t/trace-utility-on-hcs12-c32/1144>\
**Category:** Kernel\
**Created:** [October 18, 2005, 11:51am UTC](https://forums.freertos.org/t/trace-utility-on-hcs12-c32/1144 "2005-10-18T11:51:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [October 18, 2005, 11:51am UTC](https://forums.freertos.org/t/trace-utility-on-hcs12-c32/1144/1 "2005-10-18T11:51:24Z")

</div>

**[dalehumby](https://sourceforge.net/u/dalehumby/)** wrote on [Tuesday, October 18, 2005](https://sourceforge.net/p/freertos/discussion/382005/thread/32b226b2/#6921):

Hi.

I am using this ports demo and would like to put in a trace for learning purposes. I have looked at the API help and read the article [https://sourceforge.net/forum/message.php?msg\_id=3323682](https://sourceforge.net/forum/message.php?msg_id=3323682), but I need a little more help.

Where would be a good place to declare the buffer and to start the trace (vTastStartTrace)? What type decleration is correct for the buffer?

I defined char cBuf[500]; in the local variables section of main.c and the call to vTastStartTrace in vApplicationIdleHook before the for(;😉 loop.

However, at compile CodeWarrior claims there is no more RAM at location 0xFB9. I suspect this is due to the position of where I have declared the buffer.

Thanks and regards  
Dale

---

<div class="post-metadata">

**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\
**Post date:** [October 18, 2005, 1:15pm UTC](https://forums.freertos.org/t/trace-utility-on-hcs12-c32/1144/2 "2005-10-18T13:15:58Z")

</div>

**nobody** wrote on [Tuesday, October 18, 2005](https://sourceforge.net/p/freertos/discussion/382005/thread/32b226b2/#6921/56fd):

It is more likely that you just don’t have enough RAM left to create a 500 byte buffer, and that trying to do so is causing the data segment to overrun.

Check the map files to see how much RAM is left.