Supported Hardware

Bench

The VSEC Test software environment is distributed as custom disk images designed for the Raspberry Pi. This forms the central processing unit for all test operations and is known as the “Bench”. Get started by checking out our guide to Create a New Bench!

Platform Compatibility: VSEC Test supports installation on any Raspberry Pi model 3, 4, or 5.
Performance Considerations: While optimized for all supported models, higher RAM variants (e.g., 4GB or 8GB) may offer improved performance during resource-intensive test cases.

Interfaces

The interfaces on this page fall into two groups:

Built-in Test Cases: CAN and Ethernet/IP. The pre-built Test Cases run on these interfaces. The IP Test Cases work on any Linux IP interface of the Bench.
Usable through Custom Test Cases: Wi-Fi, Bluetooth Classic, Bluetooth Low Energy, USB, Cellular, UART and JTAG. There are no built-in Test Cases for these interfaces. The hardware listed below can be connected to a Bench and used through Custom Test Cases or the Remote Terminal.

CAN

VSEC Test’s CAN test cases utilize a SocketCAN interface, identified by the device parameter in audits. Many hardware devices support SocketCAN, often appearing as can0 once connected to the Linux machine. Some devices, such as those from Intrepid Control Systems, may require specific drivers.

Recommendation: PCAN-USB from PEAK.
Configuration: If your CAN device does not auto-detect the bus baud rate, manual configuration is required. Refer to the Linux kernel documentation for detailed commands: https://docs.kernel.org/networking/can.html

Setup Commands

After connecting your CAN interface to the Bench, you may need to configure it with commands similar to these:

Virtual CAN

sudo modprobe vcan
sudo ip link add dev vcan0 type vcan
sudo ip link set up vcan0

CAN

sudo ip link set can0 up type can bitrate 500000

CAN-FD

sudo ip link set can0 up type can bitrate 500000 sample-point 0.75 dbitrate 2000000 dsample-point 0.75 fd on

Automotive Ethernet

VSEC Test’s Automotive Ethernet tests are designed to operate on any standard Linux IP interface. This allows for testing on Automotive Ethernet networks using any media converter that can provide a compatible interface to the Linux-based Bench. Static IP configuration is often necessary on such networks, as DHCP may not be available.

Recommendation: Intrepid RAD-Moon / RAD-Moon 2 Media Converter

WiFi

A Wi-Fi adapter appears on the Bench as a generic Linux IP interface, allowing the Bench to act as either a client to the DUT’s access point or a peer. Wi-Fi testing is done through Custom Test Cases. DHCP is typically available in these scenarios, negating the need for static IP assignment.

Recommendation: Alfa WiFi to USB adapters, such as the AWUS036AXML, which support monitor mode and packet injection.

Bluetooth Classic

Bluetooth Classic testing is done through Custom Test Cases.

Recommendation: ESP-WROVER-KIT or Ubertooth One.

Bluetooth Low Energy

Bluetooth Low Energy (BLE) testing is done through Custom Test Cases.

Recommendation: Ubertooth One or nRF52840 Dongle.

USB

USB testing is done through Custom Test Cases, for example with the facedancer libraries.

Recommendation: GreatFET One or Cynthion.

Cellular

Cellular testing is done through Custom Test Cases on a generic IP interface. Sniffing requires all cellular traffic to be passed to the Linux device, often described as a TAP interface by cellular tools.