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.

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

Jump to bottom

Nucleo l476 rg analog #1045

Merged
merged 3 commits into from Jan 31, 2017
Merged

Nucleo l476 rg analog #1045

merged 3 commits into from Jan 31, 2017

Conversation

VVESTM
Copy link
Contributor

@VVESTM VVESTM commented Jan 31, 2017

Hello Gordon,

Here are some updates for Nucleo L476 RG board.
It adds adc and dac functionnalities.

Regards
Vincent

@gfwilliams
Copy link
Member

Cool - thanks!

@gfwilliams gfwilliams merged commit 43ad82c into espruino:master Jan 31, 2017
@VVESTM
Copy link
Contributor Author

VVESTM commented Feb 1, 2017

Thanks Gordon
With this pull request, the SW concerning stm32 low layer api on NucleoL476RG is pretty complete.

Vincent

@gfwilliams
Copy link
Member

Wow, thanks! How portable do you think this is to different parts?

There's a post on the forum at the moment where someone is trying to port to the Nucleo F413:

http://forum.espruino.com/conversations/299344/#comment13447980

@VVESTM
Copy link
Contributor Author

VVESTM commented Feb 1, 2017

Low Layer API are done to ease the portage on differents chips. It will be portable if there is no big difference on the IP used.
Unfortunately, this is not yet available on all the platforms. The first family to benefit of this API was L4. It will come for F4 during first or second quarter. So need to wait a little bit more for F413...
Once the LL is available on F4, it should be straight forward to run my software on this board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@VVESTM @gfwilliams