Port of MicroPython to STM32H750B-DK board ?

[LAPSyLAB]

Hello,

has anyone tried or has more info about port to STM32H750B-DK board ?
One limitation is probably Internal Flash of only 128KB, but plenty of QSPI Flash, so this shouldn't be a problem.
I've also heard about the problem with clock configuration - not sure if this one is true.

There is a port for STM32H7B3I_DK which seems to be the closest one. Has anyone tried or has advice how to approach port for STM32H750B-DK board ?

Thanks in advance,
regards.

[jahr]

Hello, some time ago I've written definitions for some H750 boards. Not the STM32H750B-DK but you may find how I dit it ;-) Check the articke here and (somehow outdated, but previously working ;-) ) definitions here and here.

[LAPSyLAB]

Thanks for info, will take a look. How did you compile micropython for those boards - CubeIDE ?

thanks.

[jahr]

No, I've never used CubeIDE for building MP. You may put the above mentioned definitions to ports/stm32/boards/ directory (e.g. clone it there) and then build it in the standard way, i.e. from ports/stm32/ directory run e.g. make BOARD=WEACT_H750. But keep in mind that these definitions were tested more than one year ago, so it is possible that the build may fail.

[LAPSyLAB]

Hello, Thanks for all the info and help. I think it will be much easier to start our port. We will let you know if definitions compile… Regards, Robert. From: Jan Hrudka ***@***.***> Sent: Thursday, December 15, 2022 10:10 AM To: micropython/micropython ***@***.***> Cc: LAPSy ***@***.***>; Author ***@***.***> Subject: Re: [micropython/micropython] Port of MicroPython to STM32H750B-DK board ? (Discussion #10219) No, I've never used CubeIDE for building MP. You may put the above mentioned definitions to ports/stm32/boards/ directory (e.g. clone it there) and then build it in the standard way, i.e. from ports/stm32/ directory run make e.g. BOARD=WEACT_H750. But keep in mind that these definitions were tested more than one year ago, so it is possible that the build may fail. — Reply to this email directly, view it on GitHub <#10219 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXLHQ2HG6BPS6ZKPPWP4JLWNLN7DANCNFSM6AAAAAAS6HLUWU> . You are receiving this because you authored the thread.Message ID: ***@***.***>