• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 79 subscribers
  • Views 187 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.

MSP430F67691A: Issue with MSP430F67691A – Device Stops Working After Long-Term Operation

Ankush
Intellectual 640 points

Part Number: MSP430F67691A

Dear TI Support Team,

I am using the MSP430F67691A microcontroller in one of our products. We are facing an issue in the field and would appreciate your guidance.

The problem occurs as follows:

The device operates normally for several weeks (around one month).

Suddenly, the unit turns off and does not start again.

The MCU does not run the application code even after power cycles.

However, once we reprogram the MSP430F67691A using our debugger, the device starts working normally again.

We have checked our firmware and hardware, but we are still not able to identify the root cause. 

Could you please help us with the following?

Recommended methods to diagnose unexpected shutdown or startup failures on the MSP430F67691A.

Details on how to properly read and interpret the reset-cause register for this device family.

Any known issues related to long-term stability, brown-out conditions, FRAM/flash writes, or bootloader behavior.

Best practices for ensuring reliable power-up, brown-out protection, and preventing memory corruption on this MCU.

Suggestions for logging reset cause or detecting abnormal resets during runtime.

Thank you in advance for your support. We look forward to your guidance to resolve this issue.

  • 0
    TI__Expert 8155 points

    Hi, thanks for reaching out! Is this happening across multiple ICs, or is it just a single one? What conditions is the device operating in (i.e. any power supply interruptions or variations, any external signals that might be causing odd behavior, etc.). I don't think this would be a code issue since you say you are able to run your program successfully.

    What is the end application here? In metering applications, it could be possible that there is some strong EM emission may be causing the device memory to become corrupt, or can interfere with the power supply lines/signal lines within a device, causing voltage fluctuations or "noise spikes". These disruptions can cause the CPU to execute instructions incorrectly or trigger unintended write/erase operations in the flash memory, leading to data corruption.

**Attention** This is a public forum