• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 225 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F6726A: Erreta USCI37 further information needed

Rifat Sahiner
Prodigy 20 points
Part Number: MSP430F6726A

Hello,

I'm having I2C communication fault that happens very rarely. USCI37 on erretasheet seems like a possible cause for the fault but explanation on the document is not sufficient. I have questions below;

What does "bus stall" means? Does it means clock or data lines keeps on a certain level or else?

When the error happens does it only effects current or next read or all other communication until I2C or MCU reset?

About workaround 1; what if first read was okay and second read on RXBUF causes the error?

Thanks.

  • 0
    TI__Mastermind 26420 points

    Hey Rifat,

    Let me take a look at the errata and get back to you in the morning.  

    Thanks,

    JD

  • 0
    TI__Mastermind 26420 points

    Hey Rifat,

    The only time I saw this errata, the clock was getting stuck held low which obviously broke the communication and remained until the I2C module was reset.  

    This is an interesting question on the errata, and I don't have the information.  I would assume that either it's not possible for the back to back reads to stall the I2C state machine or it's so statistically unlikely that it is irrelevant.   

    I will say, this is a well-known errata as this USCI module is across a large number of MSP430s and this workaround has been implemented by many customers without issue. 

    Thanks,

    JD

**Attention** This is a public forum