CCS/TMDSRM48HDK: Debug Call Stack - "next frame is identical to an existing frame"

Hello,

Here is my .out file:

2262.MUX.zip

I'm creating a periodic task which toggles leds. The toggle function is called through 3 different functions:

void function3(void)
{
    BSP_LED_Toggle(2);
}
void function2(void)
{
    function3();
}
void function1(void)
{
    function2();
}

static void AppTaskStart (void *p_arg)
{
    OS_ERR err;

    /* Initialize the Tick interrupt */
    OS_BSP_TickInit(OSCfg_TickRate_Hz);

    BSP_LED_Off(0);
    while (1)
    {
        BSP_LED_Toggle(1);
        function1();
        OSTimeDlyHMSM((CPU_INT16U) 0,
                      (CPU_INT16U) 0,
                      (CPU_INT16U) 0,
                      (CPU_INT32U) 500, // 500ms
                      (OS_OPT )OS_OPT_TIME_HMSM_STRICT,
                      (OS_ERR *)&err);

        if (err != OS_ERR_NONE)
        {
            BSP_LED_On(6);
        }
    }
}

Here is the result when i place a breakpoint in function3:

Thanks,

Bastien

Hi Bastein,

The error msg on the call stack is a bit misleading.

If you were running CCS v7, you will see this.

I check the debug info in the object file. The compiler did not generate any information on how to unwind the callstack beyond the second frame.

I will file a compiler bug.

-Raymond

Hello,

So it's a compiler bug? I must wait for an update?

Thanks for your help,

Bastien

Hi,

We are going to need a reproducible test case that we can compile.  Also, this forum post will be moved to the compiler forum.

If a bug is found, the branch you are using, ARM CGT v5.2.x, will not be updated with a patch because it is reactive.  Only active branches will be patched with the fix.  In the meantime, you can try compiling your code with a later branch to see if the problem still persists.  

Thanks,

Anna Youssefi

Compiler Support Team