I am currently having some issues with the loopback testing on 2 COM ports simultaneously using Burn In Test Pro v4.0 on Win XP SP1 & 2 on a few platforms. Most of the results will give me error message of “error while sending data to the COM port(s)”. The testing requirements/configurations in burnintest are:
Duty Cycle 100
RTS/CTS and DSR/DTR testing enabled
Send & receive timeout 3500ms
Port speed 115200Kbits/sec
The default COM port settings in Windows device manager however are as below:
Bits per second: 9600
Data bits:8
Parity:None
Stop bits:1
Flow control: None
In Advanced Settings the Use FIFO buffers(requires 16550 compatible UART) is checked. The Receive Buffer is High(14) & Transmit Buffer is High(16).
My questions:
1. How does the duty cycle(set to 100) affect the COM port transmission?
2. The port speed of the BurnInTest was set to 115200kb/s. The chipset Serial I/O Unit can support up to 115Kbps. However the default COM port settings as can be seen above is 9600bps and the receive and transmit buffers are both set to high. Does the settings in the COM port in any way affecting the loopback test performed? How does it relate to the default settings in the COM port?
3. On the cases that we get an error message, we tried rerun the test by changing the Advanced Settings for COM port Receive Buffer set to Low(1) for both COM ports and no error was found. Can you please explain how the settings of receive & transmit buffer affect the COM data transmission?
4. We also tried the test using the Linux version of BurnInTest and for boards that have critical error on the loopback test before on BurnInTest for Windows, we did not receive such error now when using the Linux version. Does the Linux version in any way different than the Windows version? Does it suggest an OS or driver problem?
5. Specifically for loopback test, what are the improvements on the v5.0 of the Burn InTest Pro compares to v4.0?(bug fixes, etc)
Your clarification on these queries would be much appreciated.
Many thanks.
Regards,
James
Duty Cycle 100
RTS/CTS and DSR/DTR testing enabled
Send & receive timeout 3500ms
Port speed 115200Kbits/sec
The default COM port settings in Windows device manager however are as below:
Bits per second: 9600
Data bits:8
Parity:None
Stop bits:1
Flow control: None
In Advanced Settings the Use FIFO buffers(requires 16550 compatible UART) is checked. The Receive Buffer is High(14) & Transmit Buffer is High(16).
My questions:
1. How does the duty cycle(set to 100) affect the COM port transmission?
2. The port speed of the BurnInTest was set to 115200kb/s. The chipset Serial I/O Unit can support up to 115Kbps. However the default COM port settings as can be seen above is 9600bps and the receive and transmit buffers are both set to high. Does the settings in the COM port in any way affecting the loopback test performed? How does it relate to the default settings in the COM port?
3. On the cases that we get an error message, we tried rerun the test by changing the Advanced Settings for COM port Receive Buffer set to Low(1) for both COM ports and no error was found. Can you please explain how the settings of receive & transmit buffer affect the COM data transmission?
4. We also tried the test using the Linux version of BurnInTest and for boards that have critical error on the loopback test before on BurnInTest for Windows, we did not receive such error now when using the Linux version. Does the Linux version in any way different than the Windows version? Does it suggest an OS or driver problem?
5. Specifically for loopback test, what are the improvements on the v5.0 of the Burn InTest Pro compares to v4.0?(bug fixes, etc)
Your clarification on these queries would be much appreciated.
Many thanks.
Regards,
James
Comment