This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

  • TI Thinks Resolved

CCS/TMS570LC4357: Break debugger on SP specific value

Part Number: TMS570LC4357

Tool/software: Code Composer Studio

Hi, I was wondering if it's possible to get a break in the debugger if the stack pointer get a certain value. Memory location R/W, no problem, PC no problem, but I am interested to know where the stack pointer gets to a given value (or less-than). Thanks!

  • Hi Attila,
    Not the SP itself but you can set a watchpoint on the __stack symbol, that corresponds to the lowest address of the stack. This could help with what you analysis. Please see the below link for more details:
    processors.wiki.ti.com/.../Checking_for_Stack_Overflow

    Thanks
    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    The problem is that I get a predictable crash when my SP reaches a certain value that is NOT the bottom. Say my stack is between 0x..0000 and 0x..2500. When crash happens, the SP is always 0x..2400 and the content is all zeros. I really wanna catch BEFORE the SP gets 0x..2400... Thanks! 

  • In reply to Attila Vass:

    Wouldn't setting a watchpoint for accesses at address 0x2404 work in this case?

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    Nope. :-(

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.