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.

Tiva reboots Randomly - TIRTOS

Hi all,

HW: TIVA-C 1294C family

SW: custom softwre built on top of  TIRTOS.

Our device is rebooting randomly and we are not able to define any pattern of reboot.  It reboots randomly some time for 2 mins/5 mins/10 mins/ when it kept aside in Idle mode.

We have 7 tasks defined with  2 task with stack size of 16KB each. When we reduced  the stack size of these 2 tasks to 8KB each, random reboot behaviour is not observed any more. Tested for more than 4 hours and never observed reboot.

Can some one give a clue to identify the cause for the same in RTOS?  

Thanks . 

  • Hello Ravi,

    There is a Reset cause register in system control called SYSCTL.RESC. Can you check what is the value of this register as it will indicate what is the cause of the reset.

    Regards

    amit

  • Ravi,

    Can you check to make sure your other 5 tasks are now blowing their stacks?

    Judah

  • And check that you don't run into a watchdog timeout.

  • HI Amit,
    Thanks for the inputs . But sorry. I forgot mention the cause of reset.
    Basically we enabled the watch dog & because of this watchdog system reboots.

    In a thread we refresh the watch dog periodically. But when system hang somewhere, wtach refresh is not called and hence it reboots. But, the issue what I am trying to understand is why it hangs & where it hangs !

    If I enable debug logs, it never reboots.
    Also, i I connect to CCS and keep it for running, it never reboots. IT reboots only in release mode .

    We have turned all optimizations optimation option to OFF to make sure that is not the reason.
  • Hi jadhavang,
    Thanks for the reply.

    We are running for watchdog timeout. But question is why only in release mode? Is ther e iny issues of timing in threads? We are stuck
  • Actually, a watchdog timeout is an application problem (including the OS), and not a MCU problem. Only you can specify what watchdog setting is appropriate for your application.

    But question is why only in release mode?

    Debug and Release mode can have (very) different build settings and components included.

    Perhaps the debugger makes some initialisations/settings that are missing when running standalone ? That would apply when running in the debugger.

    Or it could be an optimisation issue. If you use a windowed watchdog, you may trigger it too early in release mode.