TMS320F28377S: For higher baud rates, SCI RX buffer is getting corrupted.

Hi Chris,

The only thing approaching an example for RX in non-FIFO mode is the following function in the driverlib:

//*****************************************************************************
//
//! Determines if there are any characters in the receive buffer when the
//! FIFO enhancement is not enabled.
//!
//! \param base is the base address of the SCI port.
//!
//! This function returns a flag indicating whether or not there is data
//! available in the receive buffer.
//!
//! \return Returns \b true if there is data in the receive buffer or \b false
//! if there is no data in the receive buffer.
//
//*****************************************************************************
static inline bool
SCI_isDataAvailableNonFIFO(uint32_t base)
{
    //
    // Check the arguments.
    //
    ASSERT(SCI_isBaseValid(base));

    //
    // Return the availability of characters with FIFO disabled.
    //
    return(((HWREGH(base + SCI_O_RXST) & SCI_RXST_RXRDY) ==
            SCI_RXST_RXRDY) ? true : false);
}

Which is basically just returning RXST.RXRDY.

I guess what should be done in non-fifo RX ISR is to check this flag at the beginning to determine if the ISR was caused by RXRDY or a break detect.  If caused by break detect, instead of reading data you should issue a module SW reset.  I don't think that helps you other than potentially explaining why the data is corrupt.  

I'll submit for a non-fifo RX example to be written.  This will probably take awhile to get written and released.