TDA4VM: C66x Stack Size

Hello Porselvan,

Can we get more details on the project/end customer and the complete use case information here so that we can help prioritize this thread?

Thanks.

Hi Praveen,

We are working on developing a middleware which can be ported to different SoC's for an ASIAN OEM, its part of upcoming CES demo program.
As part of that middleware, we are creating a IPC receiving class which will receive the message from different cores and post that ipc message to a listener queue and another listerner task will read the messages from that queue and process it in that core.
This design we have tested for C7x core in TDA4 and its working perfectly, now when we port the same code for C6x its failing.

We are currently blocked on this, and not sure how to proceed. Instead of blind debugging if some pointers on this issue anyone can point us, it will be helpful for us

We suggest you make us aware of the TI PSDK RTOS and its documentation as much as possible. We must delay looking into anything outside this due to other priority items and limited bandwidth. However, we will look into this next week and get back to you with feedback.

Thanks.

Hi Praveen,

thanks for the feedback, I’m using RTOS SDK internally to have this design ready, any feedback on this issue will be more helpful for us.

Hello Porselvan,

Some basic quesiton -

Are you saying that both parent and spawned task has to access the same C++ queue?

Also where the parent task creating the C++ Queue? on the stack or on the heap?

Are you saying that gTskStackMain and gTskStackCmdQue the "task stack memory" that used use by the parent and spawned task?

Thanks.

Hi Praveen,

Are you saying that both parent and spawned task has to access the same C++ queue?

yes, I was able to access by passing this pointer as an argument to the task.

/* code */

    taskParams.stack         = gTskStackCmdQue;
    taskParams.stacksize     = sizeof(gTskStackCmdQue);
    taskParams.arg0           = static_cast<void *>(this);

    taskHandle = TaskP_create(workerTask, &taskParams);

So with the this pointer, I am able to access the that particular class instance queue using getter function.

Also where the parent task creating the C++ Queue? on the stack or on the heap?

Stack.

/* code */

//global variable

static uint8_t gTskStackCmdQue[8*8192]
__attribute__ ((section(".bss:taskStackSection")))
__attribute__ ((aligned(8192)))
    ;

//later in the class func

    taskParams.stack         = gTskStackCmdQue;
    taskHandle = TaskP_create(workerTask, &taskParams);

Are you saying that gTskStackMain and gTskStackCmdQue the "task stack memory" that used use by the parent and spawned task?

Yes right.,

With the above design I was able to communicate in the C7x core without any issues, when I take the same code and compile it for C66x and test, I'm getting NULL / 0 when I access the queue. Similar issue I observed in C7x as well, later it got resolved when I aligned the parent and spawned stack task  as 8192 (__attribute__ ((aligned(8192)))) when I define the stack:

    static uint8_t gTskStackCmdQue.

So is something like that any requirement is their for C66x? when the stack memory for the tasks has to be aligned in some particular value? or this issue is related to something else?