米6体育平台手机版

SLAZ616AA August 2014 – August 2021 MSP430FR68891

1
2
3
4
5
1. 6
2. 7
  1. 8
  2. 9
3. 10
11
1. 12
2. 13
3. 14
4. 15
5. 16
6. 17
7. 18
8. 19
9. 20
10. 21
11. 22
12. 23
13. 24
14. 25
15. 26
16. 27
17. 28
18. 29
19. 30
20. 31
21. 32
22. 33
23. 34
24. 35
25. 36
26. 37
27. 38
28. 39
29. 40
30. 41
31. 42
32. 43
33. 44
34. 45
35. 46
36. 47
37. 48
38. 49
39. 50
40. 51
41. 52
42. 53
43. 54
44. 55
45. 56
46. 57
58

6.42 USCI41

USCI Module

Function

UCBUSY bit of eUSCIA module might not work reliable when device is in SPI mode.

Description

When eUSCIA is configured in SPI mode, the UCBUSY bit might get stuck to 1 or start toggling after transmission is completed. This happens in all four combinations of Clock Phase and Clock Polarity options (UCAxCTLW0.UCCKPH & UCAxCTLW0.UCCKPL bits) as well as in Master and Slave mode. There is no data loss or corruption. However the UCBUSY cannot be used in its intended function to check if transmission is completed. Because the UCBUSY bit is stuck to 1 or toggles, the clock request stays enabled and this adds additional current consumption in low power mode operation.

Workaround

For correct functional implementation check on transmit or receive interrupt flag UCTXIFG/UCRXIFG instead of UCBUSY to know if the UCAxTXBUF buffer is empty or ready for the next complete character.
To reduce the additional current it is recommended to either reset the SPI module (UCAxCTLW0.UCSWRST) in the UCBxCTLW0 or send a dummy byte 0x00 after the intended SPI transmission is completed.

6.42 USCI41

Category

Function

Description

Workaround