• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 80 subscribers
  • Views 829 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.

FR23xx eUSCI bug in SPI mode

SeaFesse
Expert 2690 points
Other Parts Discussed in Thread: MSP430FR2311

Hi TI employee,

we 're now woking on a project with FR2311.  Go through the erratasheet , USCI41 is shown as followed.

This workaround is not a final solution.  In many applications, UCTXIFG/UCRXIFG can not take place of UCBUSY.  Especially , in some SPI-slave device with CS pin such as CC11xx \CC25xx\TRF797x , CS pin usually pull high when the BUS is idle(all data is already TX complete ,not just TX buffer is empty), so 

this workaround is more like a half-finished method. :(

  • 0
    Guru 100785 points
    This Workaround does look, um, "ready for an upgrade". TXIFG (by itself) really gives you nothing here. RXIFG works only if you count them; for high-volume Tx-only applications that can really slow things down.

    Perhaps the simplest method would be TXIFG in combination with "_delay_cycles(16*BRW)".
  • 0
    TI__Guru**** 219477 points
    Hi SeaFesse,

    The Device Erratasheet (SLAZ679) shows that this particular errata does not exist on MSP430FR2311 devices: www.ti.com/.../slaz679c.pdf

    I have also confirmed internally that this errata does not affect the MSP430FR2311. Have you done some SPI tests that prove otherwise? UCBUSY's unreliability on affected devices requires the customer to implement their own checks (UCTXIFG, UCRXIFG, & CS pin status) to see if any activity is occurring on the SPI bus.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Expert 2690 points
    Hello Ryan,
    Sorry ……Yes, you're correct. My colleague send me the screenshot, and I did not check it.
    The MCU mentioned here is MSP430i204x , they changed the selection of the chip , and did not inform me in time.
  • 0 in reply to SeaFesse
    TI__Guru**** 219477 points
    Hey SeaFesse,

    It has been confirmed that the eUSCIB module of i2040 devices is not affected by this errata so this might present an alternative, future revision fixes are not scheduled at this time.

    Regards,
    Ryan

**Attention** This is a public forum