DEV Community

Cover image for SLX SteerDrive: STM32 firmware for an EPS controller
Marco
Marco

Posted on Edited on Originally published at siliconlogix.it Fully Autonomous

SLX SteerDrive: STM32 firmware for an EPS controller

The STM32 at the centre of the bench

A controller demonstrates its value when it receives measurements, decides which command to apply and handles inconsistent data or a lost connection. The display helps the operator observe and manage that work; the firmware remains responsible for control.

SLX SteerDrive is an electric power steering controller development bench built by Silicon LogiX. The STM32H750B-DK runs EPS control and manual commands, provides the touch interface and communicates with the simulator over CAN FD or Ethernet. The motor, steering mechanism and load are simulated on the PC; no physical motor is connected to the board. The simulator returns the signals required to close the loop.

The path is explicit: the operator sets a reference on the Discovery, the firmware receives a model sample, calculates assistance and sends a command. The simulator updates the motion and produces measurements for the next cycle. The software article examines the model, 3D scene and analysis tools.

STM32H750B-DK running the SteerDrive EPS HMI, with the DSD TECH SH-C31G USB CAN FD adapter and bus wiring visible

Frame from the recorded demonstration: the Discovery runs the EPS controller and displays CAN FD communication with PC-provided sensors. The SH-C31G adapter and bus wiring are visible above the display. Motor, mechanics and current are simulated on the PC.

Closed loop with the STM32 controller: simulated measurements from the PC, EPS control on the board and an assistance command back to the model

Controller computation and communication links are real. The steering mechanism, load and motor run as PC models; this defines the scope of the tests.

What an EPS controller does

EPS stands for Electric Power Steering: an electric motor adds assistance to the driver's effort. Steering-column torque and vehicle speed help determine the requested assistance. On the SteerDrive bench, a virtual torsion bar connects the steering wheel and pinion; its deformation produces the sensor signal. Driver torque, measured torque and assistance are separate quantities that can also be observed during a reversal.

The firmware filters the measurement, applies a dead zone and uses a speed-dependent assistance map. Torque and slew-rate limits control transitions between requests. Near an end stop, assistance is reduced in the direction that pushes towards the limit while allowing the mechanism to return. Current received from the model contributes to assistance derating and sustained-overcurrent handling.

EPS and ESP serve different functions. ESP, electronic stability control, compares vehicle motion with the requested direction and can act on braking and powertrain torque. SteerDrive develops steering assistance control; it does not implement ABS, yaw control or selective braking. Bosch's descriptions of electric power steering and vehicle stability cover the two areas.

Hardware and firmware boot

The Discovery integrates the Cortex-M7 microcontroller, kit display, touch input, external memory, Ethernet and CAN FD interface. The firmware uses FDCAN1 and the board's transceiver: the digital controller prepares frames, while the transceiver transfers them to the differential CAN_H/CAN_L pair. The hardware reference is ST user manual UM2488.

The HMI application exceeds the STM32H750's 128 KiB of internal Flash. A small internal bootstrap therefore starts the application in QSPI memory using execute-in-place, XIP, mapped at 0x90000000. Application and bootstrap are separate images; after programming, QSPI readback was compared with the expected binary.

This includes integrating peripherals and their constraints: clocks, interrupts, shared memory and display updates must coexist with control. The Discovery is the development platform. A product board requires its own electrical integration, power supply and application-specific environmental verification.

The control cycle

The control task has higher priority than communication and graphics and runs every 10 ms. Networking handles message exchange and validation; the HMI receives coherent state snapshots and submits operator requests. Bounded queues and snapshots separate the paths so that drawing a page does not add a wait to assistance computation. This follows the principles of FreeRTOS priority-based scheduling.

At each update, the firmware checks session, sample, transaction and data age, evaluates bench state and calculates the permitted command. The response retains its correlation with the sample used. The PC can identify which measurement produced an assistance request even when newer packets have already arrived.

Control period, execution time on the MCU and end-to-end communication response time are different measurements. In the tests below, the maximum observed controller computation time was 260 µs, or 2.6% of the 10 ms period. This ratio describes computation duration relative to its time window; graphics, networking, interrupts and other tasks contribute separately to total MCU load. Link response time also includes scheduling, transport and PC-side work. The observed maximum is not a formal worst-case execution-time proof.

The 100 Hz cycle covers assistance, position and bench supervision. Current returned by the simulator describes the actuator model; this firmware does not perform three-phase motor commutation or run an FOC loop. Separating control levels makes the controller's timing and responsibilities clear.

Manual commands and HMI

The LVGL HMI operates within the display's 480 × 272 pixels. The top bar shows EPS state and transport; Bench, Commands, Signals and System keep start, stop and reset recognisable. System pages expose connections, alarms, information and parameters. Charts distinguish torque, rack position and current.

The controller can use the PC Profile or receive a manual reference from the touch display. Torque sets virtual driver effort, limited to ±8 Nm. Steering wheel uses a virtual driver to follow an angular reference with limited torque. In Axis mode, the position controller runs on the STM32 and uses rack feedback within the ±45 mm domain.

Axis mode also demonstrates a control function relevant to automation: the controller generates the action needed to follow a position, while the PC supplies a plant with inertia, friction and load. The reference is ramped at 25 mm/s; requested assistance is limited to ±32 Nm with a maximum slew rate of 80 Nm/s. Virtual driver torque is zero in this mode.

SteerDrive HMI: framebuffer read from the physical display during CAN FD communication, native manual-command and signal-chart previews

Top left: framebuffer read from the Discovery during CAN FD testing. The other panels show Commands and Signals from the same HMI in the test environment, plus operator functions. Actual application labels remain in Italian.

Ethernet/CAN FD selection is available while the bench is stopped. The highlighted button and top-bar label reflect the same choice. Tapping the already-selected transport preserves the session; changing transport requires the peer to become available again and an explicit start.

CAN FD: bus and bit timing

CAN FD extends the Classical CAN data field to 64 bytes and, with BRS, allows a higher data-phase bit rate. Arbitration retains the nominal bit rate; the data phase can use different timing. SteerDrive uses 500 kbit/s nominal and 2 Mbit/s data, standard 11-bit identifiers and a 64-byte payload.

On this bench, CAN_H connects to CN11 pin 1 and CAN_L to CN11 pin 2; a third wire connects the ground references. Both ends have 120 Ω termination: JP7 on the Discovery and termination on the isolated DSD TECH SH-C31G adapter. The link was verified with wires shorter than 30 cm. Pin assignments and jumpers must be checked against the actual board revision and its schematic.

CAN FD connection between Discovery and SH-C31G showing transceivers, CAN_H, CAN_L, ground reference and 120-ohm termination at both ends

The transceiver connects the controller's digital signals to the differential line. The diagram represents the tested bench connection; the PC reaches the bus through the isolated USB adapter.

Timing was also verified against internal clocks. The 200 MHz PLL1Q source is divided by two in the CCU, giving a 100 MHz CAN clock within the project's APB1 clock limit. A prescaler of 5 and 40 time quanta per bit produce 500 kbit/s; the same prescaler with 10 quanta produces 2 Mbit/s. Nominal segments are 34/5 and data segments 7/2, in addition to the synchronisation quantum. Transmitter delay compensation, TDC, is disabled in the tested profile. Other wiring or bit rates require their own verification.

A compatible adapter requires both a PC driver and firmware that advertises and supports CAN FD and its timing limits. Discovery–PC communication was verified using WinUSB/gs_usb and an SH-C31G with official DSD TECH v1.5 firmware, while the electromechanical model remained in the simulator. PEAK PCAN is a separate software backend.

The SLX FD 1 protocol

The bus is standard; identifiers and signal meanings belong to the application. A CAN ID is not a universal code for a car's steering controller. SteerDrive uses the SLX FD 1 contract, with a DBC describing fields and units. Integration with a manufacturer's ECU or vehicle network requires that vehicle's contract. OBD, UDS, J1939 and CANopen are separate application protocols and are not implemented by this bench.

HELLO and READY open the session. The controller emits REQUEST with mode and reference; the PC returns SENSOR, and the STM32 replies with COMMAND. ARM handles start, stop and reset; CONFIG selects the regulation while inactive; STATUS and ACK expose state and confirmations. ARM and ACK use different IDs in the two directions, keeping one producer per arbitration ID.

Service Hexadecimal ID Direction and purpose
HELLO / READY 0x501 / 0x502 PC → ECU / ECU → PC: opening and capabilities
REQUEST 0x503 ECU → PC: reference and requested conditions
SENSOR 0x504 PC → ECU: torque, speed, position, current
COMMAND 0x505 ECU → PC: assistance, state and diagnostics
ARM 0x506 / 0x516 ECU → PC / PC → ECU: operator request and command
STATUS / CONFIG 0x507 / 0x508 ECU → PC: state / PC → ECU: configuration
ACK 0x509 / 0x519 ECU → PC / PC → ECU: transaction confirmation

The 64-byte SLX FD 1 payload: session identity, correlation, local timestamp, four values and application CRC

The application contract is shared by both transports. Its CRC and identity checks complement the link's own checks.

Encoding is little-endian. Version, type and flags occupy the first four bytes, followed by session, run, sequence, transaction, sample, boot identity and source age. The 64-bit local timestamp is diagnostic. Four signed 32-bit integers carry service-specific values, followed by detail and an IEEE CRC-32 over the first 60 bytes. Quantities use explicit integer scales such as mNm, µm and mA.

