Add STM32 F413ZH bxCAN board config#420
Draft
nhuvaoanh123 wants to merge 9 commits into
Draft
Conversation
nhuvaoanh123
added a commit
to nhuvaoanh123/openbsw
that referenced
this pull request
Mar 30, 2026
Configure the DoCAN transport layer for STM32 UDS diagnostics: - DoCanSystem: Change CAN addressing from S32K default (0x02A/0x0F0) to standard OBD-II UDS IDs (0x7E0 request / 0x7E8 response) - appConfig: Update LOGICAL_ADDRESS to 0x0600 for STM32 diagnostics - DiagSession: Add AppProgrammingSession that uses programming-session response byte (0x02) without triggering bootloader shutdown — enables UDS programming-session services while keeping the dispatcher alive The DiagSession change affects all platforms but only activates when PLATFORM_SUPPORT_UDS=ON. Existing S32K and POSIX builds are unaffected as they use different session configurations. Milestone: TesterPresent (0x3E) works end-to-end over CAN bus with PR 10. Depends on eclipse-openbsw#420 (PR 8: F413ZH). PR 9 of 10.
This was referenced Mar 30, 2026
nhuvaoanh123
force-pushed
the
stm32-pr-8
branch
from
3ab3192 to
1804a3b
Compare
nhuvaoanh123
pushed a commit
to nhuvaoanh123/openbsw
that referenced
this pull request
Mar 30, 2026
Configure the DoCAN transport layer for STM32 UDS diagnostics: - DoCanSystem: Change CAN addressing from S32K default (0x02A/0x0F0) to standard OBD-II UDS IDs (0x7E0 request / 0x7E8 response) - appConfig: Update LOGICAL_ADDRESS to 0x0600 for STM32 diagnostics - DiagSession: Add AppProgrammingSession that uses programming-session response byte (0x02) without triggering bootloader shutdown — enables UDS programming-session services while keeping the dispatcher alive The DiagSession change affects all platforms but only activates when PLATFORM_SUPPORT_UDS=ON. Existing S32K and POSIX builds are unaffected as they use different session configurations. Milestone: TesterPresent (0x3E) works end-to-end over CAN bus with PR 10. Depends on eclipse-openbsw#420 (PR 8: F413ZH). PR 9 of 10.
nhuvaoanh123
force-pushed
the
stm32-pr-8
branch
from
1804a3b to
0a54681
Compare
nhuvaoanh123
added a commit
to nhuvaoanh123/openbsw
that referenced
this pull request
Mar 30, 2026
Configure the DoCAN transport layer for STM32 UDS diagnostics: - DoCanSystem: Change CAN addressing from S32K default (0x02A/0x0F0) to standard OBD-II UDS IDs (0x7E0 request / 0x7E8 response) - appConfig: Update LOGICAL_ADDRESS to 0x0600 for STM32 diagnostics - DiagSession: Add AppProgrammingSession that uses programming-session response byte (0x02) without triggering bootloader shutdown — enables UDS programming-session services while keeping the dispatcher alive The DiagSession change affects all platforms but only activates when PLATFORM_SUPPORT_UDS=ON. Existing S32K and POSIX builds are unaffected as they use different session configurations. Milestone: TesterPresent (0x3E) works end-to-end over CAN bus with PR 10. Depends on eclipse-openbsw#420 (PR 8: F413ZH). PR 9 of 10.
nhuvaoanh123
force-pushed
the
stm32-pr-8
branch
from
0a54681 to
fcd2075
Compare
nhuvaoanh123
added a commit
to nhuvaoanh123/openbsw
that referenced
this pull request
Mar 31, 2026
Configure the DoCAN transport layer for STM32 UDS diagnostics: - DoCanSystem: Change CAN addressing from S32K default (0x02A/0x0F0) to standard OBD-II UDS IDs (0x7E0 request / 0x7E8 response) - appConfig: Update LOGICAL_ADDRESS to 0x0600 for STM32 diagnostics - DiagSession: Add AppProgrammingSession that uses programming-session response byte (0x02) without triggering bootloader shutdown — enables UDS programming-session services while keeping the dispatcher alive The DiagSession change affects all platforms but only activates when PLATFORM_SUPPORT_UDS=ON. Existing S32K and POSIX builds are unaffected as they use different session configurations. Milestone: TesterPresent (0x3E) works end-to-end over CAN bus with PR 10. Depends on eclipse-openbsw#420 (PR 8: F413ZH). PR 9 of 10.
nhuvaoanh123
force-pushed
the
stm32-pr-8
branch
from
fcd2075 to
dc24f45
Compare
nhuvaoanh123
added a commit
to nhuvaoanh123/openbsw
that referenced
this pull request
Mar 31, 2026
Configure the DoCAN transport layer for STM32 UDS diagnostics: - DoCanSystem: Change CAN addressing from S32K default (0x02A/0x0F0) to standard OBD-II UDS IDs (0x7E0 request / 0x7E8 response) - appConfig: Update LOGICAL_ADDRESS to 0x0600 for STM32 diagnostics - DiagSession: Add AppProgrammingSession that uses programming-session response byte (0x02) without triggering bootloader shutdown — enables UDS programming-session services while keeping the dispatcher alive The DiagSession change affects all platforms but only activates when PLATFORM_SUPPORT_UDS=ON. Existing S32K and POSIX builds are unaffected as they use different session configurations. Milestone: TesterPresent (0x3E) works end-to-end over CAN bus with PR 10. Depends on eclipse-openbsw#420 (PR 8: F413ZH). PR 9 of 10.
nhuvaoanh123
changed the title
nhuvaoanh123
force-pushed
the
stm32-pr-8
branch
4 times, most recently
from
acd7ad5 to
004ce0f
Compare
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
force-pushed
the
stm32-pr-8
branch
2 times, most recently
from
75b9bd9 to
0745ab7
Compare
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.
Add the STM32 hard fault handler with RAM dump region and the IWDG watchdog driver. Add the G474RE safety manager sources and watchdog unit tests.
Add the NUCLEO-F413ZH reference application board: BSP configuration, board main with FreeRTOS and ThreadX variants, bxCAN CAN system, and the board presets.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
Description
Eighth PR in the STM32 platform series. Adds complete board support for the second STM32 Nucleo board.
NUCLEO-F413ZH specs
What's included
Platform matrix
Milestone
F413ZH builds and produces bootable ELF. Build:
cmake --preset nucleo-f413zh-freertos-gccDepends on #419 (PR 7: ThreadX). PR 8 of 10.
Related Issues
Part of STM32 platform port — see #413 for series overview.
Breaking Changes
Test Plan
CC=arm-none-eabi-gcc CXX=arm-none-eabi-g++ cmake --preset nucleo-f413zh-freertos-gcc && cmake --build --preset nucleo-f413zh-freertos-gccRegression Tests
Have tests been added/updated? [ ] Yes [x] No