VxWorks BSP Developer's Reference : VxWorks BSP Validation Test Suite

bootline

NAME

bootline - functionality test for bootline

SYNOPSIS

bspVal options bootline

DESCRIPTION

This test verifies the commands executable from the VxWorks boot ROM prompt. It has a run-time of up to a few minutes. See bspVal.sh for an explanation of options.

NOTE:

This reference entry lists the most likely reasons for a test's failure. However, it does not list all possible reasons.

The first test reboots the target while sending characters to the serial console, causing possible problems with pending serial interrupts. If this test fails, check that CPU interrupts are properly disabled in romInit( ), a routine defined in romInit.s, and that all serial device interrupts are disabled and cleared in the sysLib routine, sysSerialHwInit( ).

The second and third tests check the bus error exception handling functionality (local and off-board addresses, respectively). If these tests fail, check that the memory controller is initialized properly and that any memory watchdog timers are configured to reasonable values (if present).

If there is not a local (on-board) memory address that can cause a bus error when accessed, the macro T1_BOOT_LOCAL_ERR_ADRS should be set to an invalid off-board address.

The fourth test checks that the bootline commands and booting mechanisms all act as expected. This test can fail for a variety of reasons. Check that the memory controller is set up properly and that the network connection is attached.

This test script does not work properly with a VxWorks standalone image in ROM. If the target can execute VxWorks only out of ROM, this test script should not be part of the BSP validation procedure.

Make sure that all the boot line parameters in the configuration file represent the actual target boot parameters. Failing to do so can leave target in a state where a power cycle reset is necessary with change in boot parameters.

Barring serious hardware or software limitations (such as an identifiable VxWorks problem), the target board must pass all tests for the BSP to be validated.

CONFIGURATION PARAMETERS

T1_BOOT_LOCAL_ERR_ADRS 30

Local memory address that causes bus error. (required)

T1_BOOT_OFFBOARD_ERR_ADRS

Off-board address that causes bus error. (required)

T1_BOOT_LOCAL_BUS_ERR_MSG

Local bus error message keyword. (required)

T1_BOOT_OFFBOARD_BUS_ERR_MSG

Off-board bus error message keyword. (required)

T1_SER_DEVICE

Serial device to be used on host. (required)

T1_SER_BAUD

Default serial baud rate. (required)

T1_TMO_BOOT

Timeout value for booting vxWorks. (required)

EXAMPLE

Output consists of:

                   BSP VALIDATION TEST
                   -------------------

    Target server                     : t53-160
    BSP                               : mv147
    Log file                          : /tmp/bspValidationLog.5219



    Bootline Test :
    Control X test                                            : PASS
    Bus error test for local error address                    : PASS
    Bus error test for off-board error address                : PASS
    boot commands test                                        : PASS

                      Tests RUN           4
                      Tests PASSED        4
                      Tests FAILED        0
                      Tests SKIPPED       0

SEE ALSO

bspVal.sh, bspPkCommonProc.tcl, serLib.tcl, envLib.tcl, pkLib.c