Support for STM32F411E Discovery

[Octopus]

Any plan for supporting STM32F411E Discovery?

I saw that the MCU on this board (STM32F411xE) is already supported in the source tree so it should not be too hard to add it.

The documentation for this board is here in case that it is necessary.

[tfAteba]

Hello Octopus,

If there this board is not supported yet, I'm not sure that there is any plan to support it. But as you said the MCU is already support so the hardest part of a port have already been done.

Why don't you try to make the support of this board by your self , you can follow the porting guide that you can found here: http://wiki.chibios.org/dokuwiki/doku.php?id=chibios:guides:port_guide and you are in the first case "Porting to a new board" so you can follow the describe step to make the support .

I hope this can help you.

[opidmx512]

.., you can follow the porting guide that you can found here: http://wiki.chibios.org/dokuwiki/doku.php?id=chibios:guides:port_guide ...

This guide is pretty out-of-date. Any plans for updating that guide? I am considering to create a port for the Alwinner H2+ SoC (found on the Orange Pi Zero). An up-to-date porting guide would be much appreciated.

Thanks. Arjan

[Giovanni]

Hi,

I will look into the guide, but differences are mostly into paths, it is not going to get any easier porting to a whole new SOC. Basically you need to create the whole HAL LLD layer from scratch. You can see examples of those under /os/hal/ports, the good news are that you are porting to a single SOC, not a family of hundreds devices like STM32, that makes it much easier, especially for support, when it is done it is done, you don't have a continuous flow of new devices.

I recommend focusing on HAL, PAL and Serial LLDs first.

You may start looking at he original PI port, I don't know if there is commonality but it is worth trying.

Giovanni

[opidmx512]

Thank you Giovanni.

Some background

The Allwinner H2+ SoC is based on the Cortex-A7 ARM. The H3 SoC is similar:

Allwinner H3 (sun8iw7p1) SoC features a Quad-Core Cortex-A7 ARM CPU, and a Mali400 MP2 GPU from ARM.
H2+ is a variant of H3, targeted at low-end OTT boxes.
Reference : https://linux-sunxi.org/H3

Basically, I have all the low-level drivers ready here -> https://github.com/vanvught/rpidmx512/t ... ter/lib-h3

I just need the guidance on how to properly define the directory structure for the ARM Cortex-A7, SoC H2+/H3, and board. Where I would like to start with the Orange Pi Zero board. However, when I learn ChibiOS quickly, then the support for the Orange Pi One board can be there as well.

Thanks again, Arjan

[Giovanni]

Hi,

The ARM port is the existing one: /os/common/ports/ARM, I believe the previous PI port is using it too. Everything regarding device drivers is under /os/hal/ports, you may follow the STM32 or AVR pattern. Start with creating a directory with your device/family name, the LLD sub-directory contains a collection of drivers for the various IPs.

Giovanni

[opidmx512]

The ARM port is the existing one: /os/common/ports/ARM, I believe the previous PI port is using it too.
Giovanni

Hi Giovanni,

I assume that you are referring to the Raspberry Pi port. That one is 7 years old (https://github.com/steve-bate/ChibiOS-RPi), an old board, therefore not using the ARM Cortex-A7.

Looking at https://github.com/ChibiOS/ChibiOS I cannot find any implementations for the ARM Cortex-A7. I am not sure what I should create. For sure the mmu.c/mmu.h And what about cache-v7 functions? It's own H2+/H3 ld in https://github.com/ChibiOS/ChibiOS/tree ... ers/GCC/ld ?

Maybe I should just wait for the updated port guide.

- Arjan

[Giovanni]

Hi,

The ARM port works also for Cortex-A7: /os/common/ports/ARM

It is missing FPU support for context switching, if you need FPU that is the enhancement area but you can skip it initially.

Giovanni