• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 79 subscribers
  • Views 339 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

msp430 is resetting

manish bhatt1
Intellectual 785 points
Other Parts Discussed in Thread: MSP430F5338

Hello

I am using msp430f5338 in my new design.

Sometimes I found that msp is resetting on runtime.

Till now I have'nt seen this problem in debug mode so I am unable to find out that exact reason of reset.

Power supply and ground are stable and watchdog is disable at starting of code.

Pls let me know the exact cause of reset.

Thanks

Manish

  • 0
    TI__Guru 68116 points

    Hi Manish,

    I think we are going to need more information to help you out. It is hard to know what could be causing this without knowing more about your code or about your hardware setup. Are you using a TI target board or your own board?

    Fortunately this is a 5xx device - you should be able to find some information about the type of reset occurring by checking the value in SYSRSTIV at the beginning of your code. If you can only get the issue to occur when running stand-alone, you can have SYSRSTIV read at the beginning of your code and then output it somehow on pins (a # of pin toggles, or output as a hex value on some free pins for example). This will help give you a clue as to what things could have caused the reset - you can find a table of SYSRSTIV values and possible reset causes in the datasheet (Table 12) www.ti.com/lit/gpn/msp430f5338 , and there are many other threads on this forum discussing SYSRSTIV if you want an example of checking it.

    Regards,

    Katie

  • 0
    Guru 227245 points

    Katie’s suggestion of checking SYSRSTIV for the cause of the last reset is a good one. However, in most cases, it will not give you a direct answer.

    The most usual reasons for sudden and non-deterministic resets are
    - stack corruption (due to out-of-bounds array writes)
    - stack overflow (too much code nesting, too many local variables, recursions and worst of all, interrupt nesting)
    - a missing ISR for an enabled interrupt. (this is usually deterministic, if the interrupt source is deterministic. But in some cases, like port pin interrupts or error interrupts, it may run for quite a long time until the interrupt comes and crashes the system)

**Attention** This is a public forum