Skip to content

[New Variant] NUCLEO-L412RB-P #2663

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

Closed
lylecheatham opened this issue Mar 1, 2025 · 2 comments · Fixed by #2713
Closed

[New Variant] NUCLEO-L412RB-P #2663

lylecheatham opened this issue Mar 1, 2025 · 2 comments · Fixed by #2713
Labels
new variant Add support of new bard
Milestone

Comments

@lylecheatham
Copy link

Board description

Hi there,

I'm willing to submit a PR for this but I'm a bit confused as to how! It seems that the guide in the wiki is for a "generic" board. Is a nucleo a generic board or how would I go about this? I'm switching a project I have over to this microcontroller and it's all Arduino code that I'd rather not port 😁

I found this previous Issue and it made it seem like version 2.0 would have it but it does not seem to be the case #1350

If you just point me in the right direction then I'll get going!

@fpistm fpistm added the new variant Add support of new bard label Mar 3, 2025
@fpistm
Copy link
Member

fpistm commented Mar 3, 2025

Hi @lylecheatham
Right, Wiki describes only the generic.
And no the 2.x does not provide this support, it was only mentioned in the issue that 2.0.0 have to be released before try to make a PR.
You can mimic any PR to see how dedicated board is added.
Like this one:
296fa63

@fpistm
Copy link
Member

fpistm commented Mar 4, 2025

Added to #722.

@fpistm fpistm closed this as completed Mar 4, 2025
@fpistm fpistm linked a pull request Apr 17, 2025 that will close this issue
@fpistm fpistm added this to the 2.11.0 milestone Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new variant Add support of new bard
Projects
Development

Successfully merging a pull request may close this issue.

2 participants