The same contract over Ethernet

The Ethernet path encapsulates the same application frame in an 80-byte UDP datagram: a 16-byte header with SLXD magic, version, flags, length and ID, followed by the 64-byte SLX FD 1 payload. The PC uses port 48050 and the controller port 48051. Bench networking uses DHCP with an AutoIP fallback.

UDP preserves message boundaries but does not guarantee delivery or ordering; application behaviour must account for this, as described by RFC 768. SteerDrive therefore checks freshness, sequence and session membership over both transports. Reusing the contract allows links to be compared without changing the meaning of measurements.

This path carries control data over conventional Ethernet. It does not implement DoIP, TSN or an Automotive Ethernet stack, and does not reproduce electrical CAN arbitration on the Ethernet cable.

Faults, shutdown and reconnection

A valid but old command is unusable. The controller checks declared age and locally measured transaction duration: a 30 ms request deadline, 40 ms maximum data age and 60 ms receive timeout. The PC imposes a 50 ms command-freshness limit relative to its own sample. It does not subtract timestamps from different clocks; duplicates and packets from an old session do not renew the deadline.

Missing data, inconsistent sessions, CAN I/O errors, bus-off or sustained overcurrent place the bench in its defined fault state and zero the assistance request. The fault remains latched: reset is explicit and is separate from start. In the model, cutting current and torque is idealised; a real power stage requires its own shutdown chain and energy-dissipation path.

Controller INIT, READY, ACTIVE and FAULT states with explicit start, stop, latched faults and disarmed recovery

Link availability and assistance enablement are separate decisions. Restored communication does not restart the bench.

Orderly CAN closure has its own transaction. The PC requests stop with the DETACH flag, waits for the correlated ACK and then closes the USB adapter. The controller zeroes assistance and stops the session's periodic traffic. Reconnection requires a fresh opening exchange and a new start, so the node does not continue transmitting to a peer that has already disconnected.

The CRC and identifiers protect data consistency within the bench, without providing cryptographic authentication. This version operates on a trusted laboratory network; a connected product requires dedicated cybersecurity and update-protection requirements.

STM32–simulator verification

Firmware 0.4.2 was programmed and verified in QSPI. LCD, touch and transport selection were checked on the board, including consistent button and top-bar updates. The measurements from 12 November 2026 concern data exchange between the Discovery and PC software, with the motor, steering mechanism and load simulated.

Link verification Board–PC CAN FD Ethernet / UDP
Session duration 60 s 60 s
Valid COMMAND messages 5,959 5,970
Maximum observed link response 22.672 ms 21.905 ms
100 ms data interruption Shutdown and explicit recovery passed Shutdown and explicit recovery passed
Missed MCU cycles 0 0

For the final CAN profile, hardware counters reported zero lost RX frames, rejected TX frames, bus-off events and HAL errors. Orderly closure and a new connection without restarting the Discovery passed. The sessions include intentional data loss; message counts do not represent maximum throughput or a latency guarantee under every condition.

The message count documents exchange over the session. State transitions complete the interpretation: a restored link must leave the controller in a recognisable condition and let the operator decide when to start.

Exercised condition Verified behaviour Integration significance
100 ms data interruption Assistance disabled and fault latched The model stops using an expired command
Explicit reset Return to the disarmed state Link recovery remains separate from start
CAN session closure Stop, correlated ACK and adapter release The controller completes the exchange before USB closure
New CAN connection Session reopened without restarting the Discovery The connection cycle can be repeated while the board remains operational

The 100 ms interruption is the stimulus applied to communication; the results describe observed states and recovery. Response measurements always concern STM32 and simulator, with motor and mechanics modelled on the PC.

Firmware for automotive and automation

SteerDrive documents skills applicable to device development: STM32 porting, external-memory boot, RTOS tasks, torque and position control, touch HMI, CAN FD, Ethernet and diagnostics. The board has a verifiable role in the control loop, with observable responsibilities and data.

Silicon LogiX can support automation companies and automotive teams with firmware, service interfaces and verification benches. From an axis controller to an ECU verification tool, development starts with signals, actuators, response times, protocols and required fault behaviour. The simulator exercises these decisions before integration with the plant.

An automotive product requires project-specific OEM requirements, suitable hardware, calibration, electromagnetic compatibility, functional safety and validation processes. SteerDrive does not claim ISO 26262 compliance, an ASIL rating or an AUTOSAR implementation. The tests presented make the completed work and its extension towards a client's product assessable.

Discuss your firmware and verification bench

Technical references

SteerDrive specifications and results refer to version 0.4.2. The cover shows the native HMI in the test environment; the HMI figure distinguishes the board framebuffer from previews.


Originally published on Silicon LogiX.

Top comments (0)