Skip to content

added CAN GPIO configuration to bxcan README caveats #48

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.

Sign up for GitHub

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

Merged
pavel-kirienko merged 1 commit into from
Mar 31, 2025
Merged

added CAN GPIO configuration to bxcan README caveats #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions stm32/libcanard/bxcan/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,8 @@ In order to avoid frame loss due to RX overrun, the following measures should be
* The driver does not permit concurrent access from different threads of execution.
* The clocks of the CAN peripheral must be enabled by the application before the driver is
initialized. The driver cannot do that because this logic is not uniform across the STM32 family.
* The driver does not configure CAN GPIOs, as they vary by hardware setup.


Note that it is possible to invoke the driver's API functions from IRQ context, provided that the
application takes care about proper guarding with critical sections.
Expand Down