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

Switch CAN port definiton on Nucleo-496 hwdef #23070

Closed

Conversation

RobertatPegasus
Copy link
Contributor

The CAN port as it was is a valid CAN port for the Nucleo, but on the development board the CAN silkscreen is actually on PD0 and PD1. This change makes it easier to get the example running on the Nucleo.

This was tested on a real Nucleo board. The CAN tx/rx was plugged in to a tranceiver which was plugged in to a pixhawk 4. I installed the bootloader first on the nucleo with an st-link, then updated the firmware image with mission planner. The Nucleo was active on the CAN bus in both images.

The CAN port as it was is a valid CAN port for the nucleo, but on the development board the CAN silkscreen is actually on PD0 and PD1. This change makes it easier to get the example running on the Nucleo
@peterbarker
Copy link
Contributor

Thanks for this.

I've fixed up the commit list and commit messages to conform to our standards and created a new PR here: #28229 (I was unable to force-push your branch here).

I've marked that new PR as MergeOnCIPass.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants