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

STM32H747XI #1

Open
ericlewis opened this issue Jan 9, 2020 · 2 comments
Open

STM32H747XI #1

ericlewis opened this issue Jan 9, 2020 · 2 comments

Comments

@ericlewis
Copy link

I am interested in adding support for STM32H747XI. I read your thesis, great work! Curious of some pointers on how to go about this, as well as wondering how/if you would prefer this be added to this repo.

@dragomirecky
Copy link
Member

Hey Eric and sorry for the late reply!

Yes, I think it would be great if HAL for STM32H7 would be part of this library (maybe as a STM32H7 library?)

I think the first part of adding support for this MCU would be extending cross to make it easy to build a library/application for this microcontroller. It is just about generating the right linker script and compiler flags. I think the only difference from STM32F439ZI might be the memory layout in the linker script and changing some compiler flags (definitions).

With cross working, you can then try the board with some simple program and verify that it is running as expected (just a for loop, attach to it with debugger and check it does the expected 😊)

Then I would focus on creating a HAL. The easy approach is just to take an official C HAL and create a Swift wrapper around it. I am not sure how much of the functionality is shared with STM32F4, but in case it is similar enough, we might even consider making one shared STM32 library (instead of multiple separate libraries like STM32F4, STM32H7, etc).

I hope this helps. Let me know if you have any other questions – having support for STM32H747XI would be awesome! 🙃

@ericlewis
Copy link
Author

Awesome! Thanks for the reply! I will be picking this up probably around the end of feb.

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

No branches or pull requests

2 participants