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.
- Cellular Testing: For test cases involving cellular networks, the Raspberry Pi 5 is strongly recommended to ensure sufficient processing overhead and optimal performance.
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 vcan0CAN
sudo ip link set can0 up type can bitrate 500000CAN-FD
sudo ip link set can0 up type can bitrate 500000 sample-point 0.75 dbitrate 2000000 dsample-point 0.75 fd onAutomotive 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
WiFi tests in VSEC Test operate on a generic Linux IP interface, allowing the Bench to act as either a client to the DUT’s access point or a peer. 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
VSEC Test supports Bluetooth Classic for various testing requirements.
- Recommendation: ESP-WROVER-KIT or Ubertooth One.
Bluetooth Low Energy
VSEC Test supports Bluetooth Low Energy (BLE) functionality.
- Recommendation: Ubertooth One or nRF52840 Dongle.
USB
USB test cases within VSEC Test leverage the facedancer libraries for advanced device interaction.
- Recommendation: GreatFET One or Cynthion.
Cellular
For Cellular testing, the VSEC Test Bench operates on a generic IP interface. A crucial requirement for sniffing tests is that all cellular traffic must be passed to the Linux device, often described as a TAP interface by cellular tools.
- Recommendation: Hardware recommendations are dependent on the specific use case and cellular modem/network being tested.
UART
VSEC Test’s UART test cases utilize a generic TTY interface.
- Recommendation: Any USB to UART cable compatible with the appropriate logic level.
JTAG
JTAG tool recommendations vary based on the target system and debugging requirements.
- Recommendation: Common choices include FTDI chips for JTAG or SWD, a miniWiggler for DAP, and a USBDM for BDM communication.