Hello Jonathan, It seems that the UCTXIFG is stuck at a value of zero to indicate that the UCB0TXBUF is not empty and therefore a new value should not be written to it. This contradicts the UCBUSY while loop which, once cleared, indicates that the eUSCI is inactive. This behavior is the exact opposite of USCI41 errata which is documented for this device. Please see if slowing down your clock speed solves the issue. Otherwise you can try to remove the UCTXIFG while loops and depend solely on the UCBUSY bit. I will investigate this behavior further next week. Regards, Ryan
↧