• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 381 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CC1310: TIRTOS- Ti15.4 Stack does not function properly on adding another task

CC1310: Ti15.4 code crashing

Sabin John
Intellectual 475 points
Part Number: CC1310

Hello 

I have added a new task to the TI15.4 code . The 4 tasks are

Mactask (priority=3; stacksize=1024)

apptask (priority=2; stacksize=960)

mytask (priority=1; stacksize=1024)

idle task (priority=0; stacksize=512)

The code however is crashing when the flow is as such

Cllc_process->Cllc_events & CLLC_STATE_CHANGE_EVT->processState(Cllc_coord_states_t state)
-> case Cllc_coordStates_scanEdCnf:->sendStartReq->ApiMac_mlmeStartReq->ASSERT

Is there any possible reason for this? What should I look out for? I have also attached screenshots of the callstack

Regards,

Sabincallstack.docx

  • 0
    TI__Mastermind 25810 points

    Hey Sabin,

    I wasn't able to make any conclusions from the call stack you attached. What functions are you performing inside the newly created task? Do those functions overlap with any that may already be performed in the 15.4 code?

  • 0 in reply to Ammar N
    Intellectual 475 points

    Hey Ammar,

    Thank you for responding!

    In our new task we are performing some uart related operations, rx and tx over uart. When we observed that the code is crashing, we commented out all the code in the While(1) loop in the new task and just added a tasksleep of 50ms, to see the operation but it was still crashing from the same function call. 

    We haven't modified the internal functionality of both the apptask and mactask. We have added a task sleep of 50ms after collector process in the app task while(1). When our new task is not initialised (commented out from init, effectively only 3 tasks in picture, mactask, apptask and idle) then all the Ti tasks are performing normally without any crash. 

    What I was trying to find out is, as you can see in the call stack Assert is called from FHAPI. Is there any scenario where this FHAPI may cause a crash, any prerequisite condition that is not fulfilled that is causing it to crash from there. I am unable to step into that function to try and debug.

    Sorry if my inputs are not of much help. Let me know if you need to know anything specific.

    Thanks,

    Sabin

    memory usage

  • 0 in reply to Sabin John
    TI__Mastermind 25810 points

    We certainly don't intend for the api to crash under any circumstance. For this reason, I'm trying to reproduce the issue on my end, but am unable to do so.

    I went ahead and added a new task in main() that just counts and sleeps (I call Task_sleep(50)). Any advice to help reproduce would be helpful.

  • 0 in reply to Ammar N
    Intellectual 475 points

    Hello Ammar,

    Increasing the stack size resolved my issue.. You may close the thread. Thank you for your time! 

    Regards,

    Sabin