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.

MSPM0G3507: Strange I2C Startup/Reset Behavior (Controller Mode)

Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

I'm working with a customer that is describing their symptoms as follows:

The reason I wanted to try the latest syscfg and sdk is that I am having an issue with the I2C ports. Sometimes after a power cycle they just stop outputting anything. The code is looping on the routines to write slave device, but I see nothing on the ports. They are pulled up with 4.7K resistors and I can pull them low with a 470 ohm resistor. So they are not shorted. Currently they are on the MFCLK. IF I leave everything else the same and switch to BUSCLK, then the ports toggle, but I do not get full functionality still. I can read and write a few registers, but eventually it starts failing again.

Should be noted that once in this state, even reflashing does not restore the device. To get back to a good state, I have to go back to an old load and flash the device. Still does not function, but then if I power cycle it will be fine again. If I then load the FW that has issues, it will run fine maybe for a few power cycles, maybe hours, but then crashes again.

Any suggestions on something to try.

I've spent quite a bit of time debugging I2C on the MSPM0 platform and have not run into anything like this behavior. Therefore, I'm suspecting something unique to the customers hardware or software. However, I'm at a bit of a loss as to what could be happening. I'm looking for some ideas for further investigation.

I'll reply with the SysConfig, SDK, and CCS version info once it is provided by the customer.

Thanks,

Stuart