Vehicle Control Module

A communication gateway and power distribution for motorsports, serving as the main electronic hub of the vehicle.

Goals

• Completely open-source HW and SW. Should be a platform that anybody can hack, extend, and make their own.
• Common parts, readily available for Digikey, Mouser, etc. Datasheets are available without NDA.
• Shoot for OEM level reliability and robustness, without going full ASIL alphabet soup.

Vision

• Controlling a circuit should be as simple as writing some logic (engine_temp_c > 70.0f) && (vehicle_speed_mps < 5.0f).
• No need for traditional fuses, relays as something like a slow-blow fuse can be done in software.
• Plug into the vehicle using standard ethernet to debug/reconfigure/reflash.
• Foundation for support datalogging, telemetry, and HMI.

Hardware

Based on the Microchip ATSAMV71Q21.

• (2) CAN-FD channels via TLE9250.
• (3) 100BASE-T1 channels via TJA1100.
• (1) 100BASE-TX channel via KSZ8061MNX to support debug with a laptop.
• (18) High Side drivers via BTS50015-1TAD.
• (2) RS-232 serial channels to connect GPS receivers and legacy IMUs.
• (8) Digital Inputs.

Prerequisites

MacOS

wget https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu-rm/10-2020q2/gcc-arm-none-eabi-10-2020-q2-preview-mac.pkg

# Install.  Add `/Applications/ARM/bin/` to PATH via bash_profile.

brew install cmake

Building

# Jump into the sw directory, create a build dir, and then jump into that.
cd sw
mkdir build
cd build

# Run CMake specifying the toolchain file.
cmake ..

# Build!
make

Debugging

A configuration script under conf/j-link can be used with Segger Ozone to load the generated ELF on target and debug.