Receiving "ghost" data on UART RX, also writing to UART serial port 2 sends data on serial port 1
Posted: Tue Jul 27, 2021 9:02 am
I've recently taken over work on Netburner-based hardware. The code base that I'm working on has been moved from MOD5272 to MOD54415. Here are the problems or questions that I'm facing:
On MOD54415:
On MOD54415:
- My application is sending data on serial port 0 and serial port 2 at 19200 baud without any problem.
- On serial port 2, my application is receiving "ghost" data, i.e. data is not being sent to the UART, but the serial receive routine is being invoked.
- It's a mystery to me why the previous developer used serial port 2 for the MOD54415.
- I'm checking TX signals with an oscilloscope connected to UART 0 TX pin J2[4] and UART0 TX pin J2[22].
- QUESTION: Is there anyway via port control or selection bits that UART2 is mapped to the pins for UART1? I did not find anything in the MCF54415 documentation
- QUESTION: All control registers for UART2 are same as for UART0. What could cause "ghost" data to be received?
- My application is sending data on serial port 0 and serial port 1 at 19200 baud without any problem.
- I'm also checking TX signals with an oscilloscope connected to UART 0 TX pin J2[4] and UART1 TX pin J2[22].
- My application should receive data serial port 0 and serial port 1 without any problem, but haven't tested yet. Users have not reported any problems.