• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 197 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.

MSP430FR6047: msp430FR6047

Asaf Tvito
Genius 4010 points
Part Number: MSP430FR6047


Tool/software:

Hi,

I built a sensor project based on the example of ultrasonic water flow measurement. The MSP430 is connected by i2c to another CPU which wakes up the MSP430 from sleep by reading the ultrasonic sample every 1 minute in I2C.
After a few days the MSP gets stuck and only re-burning can release it.
I would appreciate help solving the problem

  • 0
    TI__Genius 16030 points

    Hi Asaf,

    Have you tried connecting a debugger to the device, or outputting any error information?

    You need to determine whether the device has encountered an error condition, or if it is hanging.

    If the device has an error you can use the error information to diagnose the problem and take the proper steps to get the readings again. You may just need to reinitialize the USS modules or I2C module.

    If the device is hanging (if the program counter has run off into the weeds, device encountered a hard fault, etc.) then you need to review your application code to see where the point of failure is.

  • 0 in reply to Dylan OBrien
    Genius 4010 points

    when the device is stuck game over only reprograming the device takes it out , even power down is not work.

  • 0 in reply to Asaf Tvito
    Guru 42145 points

    If you can't run it under the debugger you can do things like:

    Toggle a GPIO in the main loop as a heartbeat.

    Toggle a GPIO in the default stub to see if some errant interrupt is triggering

    If the sensor is not a simple ADC read, set a GPIO when you start talking to the sensor and reset the GPIO when you finish to see if you are hanging up during the communication.

    As a possible solution, you can set up the Watch Dog Timer to reset the board if the dog isn't fed periodically.

  • 0 in reply to Keith Barkley
    TI__Genius 16030 points

    Hi Asaf, 

    I am still not clear on how exactly the device is failing. When you say the device is stuck I assume you mean that it does not respond over I2C. As Keith mentions, if you are unable to access via debugger there are a few other ways to get information on the device status. 

    You may want to try flashing your application code to an EVM so you are able to debug it, then see what is going on internally to the device to diagnose the issue. Debug access is going to help to address the issue quite a bit.

  • 0 in reply to Asaf Tvito
    Guru 42145 points

    Are you sure it is not the sensor that is stuck? A power-cycle should start re-running from main and start fresh.

**Attention** This is a public forum