Revision(s) Affected: 0, A

If the XRDY bit is used to properly gate writes to the DX2/DX1 registers, this condition does not occur.

Per the operation of the McBSP, a write to the DX1 data transmit register automatically clears the XRDY bit, indicating a not-ready status. Once this data is transferred to the internal transmit shift register (XSR1), the McBSP HW sets the XRDY bit to indicate a ready status, and new data can be written to DX2/DX1 data transmit registers.

If the set and clear of XRDY occur on the same CPU clock cycle, the XRDY bit remains cleared and the new data in DX2/DX1 is not transmitted.

In this state of XRDY = 0, the McBSP will appear not-ready indefinitely.

Any subsequent writes to DX2/DX1 will behave normally and the XRDY bit will function normally.

Workaround: When transmitting multiple words of data using the McBSP module, the XRDY bit in the SPCR2 register should be polled before writing new data to the DX2/DX1 registers in order to prevent overwriting. For those modules that do not have access to the XRDY bit (such as the DMA controller), the XINT interrupt inside the McBSP module can be configured to reflect XRDY (through the XINTM bits in the SPCR2 register) and this can also be used to gate writes to the DX2/DX1 registers. This also ensures the XRDY bit is not set and cleared on the same CPU cycle, causing the above “indefinite not-ready” condition.

If the system allows multiple bus controllers (such as the C28x CPU and the DMA controller) to write to the DX2/DX1 registers, then the ready-state of the XRDY bit should be validated prior to passing control of the McBSP to a different bus controller. This ensures that the state of XRDY is accurate and the simultaneous set/clear action does not occur.