How paradigmengineering/aks-2026-hardware works
This repository contains STM32G474 firmware for an autonomous kart. The principal workflow is the firmware main loop: it monitors safety and timing signals, coordinates steering and braking behavior, and manages the drive controller over CAN; a UART interface provides a separate Jetson communication capability. The graph focuses on application code rather than the bundled STM32 HAL/CMSIS framework. Source excerpts are partial, so unshown peripheral and interrupt wiring is omitted rather than inferred.
Main entry points: main.c Main Control Loop · drive_can.c Drive CAN · jetson_uart.c Jetson UART · steering.c Steering Control
Components 10
Application Control
- Main Control Loop
firmware/ParadigmSTM32G474/Core/Src/main.c
Vehicle Actuation
- Steering Control
firmware/ParadigmSTM32G474/Core/Src/steering.c - Braking Control
firmware/ParadigmSTM32G474/Core/Src/braking.c
Communications
- Drive CAN
firmware/ParadigmSTM32G474/Core/Src/drive_can.c - Jetson UART
firmware/ParadigmSTM32G474/Core/Src/jetson_uart.c
MCU Platform
- Interrupt Handlers
firmware/ParadigmSTM32G474/Core/Src/stm32g4xx_it.c - System Startup
firmware/ParadigmSTM32G474/Core/Src/system_stm32g4xx.c
Other components
- Kart Signals
- Drive Controller
- Jetson Computer
Connections 9
- Kart Signals → Main Control Loop: provides signals
- Main Control Loop → Steering Control: uses control
firmware/ParadigmSTM32G474/Core/Src/main.c - Main Control Loop → Braking Control: uses control
firmware/ParadigmSTM32G474/Core/Src/main.c - Main Control Loop → Drive CAN: manages drive
firmware/ParadigmSTM32G474/Core/Src/main.c - Drive CAN → Drive Controller: exchanges CAN
- Main Control Loop → Jetson UART: uses interface
firmware/ParadigmSTM32G474/Core/Src/main.c - Jetson UART → Jetson Computer: exchanges UART
- Main Control Loop → Interrupt Handlers: configures IRQ
- Main Control Loop → System Startup: initializes MCU