02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

VxWorks 5.5<br />

<strong>BSP</strong> Developer’s <strong>Guide</strong><br />

The third test spawns a single pkLoopbackTest( ) task for each serial port connected in<br />

loopback mode. Each port sees a pattern of sequential characters sent and received at the<br />

maximum baud rate. All characters must be received in the order sent. If this test fails,<br />

check that all serial ports under test are set up correctly for loopback mode. Make sure<br />

that the serial driver is handling receive and transmit interrupts properly. Make sure that<br />

all serial channels under test have been configured and initialized to the correct values.<br />

The fourth test spawns several pkLoopbackTest( ) tasks for each serial port connected in<br />

loopback mode. Each task repeatedly sends a particular character to one of the ports.<br />

There are several tasks for each serial port under test. Each port should receive all the<br />

characters that were sent. If this test fails, check the same problem areas suggested for the<br />

third test.<br />

The third and fourth tests spawn one or more pkLoopbackTest( ) tasks for each serial<br />

device connected in loopback mode. These tasks run concurrently, sending and receiving<br />

characters at the highest baud rate supported by both host and target. It is possible that<br />

target boards with slower CPUs and many serial devices might not possess the raw<br />

processing power required to keep up with the tests. If hardware limitations are causing<br />

the loopback tests to fail, the tests can be configured to lighten the processor load. The<br />

serial.tcl tests run at the highest baud specified in the bspVal macro,<br />

<strong>BSP</strong>TEST_HOST_RATES (provided that the rate is supported by both the host and<br />

target).<br />

Modifying <strong>BSP</strong>TEST_HOST_RATES to exclude the higher common baud rates will cause<br />

the tests to run at a lower rate, thus avoiding possible hardware- related problems.<br />

Additionally, the pkLib.c constant PK_LOOP_TASK_NUM can be changed from the<br />

default value of 4 to decrease the number of concurrent tasks running in the fourth test. In<br />

this case, the object code file pkLib.o must be rebuilt from the changed pkLib.c source<br />

file.<br />

Target boards with several serial devices and a small amount of local RAM (1Mbyte or<br />

under) might run out of memory while executing the tests. In this case, either configure<br />

the target to use an external memory card or decrease the number of tasks running as<br />

described above.<br />

If the test script execution ends prematurely, the target board might be left set to a baud<br />

rate other than T1_TIP_BAUD. This situation could leave the board in such a state that a<br />

power cycle reset would be necessary to continue with other tests.<br />

Barring serious hardware or software limitations (such as an identifiable VxWorks<br />

problem), the target board must pass all tests for the <strong>BSP</strong> to be validated.<br />

CONFIGURATION PARAMETERS<br />

<strong>BSP</strong>TEST_HOST_RATES<br />

Baud rates supported on host. (required)<br />

T1_SER_DEVICE<br />

Serial device to be used on host. (required)<br />

396

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!