-
Notifications
You must be signed in to change notification settings - Fork 41
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
[UAVCAN/CAN] Create STM32 FDCAN Driver #9
Comments
For reference @JacobCrabill added this legacy libuavcan stm32h7 driver in PX4. https://github.com/PX4/Firmware/tree/master/src/drivers/uavcan/uavcan_drivers/stm32h7/driver |
Nice. @dagar can we adapt it to support CAN FD (it seems to support only Classic CAN at the moment) and refactor it to remove dependencies on Libuavcan v0? Much like we did for bxCAN. That would be super useful. |
I'm actually (slowly) going through the process of adding Socket can support for the H7 series in Nuttx; I can make my WIP public if it speeds things up. |
It might, but what we really need is someone willing to do the actual work of extracting the low-level logic from the v0/NuttX driver into a separate reusable component. |
@pavel-kirienko I guess your goal here is to have a standalone set of files to put into any generic project, not just NuttX / PX4? I think the long-term goal for PX4 is to simply have all the drivers built into NuttX; that's the approach taken by @PetervdPerk-NXP for the UAVCAN v1 test setup on the NXP CAN boards, and it makes sense to me. I don't think it would be too difficult to take what I put together (based on the outline of your bxCAN driver) and make it libuavcan-independent. |
Has anyone developed a fdcan driver compatible with libuavcan/libcanard? |
Under NuttX there's Cyphal support which uses the SocketCAN api. |
Are you looking for a CAN FD HAL driver, i.e. for specific MCU platform? The 107-Arduino-Systems would support CAN FD frames via libcanard (and can be cross-compiled via |
Create a driver for FD reference board: STM32H743 Nucleo-144 (ST micro)
The text was updated successfully, but these errors were encountered: