印象中UART遇到ERROR要CREN關閉再開，但這顆MCU沒有CREN有類似的機制嗎?

MCU:dsPIC33EV64GM104
開發板:DM330018_Starter_Kit_Demo
我自己發送LIN的同步信號出去再送8個BYTE資料和checksum(每200ms送一次資料)
因為MCP2021A送出的資料自己也會收到，我試著用範例程式的做法等收到同步信號也就是產生FERR訊框錯錯時設定LIN_START=1準備開始收資料，但我卻發現_U1ErrInterrupt
一直被觸發但不是OERR,FERR,PERR 我用LED做測試,LED2會一直閃爍表示一直在中斷
但LED3卻沒亮...

到底是為什麼_U1ErrInterrupt一直被中斷 量了一下也是200ms被中斷一次,也就是說是收到同步信號才產生的中斷，我試著將同步信號取消(11BIT LO)_U1ErrInterrupt就不會被中斷了





void __attribute__((interrupt, no_auto_psv)) _U1ErrInterrupt(void)
{
if (U1STAbits.OERR == 1)
{
U1STAbits.OERR = 0;
LED3_SetHigh();
}

if (U1STAbits.PERR == 1)
{
U1STAbits.PERR = 0;
LED3_SetHigh();
}

if (U1STAbits.FERR == 1)
{
lin_start = 1; // first message detection phase
// U1STAbits.OERR = 0;
LED3_SetHigh();
}
LED2_Toggle();
IFS4bits.U1EIF = 0;
}

void LIN_Transmit(void)
{
// send break followed by 0x55 'autobaud' byte
while (U1STAbits.TRMT == 0); // wait for transmitter empty
while (U1STAbits.UTXBRK == 1); // wait for HW to clear the previous BREAK
U1STAbits.UTXEN = 1; // Enable UART TX
U1STAbits.UTXBRK = 1; // set the BREAK bit
U1TXREG = 0; // dummy write to trigger UART transmit
Nop(); // must wait 1 instruction cycle
U1TXREG = 0x55; // AUTO-BAUD sync character per J2602 spec

// send the LIN_MESSAGE_ID byte, is arbitrary but must be in the range 0x00 to 0x3B
// there are also 2 parity bits sent
LIN_ID = 0x23;
p0 = (LIN_ID & 0x01) ^ ((LIN_ID & 0x02) >> 1) ^ ((LIN_ID & 0x04) >> 2) ^ ((LIN_ID & 0x10) >> 4);
p0 = p0 & 0x01; // get bit value
p1 = ~(((LIN_ID & 0x02) >> 1) ^ ((LIN_ID & 0x08) >> 3) ^ ((LIN_ID & 0x10) >> 4) ^ ((LIN_ID & 0x20) >> 5));
p1 = p1 & 0x01; // get the bit value
id_byte = (p1 << 7) | (p0 << 6) | LIN_ID; // stuff parity bits into proper places

// form protected ID byte and transmit it
// the bit stuffing is optional, used here to test LIN receiver hardware
checksum = id_byte; // initial checksum value (limited to a byte value)
while (U1STAbits.TRMT == 0); // wait for transmitter empty
Nop();
U1TXREG = id_byte; // transmit the protected ID byte

//等SLAVE回資料

}