Porting to STM32MP1: Ethernet and other Peripherals

[Tom Moulton]

I am not using Linux.

Is the peripheral set used on the STM32MP1 brand new or imported from another STM32 Family?

Tom

[PatrickF]

Many peripherals come from STM32F4, STM32F7 and STM32H7 family, with some updates.

Obviously, this is not true for peripherals which are different to support extended features of STM32MP1 family (e.g. ETH, GIC, BSEC, FMC, GPU, USBH, USBPHYC, DDRCTRL, DDRPHYC, etc..).

If a peripheral driver is not available in CubeMP1 (which can be usually ported to A7), it is up to you to manage the SW.

We do not provide SW support for A7 bare metal.

Maybe AN5253 could help.

[Tom Moulton]

The App Note AN5253 appears to focus on the M4 side only.

"We do not provide SW support for A7 bare metal"

So it seems the A7 support is limited to Linux? That is disappointing.

Tom

[PatrickF]

When I mean 'support' is that ST we did not offer SW solution outside Linux.

Some OpenOS are planned for STM32MP1 family, there is for instance 3rd party which will port Android.

Cortex-A7 bare metal is not avoided by the HW (TF-A and u-Boot stages are obviously not using Linux) and some customers started development for A7 bare-metal on their side.

Only the GPU is likely not usable outside an OpenOS as requiring libraries not provided in source code.