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

[feature] Support for STM32G491 and STM32H7A3/H7B3 #1164

Closed
jjamesson opened this issue Jul 20, 2021 · 2 comments · Fixed by #1145
Closed

[feature] Support for STM32G491 and STM32H7A3/H7B3 #1164

jjamesson opened this issue Jul 20, 2021 · 2 comments · Fixed by #1145

Comments

@jjamesson
Copy link

Dear STLINK maintainers,

We are considering using STM32G491, and STM32H7A3/STM32H7B3 in our designs.

As of now, it seems that these boards are not supported by ST tools yet. Could we expect support from your toolset for these chips in the near future? It would be very helpful.

With best regards!

@Ant-ON
Copy link
Collaborator

Ant-ON commented Jul 21, 2021

@jjamesson I added support for these chips earlier (9eb81e1 and 54000d6 already in the develop branch). I had nothing to test these chips on, but everything should work. Support for the H7 and G4 series has been added previously and has been tested.

@jjamesson
Copy link
Author

jjamesson commented Jul 21, 2021

Thanks for the reply, @Ant-ON ,

You're right, I checked the /doc/devices_boards.md file (under "develop" branch) and saw that these chips weren't supported according to the list, but I didn't try the development branch myself.

Thanks,

@stlink-org stlink-org locked as resolved and limited conversation to collaborators Jul 28, 2021
@Nightwalker-87 Nightwalker-87 linked a pull request Jul 28, 2021 that will close this issue
@Nightwalker-87 Nightwalker-87 changed the title [feature] Support for G491 and H7A3/H7B3 [feature] Support for STM32G491 and STM32H7A3/H7B3 Jul 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants