Attachment 2 - VME SBC Test Plan (2).2

Overview This test plan provides guidance to the Surface Surveillance Systems Engineering Team (AJW‐148) for evaluating a VME Single Board Computer (SBC) for compliance to the ASDE‐X SMR3 Rehost Project VME

Single Board Computer Requirements. It is not a comprehensive procedure as many details are dependent upon the model of SBC evaluated. Evaluation will consist of visual inspection, analysis, and functional testing.

Referenced Documents ASDE‐X SMR3 Rehost Project VME Single Board Computer Requirements

ADAC Interface Functional Specification

Triggers Module Functional Specification

Test Methodology Requirement Method

R‐HC‐1 Visual Inspection

R‐HC‐2 Visual Inspection

R‐HC‐3 Visual Inspection

R‐HC‐4 Visual Inspection

R‐HC‐5 Visual Inspection

R‐HC‐6 Visual Inspection

R‐HC‐7 Visual Inspection, Functional Test

R‐HC‐8 Visual Inspection, Functional Test

R‐HC‐9 Visual Inspection, Functional Test

R‐HC‐10 Visual Inspection

R‐VBS‐1.1 Functional Test

R‐VBS‐1.2 Functional Test

R‐VBS‐2 Functional Test

R‐VBS‐3 Functional Test

R‐VBS‐4.1 Functional Test

R‐VBS‐4.2 Functional Test

R‐VBS‐4.3 Analysis

R‐VBS‐4.4 Functional Test

R‐VBS‐4.5 Functional Test

Specific Tests

Verify Form Factor Visually inspect the SBC to determine the following:

1. P0 Connector is absent [R‐HC‐1];

2. P1 and P2 Connectors are in standard VMEbus configuration [R‐HC‐2].

Insert SBC into VMEbus chassis in left‐most slot, labeled ‘0,’ nearest power supply.

1. Verify that no more than two (2) slots are occupied by SBC [R‐HC‐3].

2. Verify that SBC seats firmly and retention clips engage correctly [R‐HC‐3].

Verify Hardware Configuration Visually inspect the SBC to determine the following:

1. An appropriate video interface connector is present on the front panel [R‐HC‐7];

2. at least one (1) USB 2.0 type A or B Female serial interface is present on the front panel

[R‐HC‐8];

3. at least one (1) 100 Base‐T or 1000 Base‐T RJ45 Keystone Jack is present on the front panel, or, if another type of connector is utilized, that an adapter is included [R‐HC‐9].

With SBC inserted into VMEbus chassis in left‐most slot, labeled ‘0,’ nearest power supply, power on

VME chassis and follow SBC‐specific procedure to enter the BIOS configuration settings. Verify the following:

1. Processor type is Generation 5 or later Core i5 or i7 Intel processor [R‐HC‐4],

2. At least 8 Gigabytes of RAM is present [R‐HC‐5],

3. 32 Gigabytes of non‐volatile storage (HDD, SSD) [R‐HC‐6],

4. PXE boot is supported [R‐HC‐7].

Verify Operating System Support With SBC inserted into VMEbus chassis in left‐most slot, labeled ‘0,’ nearest power supply, connect monitor, keyboard, mouse and LAN following SBC‐specific procedure.

Perform Red Hat Enterprise Linux version 7.3 installation process using portable USB DVD drive or USB flash drive.

1. Partition non‐volatile storage as follows:

Partition Filesystem Size /boot ext4 500MB swap swap 1GB

/ ext4 10GB /home ext4 remaining space (greater than or equal to 20GB)

2. Create a non‐root user account: sbctester.

3. Install development tools, including gcc with C and C++ development headers and libraries.

4. Install kernel development headers and libraries.

This process will verify that:

1. USB 2.0 interface is functional [R‐HC‐8],

2. keyboard and mouse input is accepted [R‐HC‐8],

3. display output at minimum resolution of 640x480 pixels [R‐HC‐7].

Boot into Operating System and confirm the following:

1. DHCP supplied IP address is associated with LAN adapter [R‐HC‐9],

2. ability to ping other host on network [R‐HC‐9].

Follow SBC‐specific procedure to install VMEbus Board Support Package (BSP). Confirm that appropriate

VMEbus device nodes are present in /dev [R‐VBS‐4.1]

Verify VMEbus Support Verification of VMEbus support requirements necessitates implementing a custom test application in compliance with the SBC‐specific VMEbus drivers associated with the vendor‐supplied BSP. This program shall perform the following:

1. Perform A24 16‐bit data single cycle transfer VMEbus reads and writes.

a. Read/Write/Verify CSRs at addresses 0x100000‐0x100006 according to ADAC module

Functional Specification.

b. Read/Write/Verify memory at addresses 0x101000‐0x102FFF with 8‐bit (lower byte of

16‐bit data access) test pattern.

c. Read/Write/Verify memory at addresses 0x14000‐0x19FFFF with 16‐bit test pattern.

d. Read/Write/Verify CSRs at address 0x200000‐0x20001C according to Triggers Module

Functional Specification.

2. Install a VMEbus interrupt handler (request level 5).

3. Configure a Triggers Module to initiate VMEbus interrupts (request level 5).

Install VMEbus Slave Modules:

1. Using the rotary switch on the ADAC slave module, configure the ADAC VMEbus memory base address to A24:0x100000.

2. Using the rotary switch on the Triggers slave module, configure the Triggers VMEbus memory base address to A24:0x200000.

3. With VMEbus chassis powered off and SBC inserted in into VMEbus chassis in left‐most slot, labeled ‘0,’ nearest power supply, install the custom VMEbus slave modules (ADAC and Triggers) into the chassis in their appropriate slots.

Execute the test application:

1. Power on the VMEbus chassis and boot the OS.

2. Login to a shell as the sbctester.

3. Perform the appropriate steps to build the test application.

4. Execute the test application.

5. Verify that all tests pass [R‐VBS‐1.1, R‐VBS‐1.2, R‐VBS‐2, R‐VBS‐3, R‐VBS‐4.1, R‐VBS‐4.2, R‐VBS‐4.3, R‐VBS‐4.4, R‐VBS‐4.5].