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.

CCS Eclipse stack trace does not work if stack is in far RAM

Other Parts Discussed in Thread: MSP430FR5969, MSPWARE, MSP430F5659

I'm using an MSP430FR5969 and trying to walk through code with the CCS debugger.  However, I have noticed the CCS will not yield a stack trace more than one level deep.  See the screenshot:

My stack is located at 0x10020, in far RAM.  For various reasons I cannot use the low RAM in my application.  I believe this is the cause of CCS's confusion, as when I move the stack into near RAM as a proof of concept, I get a multi-level stack trace.

I have reproduced this behavior in both CCS 5.5 and 6.0.

I believe this to be a bug in CCS - can someone confirm this, or suggest a workaround?  Is there some way to tell CCS to look into far RAM for the call stack?  This is very problematic for debugging.  Thanks.