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.

MSP430FR2533: MCU Unresponsive to i2c communication until power cycle

Part Number: MSP430FR2533

Hi,

The MSP430FR2533 i2c slave stops responding to the master (QCC5124). We have an extremely high return rate of units experiencing this problem at 6%.

Some background on how we're using the MSP:

We are periodically sending i2c commands to the MSP to illuminate LEDs and read the ADC. The ADC is read when the MSP asserts an IO pin to inform the master that the ADC reading changed.

We will also read a firmware version number from the MSP during the Master init sequence. If the version number is different, we will command the MSP in BSL mode, and update the firmware via i2c. This should never be triggered since the Master firmware has never been updated since mass production. This is in place for future OTA updates, of which we have yet to push an update.

Please recall the following thread where we concluded that the ADC clock was configured out of spec:https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/844103 

Could this have something to do with what we're seeing?

In an attempt to determine root cause, I think we shouild start be determining what state the MSP430FR2533 is currently in but I'm not sure where to start, will you be able to assist with this?

Thanks!

**Attention** This is a public forum