BurnInTeest ARM v4.1 Serial Test Fail

[Wilson_ASRI]

Hi

I'm using Nvidia Orin NX platform.
It's linux aarch64 arm base.

It's have a PL2303 USB to Full UART serial port on the carrier board.
When I test the serial port loopback by BurnInTeest ARM v4.1
It's always show following error.

CRITICAL: 2023-05-08 16:07:26, Serial, Error while receiving from the COM port. Check plug is connected.

I sure the com port connect the loopback plug.
And I test it by putty is worked fine.

I tried to disable DTS/RTS DTR/DSR and got the same error.

Does anyone can help us?

[Simon (PassMark)]

Note that we do not support BIT ARM v4 anymore as development has moved to v5. We haven't tested on NVidia Orin NX either.

Are you using your own plug or a plug purchased from us? We only support our own loopback plugs.

[Wilson_ASRI]

Hi Simon,

I try to download BIT ARMv5 and got the same error.
We use our plug. I check the pin connect is same as that you sold.

• Receive and transmit (2 & 3)
• Request to send and Clear to send (7 &
• Data carrier detect, Data set ready and Data terminal ready (1, 6 & 4)

[David (PassMark)]

Maybe there are multiple serial ports in your Linux setup and the one where you have the loopback plug connected isn't the one you are testing?

[Wilson_ASRI]

Hi David,

Yes, I'm really sure it connect the RIGHT port with BIT setting.
Because we use the BIT ARMv5 and it can sent and recv some data by the com port.
The Throughput item show some bytes/sec in the terminal.
But I still get the error.
CRITICAL: 2023-05-08 16:07:26, Serial, Error while receiving from the COM port. Check plug is connected.

[Wilson_ASRI]

It's the serial test page.

[David (PassMark)]

So screen shot shows 1 error per test cycle (32 cycles and 32 errors).
So probably not random. So maybe a single error at the start or end of each cycle.
Obviously very hard to debug without having the same motherboard, loopback plug and operating system.

Can you generate a debug log using the -d flag on the command line and send us the log file.

[Wilson_ASRI]

Hi David,

This is my debug.log
I upload it to google drive because it's large than 4MB.
https://drive.google.com/file/d/1Nhs...-ymueESOIYBfs/

[David (PassMark)]

The failure message in the log is
"Is your loopback plug present"
and on the screen it is, "Check plug is connected"

There is a small check in the code to make sure there is a loopback device connected to the COM port. When this test failed and the error above is the result.

The test does the following
1) Send 1 byte to the serial port
2) Waits 100milliseconds
3) Reads 1 byte

In this case the read fails. Zero bytes are returned, but the return code was "success" meaning there was no hardware error, but there was also no data to read.

So maybe this CPU / system is so slow that 100ms isn't enough time to send and receive 1 byte of data.
(But it should be, as at 9600 baud, there should be roughly 1 character per millisecond)

Do you get the same error at a higher baud rate?

[Wilson_ASRI]

Hi David,

I have tested 115200 still get error.
Perhaps it's the usb to serial chip (PL2303) issue. Because I test ttyTHS0 is pass and ttyUSB0 is failed. I'm chcking it with agent.

I have two questions.
1. In the BIT arm v5 setting. I set

## Disable RTS/CTS flow control testing
DisableRTS
## Disable DSR/DTR flow control testing
DisableDSR​

Does it just disable RTS and DSR only? Do I need to add DisableCTS and DisableDTR?

2. In the BIT test. Does it have any difference between ttyTHS0 and ttyUSB0 for BIT?
ttyTHS0 : original UART from Nvidia Orin NX (TX/RX/CTS/RTS)
ttyUSB0 : usb to serial chip (pl2303)