Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: CAN-FD support not in support matrix for STM32 Nucleo G0B1 or G474 #67087

Closed
WardBenjamin opened this issue Jan 1, 2024 · 5 comments · Fixed by #67430
Closed

doc: CAN-FD support not in support matrix for STM32 Nucleo G0B1 or G474 #67087

WardBenjamin opened this issue Jan 1, 2024 · 5 comments · Fixed by #67430
Assignees
Labels
area: CAN Enhancement Changes/Updates/Additions to existing features platform: STM32 ST Micro STM32

Comments

@WardBenjamin
Copy link

Describe the bug

The STM32G0B1 has two CAN-FD peripherals available. Zephyr already supports one since #54403. Here is the current permalink:

Meanwhile, the "supported features" matrix on the Nucleo G0B1RE page does not list any CAN support.

Environment

  • Page: boards/arm/nucleo_g0b1re/doc/index
  • Version: main
  • SHA-1: 5d5249d
Copy link

github-actions bot commented Jan 1, 2024

Hi @WardBenjamin! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

@WardBenjamin
Copy link
Author

WardBenjamin commented Jan 1, 2024

Side note: what needs to happen for Zephyr to properly support the second CAN-FD peripheral on this chip? I saw some notes about shared IRQs being an issue here #34963 but it is unclear to me whether that's been resolved in the two years since. EDIT: looks like this is still an open issue #49379? EDIT2: Maybe now this is implemented #61422?

@WardBenjamin WardBenjamin changed the title doc: Documentation issue in 'boards/arm/nucleo_g0b1re/doc/index' doc: CAN-FD support not in support matrix for STM32 Nucleo G0B1 or G474 Jan 1, 2024
@WardBenjamin
Copy link
Author

It looks like this is also an issue on the Nucleo G474 page:

@henrikbrixandersen henrikbrixandersen added Enhancement Changes/Updates/Additions to existing features platform: STM32 ST Micro STM32 area: CAN labels Jan 1, 2024
@henrikbrixandersen henrikbrixandersen self-assigned this Jan 1, 2024
henrikbrixandersen added a commit to vestas-wind-systems/zephyr that referenced this issue Jan 10, 2024
List FDCAN1 as supported in the board documentation.

Fixes: zephyrproject-rtos#67087

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
henrikbrixandersen added a commit to vestas-wind-systems/zephyr that referenced this issue Jan 10, 2024
List FDCAN1 as supported in the board documentation.

Fixes: zephyrproject-rtos#67087

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
@henrikbrixandersen
Copy link
Member

Documentation additions: #67430

@henrikbrixandersen
Copy link
Member

Side note: what needs to happen for Zephyr to properly support the second CAN-FD peripheral on this chip? I saw some notes about shared IRQs being an issue here #34963 but it is unclear to me whether that's been resolved in the two years since. EDIT: looks like this is still an open issue #49379? EDIT2: Maybe now this is implemented #61422?

This is a separate issue, but shared interrupts are now supported at the architecture level in Zephyr.

henrikbrixandersen added a commit that referenced this issue Jan 11, 2024
List FDCAN1 as supported in the board documentation.

Fixes: #67087

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
henrikbrixandersen added a commit that referenced this issue Jan 11, 2024
List FDCAN1 as supported in the board documentation.

Fixes: #67087

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: CAN Enhancement Changes/Updates/Additions to existing features platform: STM32 ST Micro STM32
Projects
None yet
2 participants