• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 683 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.

problem with task stack

Bahubali%25252525252520Bill
Intellectual 385 points
Other Parts Discussed in Thread: MSP430F5438Hi, I have 3 tasks. When i run the code everything works fine , after expected result its showing "xdc.runtime.Error.raise: terminating execution". I have checked ROV, the stck size was completely full(it was red marked)(for 1 task and other two tasks works fine). I tried increase the size of stack with 1024 , 2048 but still getting same error(here too stack peak is almost full). So any solution???
  • 0
    TI__Mastermind 21645 points
    Hi Bahubali,

    I think the first thing to do would be to determine at what point does the crash occur. Can you share the application's callstack ? The callstack should show up in the Debug window. You can also determine each task's callstack by opening Task module's ROV view -> CallStack window.

    Does your application exit once its done with what its suppose to do and if so which task calls BIOS_exit() ? Also, are you using SysMin or SysStd as the System provider ?

    What board/target are you running your app on ?

    Best,
    Ashish
  • 0 in reply to Ashish Kapania
    Intellectual 385 points
    Sorry for late reply Ashish,
    After getting expected result i am getting this error. By changing the stack size of other tasks ,its working fine.
    May i know what is difference between SysMin and SysStd ?
    I am running this on MSP430F5438 board.
  • 0 in reply to Bahubali%25252525252520Bill
    TI__Mastermind 21645 points
    The System module as you may already know provides basic low-level "system" services like character output, printf-like output, and exit handling. SysMin and SysStd are support proxy modules that can be plugged into the System module. SysMin module is different from SysStd in that it maintains an internal buffer for storing the output and flushes the output only when System_flush() is called or the system exits. SysStd on the other hand calls the run time support library's putch() and fflush() functions. It does not internally buffer any data. SysMin is less intrusive for embedded applications.

    Best,
    Ashish