mbed-os lacks support for multiple GD32 chip series

maxgerhardt commented 3 years ago

Description of defect

The current state of mbed-os support for GigaDevice (ARM) chips is:

1 chip from the GD32F4xx series, GD32_F450ZI
1 chip from the GD32F30x series, GD32_F307VG, more specifically the GD32F307 sub-series
in the mbed-os 5.x branch: 1 chip from the GD32E10x series, GD32_E103VB

This means that a lot of other chip series have no support.

(Issue is intended for tracking purposes as more support gets added.)

Target(s) affected by this defect ?

[ ] GD32E23x (Cortex-M23)
[ ] GD32E50x (Cortex-M33)
[ ] GD32F10x (Cortex-M4)
[ ] GD32F1x0 (Cortex-M3)
[ ] GD32F20x (Cortex-M3)
[ ] GD32F3x0 (Cortex-M4)
[ ] GD32F403 (Cortex-M4)

Toolchain(s) (name and version) displaying this defect ?

All.

What version of Mbed-os are you using (tag or sha) ?

4cfbea43cabe86bc3ed7a5287cd464be7a218938

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

None relevant.

How is this defect reproduced ?

Attempting to use mbed-os with the above-mentioned chip series.

0xc0170 commented 3 years ago

@ARMmbed/team-gigadevice please review

0xc0170 commented 3 years ago

(Issue is intended for tracking purposes as more support gets added.)

I was wondering if I should close this issue, are the new targets coming?

maxgerhardt commented 3 years ago

We're talking about work that needs in the order of months to be done an PRed -- initial targets can be ticked off as we start sending PRs, but before that it makes no sense.

ARMmbed / mbed-os