A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
UART1 Modem Interrupt_CTS and RTS signals not used in HW
Other Parts Discussed in Thread: OMAP-L138Hi,
I want to validate UART1 on OMAP-L138 on our custom Hardware.
We are using the SOM from LogicPD. Difference is we have redesigned our Hardware.
We are not using CTS and RTS from UART1. In EBOOT and UBL we are successfully able to read and write using UART1.
Processor Clock is 324MHz.
During WinCE code excution I had observed that Reading IIR register returns 0xC0 and It keep on loops in the function COMAPL13xSerial::ThreadRun() which is available in c:\WINCE600\PLATFORM\COMMON\SRC\SOC\OMAPL13X_TI_V1\SERIAL\serial.cpp
further debugging it looks that the
while(!IsTerminated() &&((bData = m_pReg16550->Read_IIR()) & SERIAL_IIR_INT_INVALID)==0) is executing continuously and it enters into SERIAL_IIR_MS switch case.
Let me know your thoughts...I am not using RTS and CTS in my device... Also reading
It keep on entering that loop and IIR returns 0xC0. Although the UART datasheet doesn't say anything about the value 0x0 (Bits 3 to 0), the code considers it as Modem Interrupt. Reading MSR returns 0x11. The running code never able to clear this.
The other difference between OMAP-L138 from LogicPD and our HW is we are running ARM at 324MHz. So SYSCLK2 = 162MHz. Divider for generating 115200 baud rate we have used value 87. Which gives baud rate equals to 116379 with error percentage equals to 1%.
Please let me know even though we are not using UART1_CTS and RTS why the modem interrupt occurs?
Using Pinmux registers we have configured UART1_RTS as GP0[11] and UART1_CTS as AHCLKX.
Regards,
GSR