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

MSP430FR2433: Firmware getting corrupted in the field

Danilo A.
Mastermind 30780 points
Part Number: MSP430FR2433


Hi Team,

May we ask your help regarding our customer's inquiry below.

We have a Gateway device in which MSP430 runs along with a Raspberry Pi. Raspberry Pi and MSP430 communicates over I2C bus. We've enabled I2C BSL for firmware updates. 

Now after operating for few months in the field - MSP430 stops communicating with Raspberry Pi. Even full hard reboot of the device does not help. 

We suspect that somehow Firmware is getting corrupted in the field - so we brought one such device in our Lab and after re-flashing - it starts working. 

There is another category of problem - where MSP430 is visible on I2C bus and it gives incorrect data. In our case - all the application specific registers return a value of 0x51. 

Can someone suggest - what might be happening with the devices? 

Regards,

Danilo

  • 0
    Guru 25185 points

    This is an FRAM device so it is not that difficult to corrupt the code. Are memory protection features of the part being used to protect the firmware?

    It is possible but unlikely that FRAM errors are the cause. The ECC hardware can correct all single bit errors and detect most multi-bit errors. Enable the correctable error interrupt and count events. These should be rare so if you get a bunch you need to find out why.

**Attention** This is a public forum