Skip to content

Add STM32 FDCAN transceiver adapter#416

Draft
nhuvaoanh123 wants to merge 5 commits into
eclipse-openbsw:mainfrom
nhuvaoanh123:stm32-pr-4
Draft

Add STM32 FDCAN transceiver adapter#416
nhuvaoanh123 wants to merge 5 commits into
eclipse-openbsw:mainfrom
nhuvaoanh123:stm32-pr-4

Conversation

@nhuvaoanh123

Copy link
Copy Markdown
Contributor

Purpose of this PR

  • Bugfix
  • New Feature
  • Documentation Update
  • Other

Description

Fourth PR in the STM32 platform series. Adds the FDCAN transceiver adapter, completing CAN support for both STM32 families.

Module added

Module Purpose
fdCanTransceiver OpenBSW ICanTransceiver adapter for STM32G4 FDCAN peripheral

Mirrors the bxCAN transceiver (PR 3) but supports FD frames with up to 64-byte payload and extended filter configuration.

Milestone

Both CAN transceiver variants (bxCAN + FDCAN) now available. Tests: FdCanTransceiverTest, FdCanTransceiverIntegrationTest.

Depends on #415 (PR 3: CAN drivers). PR 4 of 10.

Related Issues

Part of STM32 platform port — see #413 for series overview.

Breaking Changes

  • Yes
  • No

Test Plan

  1. Configure: cmake --preset tests-stm32-debug
  2. Build and run: cmake --build --preset tests-stm32-debug && ctest --preset tests-stm32-debug
  3. Tests: FdCanTransceiverTest, FdCanTransceiverIntegrationTest

Regression Tests

Have tests been added/updated? [x] Yes [ ] No

nhuvaoanh123 added a commit to nhuvaoanh123/openbsw that referenced this pull request Mar 30, 2026
Add fault handling and watchdog safety infrastructure:

- hardFaultHandler: ARM Cortex-M4 HardFault handler in assembly — captures
  register state (R0-R12, LR, PC, PSR) for post-mortem analysis
- safeBspMcuWatchdog: IWDG (Independent Watchdog) driver with configurable
  timeout, kick interface, and reset-reason detection
- SafetyManager: Board-level safety lifecycle integration for G474RE

Milestone: cmake configures with safety modules. Watchdog activates with PR 6 (RTOS).
Depends on eclipse-openbsw#416 (PR 4: FDCAN transceiver). PR 5 of 10.
nhuvaoanh123 pushed a commit to nhuvaoanh123/openbsw that referenced this pull request Mar 30, 2026
Add fault handling and watchdog safety infrastructure:

- hardFaultHandler: ARM Cortex-M4 HardFault handler in assembly — captures
  register state (R0-R12, LR, PC, PSR) for post-mortem analysis
- safeBspMcuWatchdog: IWDG (Independent Watchdog) driver with configurable
  timeout, kick interface, and reset-reason detection
- SafetyManager: Board-level safety lifecycle integration for G474RE

Milestone: cmake configures with safety modules. Watchdog activates with PR 6 (RTOS).
Depends on eclipse-openbsw#416 (PR 4: FDCAN transceiver). PR 5 of 10.
nhuvaoanh123 added a commit to nhuvaoanh123/openbsw that referenced this pull request Mar 30, 2026
Add fault handling and watchdog safety infrastructure:

- hardFaultHandler: ARM Cortex-M4 HardFault handler in assembly — captures
  register state (R0-R12, LR, PC, PSR) for post-mortem analysis
- safeBspMcuWatchdog: IWDG (Independent Watchdog) driver with configurable
  timeout, kick interface, and reset-reason detection
- SafetyManager: Board-level safety lifecycle integration for G474RE

Milestone: cmake configures with safety modules. Watchdog activates with PR 6 (RTOS).
Depends on eclipse-openbsw#416 (PR 4: FDCAN transceiver). PR 5 of 10.
nhuvaoanh123 added a commit to nhuvaoanh123/openbsw that referenced this pull request Mar 31, 2026
Add fault handling and watchdog safety infrastructure:

- hardFaultHandler: ARM Cortex-M4 HardFault handler in assembly — captures
  register state (R0-R12, LR, PC, PSR) for post-mortem analysis
- safeBspMcuWatchdog: IWDG (Independent Watchdog) driver with configurable
  timeout, kick interface, and reset-reason detection
- SafetyManager: Board-level safety lifecycle integration for G474RE

Milestone: cmake configures with safety modules. Watchdog activates with PR 6 (RTOS).
Depends on eclipse-openbsw#416 (PR 4: FDCAN transceiver). PR 5 of 10.
nhuvaoanh123 added a commit to nhuvaoanh123/openbsw that referenced this pull request Mar 31, 2026
Add fault handling and watchdog safety infrastructure:

- hardFaultHandler: ARM Cortex-M4 HardFault handler in assembly — captures
  register state (R0-R12, LR, PC, PSR) for post-mortem analysis
- safeBspMcuWatchdog: IWDG (Independent Watchdog) driver with configurable
  timeout, kick interface, and reset-reason detection
- SafetyManager: Board-level safety lifecycle integration for G474RE

Milestone: cmake configures with safety modules. Watchdog activates with PR 6 (RTOS).
Depends on eclipse-openbsw#416 (PR 4: FDCAN transceiver). PR 5 of 10.
@nhuvaoanh123 nhuvaoanh123 marked this pull request as draft May 1, 2026 19:17
@nhuvaoanh123 nhuvaoanh123 changed the title feat(stm32): FDCAN transceiver adapter for STM32G4 Add STM32 FDCAN transceiver adapter Jun 2, 2026
@nhuvaoanh123 nhuvaoanh123 deleted the stm32-pr-4 branch June 2, 2026 07:48
@nhuvaoanh123 nhuvaoanh123 reopened this Jun 2, 2026
@nhuvaoanh123 nhuvaoanh123 force-pushed the stm32-pr-4 branch 3 times, most recently from 3f3f817 to f07a53e Compare June 2, 2026 08:23
Import the STM32F4 and STM32G4 CMSIS device headers from
STMicroelectronics' dedicated RIM-tracked repositories. Keep only the
F413 and G474 headers needed by the STM32 MCU foundation and record
the unused upstream headers as RIM ignores.
Add the STM32 platform entry point, chip CMake files, bspMcu startup
code, a software reset wrapper, and the STM32 unit-test presets. The
platform reuses the shared CMSIS core from libs/3rdparty/cmsis
instead of carrying a local copy.
Add STM32 BSP modules for clock, UART, GPIO, timer, ADC, and EEPROM,
plus interrupt handling primitives and the ETL platform glue.
@nhuvaoanh123 nhuvaoanh123 force-pushed the stm32-pr-4 branch 2 times, most recently from 5f4c91e to c936b83 Compare June 11, 2026 00:09
Add bxCAN and FDCAN device drivers with STM32 CAN tests.

Add the bxCAN transceiver adapter and unit-test registration.
Add the FDCAN transceiver implementation and STM32 test coverage.

Wire the FDCAN transceiver into the chip-family CMake selection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant