It’s the debug port
1 Like
how do you connect to it? is it the USB (probably not)?
and why does it have rx bytes even though @StrikeEagle is probably not using it for some work
The USB port is always Serial 0.
1 Like
It is another UART port which may or may not be exposed as a pad on the PCB.
As for what’s it’s receiving, I didn’t give it much thought until you brought this up.
so is the console port different from the debug port?
from the wiki,
The system’s serial console runs on the port labeled SERIAL4/5. The pinout is standard serial pinout, to connect to a standard FTDI cable (3.3V, but it’s 5V tolerant).
so it seems to be different.
if its not exposed then how do we have rx bytes when its not even exposed? I believe the JTAG interface is also different but not sure
I think it’s also possible that the RX is due to interference and not real bytes.
around 5.1kb of interference is little weird. it stays roughly the same all the time, not increasing too much or reducing by a lot
what value did you plot? I have the same board so I can explore a log from it to see if its similar on all boards or an issue with a specific board.
I searched on google what is UART6 and the AI overview told its the IOMCU line, but most likely it is wrong, but could be considered as a possible thing.
Just a graph from the Hardware Overview plot. The IOMCU UART seems plausible
I get the same value - 5044bytes rx and 8388b of tx.
it comes in sequence, uart1-2-3-4-5 and then iomcu.
the baud is 1500000 (no. of zeros might be a bit off) for me and the rx being lower makes sense since it would be reporting health and the tx would be io signals. I am having 4 channels on the IOMCU being used and perhaps a different number of channels could effect this value as well.
1 Like