This thread has been locked.

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 issue from OMAP3530/Beagle board

There is issue of UART1:

Current status:

- UART3 working OK as console

- UART2 tested with loopback. The looped back data seemed to be duplicated either on the output buffer, the input buffer or both.

- UART1 tested with rs232 cable with another computer. Could only make Tx work, while Rx didn't work whatever the software configuration. Loopback test failed although we could measure solid pulses on the Rx pin.

All tests were done without any hardware handshaking (RTS/CTS). The port settings and mux settings for all UARTs were copied from the working UART3.

The software used was Angstrom built via OpenEmbedded, git commit id 3f626eba5c24c1da731eace82a4797a6f0d0afd4.

Kernel used is that from recipe linux-omap-psp_2.6.32.bb (git source git://arago-project.org/git/people/sriram/ti-psp-omap.git at commit a6bad4464f985fdd3bed72e1b82dcbfc004d7869)

The kernel was built with OMAP3_MUX support, and patched enable McSPI3 and to disable the DVI and camera (for UART1). Also debugfs was enabled in order to be able to switch mux settings without recompiling and rebooting.

The tools used to test were:

cat /dev/ttyS0 (or 1 for UART2)

echo blah > /dev/ttyS0

stty (for changing the serial port settings)

Thanks for any input!

Michael Chen