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

error2

NAME

error2 - error handling tests

SYNOPSIS

bspVal options error2

DESCRIPTION

This test verifies that the target board does not hang while handling errors initiated from the VxWorks shell. The entire test can take several minutes to run. See bspVal.sh for an explanation of options.

In order to run this test, the target has to be configured with auxiliary clock. To do this, add INCLUDE_AUXCLK to config.h file of the BSP or include the component INCLUDE_AUX_CLK, if using project facility.

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 connects a routine that causes a bus error to the target's system clock interrupt. This causes an exception at interrupt level, known as a "catastrophic" error. This exception should result in a reboot of the board. An appropriate error message should be displayed by the target. If this test fails, check that the sysToMonitor( ) routine in sysLib.c is functioning properly. Also check that the address of sysExcMsg is set correctly in sysLib.c.

The second test reboots the target from the shell while characters are sent to the serial console and the auxiliary clock is enabled at the maximum rate. This checks that pending interrupts do not cause problems while rebooting. If this test fails, check that CPU interrupts are properly disabled in romInit( ), which is defined in romInit.s, and that all serial device interrupts are disabled and cleared in sysSerialHwInit( ). Also, check that the auxiliary clock routine sysAuxClkRoutine( ) is initialized to NULL and, if it is NULL, that the auxiliary clock is not called in sysAuxClkInt( ).

Make sure that all the boot-line parameters in the configuration file represent the actual target boot parameters. Failing to do so could leave target in a state where a power cycle reset would be 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_OFFBOARD_ERR_ADRS 30

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

T1_CATASTROPHIC_ERR_MSG

catastrophic error message keyword (required)

T1_SER_DEVICE

Serial device that is used on host. (required)

T1_SER_BAUD

Serial baud rate used. (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



    Second Error Test :
    catastrophic error test                                   : PASS
    reboot with interrupts                                    : PASS

                      Tests RUN           2
                      Tests PASSED        2
                      Tests FAILED        0
                      Tests SKIPPED       0

SEE ALSO

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