B-G474E-DPOW1 STM32G474 Board Support

jhgorse · December 22, 2019, 7:15pm

It appears the discovery board for G474 is not yet supported.

How do we add support? It looks like a fairly easy port.

Cheers,
Joe

Pekka01 · December 31, 2019, 1:10pm

Hi Joe,

To be able to do official port you have to be a partner. For your own purposes you can mock it look like supported board:

github.com

ARMmbed/mbed-os-tools/blob/master/packages/mbed-ls/README.md#mocking-renaming-platforms

# Development moved

The development of Mbed LS has been moved into the [mbed-os-tools](../../src/mbed_os_tools) package. You can continue to use this module for legacy reasons, however all further development should be continued in the new package.

-------------

[![PyPI version](https://badge.fury.io/py/mbed-ls.svg)](https://badge.fury.io/py/mbed-ls)

# Mbed LS

Mbed LS is a Python (2 and 3) module that detects and lists Mbed Enabled devices connected to the host computer. The Mbed OS team publishes Mbed LS on PyPI. It works on all major operating systems (Windows, Linux and Mac OS X).

It provides the following information for all connected boards in a console (terminal) output:

- Mbed OS platform name.
- Mount point (MSD or disk).
- Serial port.

# Installation

This file has been truncated. show original

Regards,
Pekka

Pekka01 · December 31, 2019, 1:15pm

Hi Joe,

Here is more information how to use custom board.

github.com

ARMmbed/mbed-os-5-docs/blob/development/docs/porting/custom-target-porting.md

# Using Mbed OS on a custom board

When designing a custom microcontroller board to run Mbed OS, you may need to make software customizations for the unique design choices you have made for your new board, such as clocking, pin connections and peripheral use. You can accomplish this by adding configuration and source files to an Mbed OS-based application project without the need to modify files within Mbed OS, itself. You can add a file named `custom_targets.json` to your project, which can store your custom target configurations. If your board is based on an existing Mbed Enabled microcontroller, you can simply extend that board configuration without the need to implement all the files yourself.

This tutorial covers the most common methods used to create a custom port of Mbed OS when starting from an existing Mbed Enabled board. For detailed information on how to create a port from scratch, go to the [Mbed Porting guide](../porting/index.html). Additionally, not all possible aspects of target configuration are covered. For detailed information on all the ways you can configure targets, go to [adding and configuring targets](../reference/adding-and-configuring-targets.html).

## Extending an existing MCU target configuration

Consider a situation in which you are creating a new board based on an existing Mbed Enabled board. This tutorial lists the steps to create the software for a new board we will call `ImaginaryBoard`. This board is based on [DISCO-L475VG-IOT01A](https://os.mbed.com/platforms/ST-Discovery-L475E-IOT01A/). It shares most of the features of DISCO-L475VG-IOT01A, but it does not use `AnalogOut`, `AnalogIn`, `CAN` or `USB`. Some pins are connected differently on the new board. 

Follow these steps to create a custom port for Mbed OS:

### Preparing

1. [Install Mbed CLI](../tools/installation-and-setup.html) if you don't already have it.

1. (Optional) Create a new Mbed program (for example, `mbed-os-imaginary-port`).

   If you don't already have an Mbed program on your computer, run this Mbed CLI command in a command terminal:

This file has been truncated. show original

Regards,
Pekka

jhgorse · December 31, 2019, 6:47pm

Thank you, Pekka.

jeromecoutant · January 2, 2020, 9:47am

Hi all

In order to introduce a new target/STM32 family, you can have a look on the wiki page: https://os.mbed.com/teams/ST/wiki/steps-to-create-a-new-STM32-platform

Don’t hesitate to make a pull request on GitHub, we will review it in order to merge it !

Thx

Jerome, ST team

jhgorse · January 4, 2020, 1:59am

Jerome,

Thanks for the link.

So it appears we will have to add a new and for the STM32G474.
TARGET_STM32\TARGET_STM32
TARGET_STM32G4\TARGET_STM32G474xE\TARGET_DISCO_G474RE

Any thoughts on what to call the TARGET_? Perhaps TARGET_DISCO_G474RE?

Then it looks like generating the PeripheralPins.c using the python script. I do not have CubeMX installed.

Looks like other things need copied from the STM32Cube package as well.

Cheers,
Joe

aglass0fmilk · February 17, 2020, 5:52pm

I am also interested in support for the STM32G4 series in Mbed.

I can look into porting. As for the target name, it should be consistent with the other nucleo boards supported by Mbed: TARGET_NUCLEO_G474RE

Jerome, is this support coming relatively soon ?

jeromecoutant · February 18, 2020, 9:53am

Hi

I am sorry, but STM32G4 support is not planned soon

2 options:

if you have contact in ST sales team, please contact them
I pushed a development branch in https://github.com/jeromecoutant/mbed/tree/DEV_STM32G4
This is what I can give with “automatic” internal scripts.
You can use it as a starting point.

Regards
Jerome

aglass0fmilk · February 18, 2020, 10:22am

Hi Jerome,

I just ordered a G473 nucleo board so I will be able to run tests. I’ll see how difficult the porting effort is from here.

Thanks for getting it started!

aglass0fmilk · February 20, 2020, 2:43pm

Hi Jerome,

I took your branch and have basic support for the NUCLEO_G747RE target (gpio and system initialization, enough to compile blinky while ignoring a lot of features that require UART).

You can see my branch here: https://github.com/AGlass0fMilk/mbed-os/tree/add-nucleo-g474re

I am hoping we can collaborate a bit to add the rest of the features since you are obviously more familiar with the STM platform than I am.

Maybe you could convince your project managers to give you some time to assist me since there is another developer working on this now :)?