Are there plans to support stm32h7 devices?

[elrosch]

Are there any plans to support stm32h7 devices in the near future?

Playing around with lbuild and adapting the platform modules of rcc and gpio I (almost) managed to have a succesful build of the blinky example. The linking stage is still failing due to some memory section overflow. I guess i'll have to adapt something there as well. Probably you can point me somewhere in case I missed something obvious.

However, as far as I can judge, the h7 devices stand out a bit compared to the other stm32 devices.
At least the clock tree configuration seems to be quite different.
Would be interesting to know your plans regarding the stm32h7 devices.

Edit:
I just discovered this PR which includes some of the adaptations I was doing as well (good to know I was on the right path). I additionally did some adaptations to the rcc module although I wasn't able to test it due to the failing link stage.

[salkinium]

Yes, I even have a STM32H7 lying around somewhere, but I got it before discovering the clock tree and power peripheral complexity and then was a bit demotivated to actually continue porting this.

If you open a PR with your code, I'll very happily check out the linker issue (should theoretically use this linkerscript template due to caches etc.)
You can ignore the full clock tree for now and just use the 8MHz it boots with or hardcode some specific clock config in the SystemClock to test all the other peripherals. That way it isn't such a blocker right away.

[salkinium]

Also note that the STM32H7 data in modm-devices may not be accurate, since the memory layout is just… hardcoded… 🙈

[elrosch]

Ok I guess that could explain the linking issues 😬
Although the memory sections don't look too different from the one's I have been using in other projects.

Here is the PR: #379
I did not yet dig very deep into the datasheets so the changes are probably pretty incomplete.

[salkinium]

Single-core STM32H7 devices are now supported since #652.