VxWorks BSP Developer's Reference : VxWorks BSP Validation Test Suite
rlogin - testing rlogin
bspVal options rlogin
This test verifies the ability to rlogin between two VxWorks target boards. The entire test should not take more than a few minutes to run. See bspVal.h for an explanation of options.
In order to run this test, the configuration file used to create the VxWorks image must have defined the following macros:
NOTE: This reference entry lists the most likely reasons for a test's failure. However, it does not list all possible reasons.
If the project facility is used to create VxWorks image, add the following components to VxWorks configuration:
INCLUDE_SHELL INCLUDE_RLOGIN INCLUDE_SHOW_ROUTINES INCLUDE_NET_SYM_TBL INCLUDE_LOADER
All tests run by this script are concerned with verifying the rlogin process. After issuing an rlogin to the target on the reference board, the first test verifies that "IN USE" appears on the console of the target board. The second test confirms the rlogin session by calling version( ) from the VxWorks shell and attempting to match the address for the target board. The third test exercises the pty by spawning printLogo( ). The fourth test checks the operation of logout( ). This process is then repeated for rlogin from the target to the reference board and the rlogin session is confirmed with tests five through eight. If any of these tests fail, check that the IP address or backplane address for the target board (T1_BOOT_E or T1_BOOT_B) and reference board IP or backplane address (T2_BOOT_E or T2_BOOT_B) are set correctly. Check also that their respective target names (T1_BOOT_TN and T2_BOOT_TN) are set to their proper values.
INCLUDE_RLOGIN INCLUDE_SHELL INCLUDE_NET_SYM_TBL INCLUDE_LOADER INCLUDE_SM_NET_SHOW INCLUDE_SYM_TBL_SHOW INCLUDE_SHELL_BANNER 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.
NOTE: This test does not require a backplane. It is enough if there is a network connection between the two targets. If the boards reside on separate sub-nets, the routing tables for each must be set up appropriately.
- T1_BOOT_TN 20
- Target name (required).
- T1_BOOT_E
- Target IP address (required).
- T2_BOOT_B
- Target backplane address (required if T1_BOOT_E is not set).
- T2_BOOT_TN
- Reference target name (required).
- T2_BOOT_E
- Reference target IP address (required if T2_BOOT_B is not set).
- T2_BOOT_B
- Reference target backplane address (required if T2_BOOT_E is not set). Because the default is to use the Ethernet, if you set both T2_BOOT_E and T2_BOOT_B, the test uses the reference target IP address.
Output consists of:
BSP VALIDATION TEST ------------------- Target server : t53-160 BSP : mv147 Second target server : t214-2 Second BSP : mv147 Log file : /tmp/bspValidationLog.6425 rlogin : IN USE message when rlogin to t53-160 : PASS reach shell of t53-160 : PASS rlogin pty usage on t53-160 : PASS logout from t53-160 : PASS IN USE message when rlogin to t214-2 : PASS reach shell of t214-2 : PASS rlogin pty usage on t214-2 : PASS logout from t214-2 : PASS Tests RUN 8 Tests PASSED 8 Tests FAILED 0 Tests SKIPPED 0
bspVal.sh, loginLib.tcl