boards: arm: Add gd32e103v_eval board

[feilongfl]

This PR adds support for GigaDevice GD32E103VBT6 SoC and GD32E103V-EVAL board that is use the SoC.

Currently, the west module dependency points to https://github.com/feilongfl/hal_gd32 (most of these code was download from gigadevice's website, -> Documents & Software -> Firmware Library)
I'm not sure where can I put these code,I found another issues #34971 have gigadevice RISKV device,but I think it's not good to put code there.

At this time, Only samples/basic/blinky is work.And lots of code is copy from stm32, So some code is not necessary.
I'll remove them later.

[github-actions]

The following west manifest projects have been modified in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_gigadevice	zephyrproject-rtos/hal_gigadevice@242a7f4	zephyrproject-rtos/hal_gigadevice@cc85acb (main)	zephyrproject-rtos/[email protected]

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[carlescufi]

@feilongfl thank you for this PR. Regarding the .dtsi files in the https://github.com/feilongfl/hal_gd32 repo, are those present in the upstream repository that this was taken from? If they are not, then you should put them in the main zephyr tree instead.

In general the policy is: if it's written exclusively for Zephyr it should be in the main zephyr tree. If it's part of a cross-RTOS HAL or library that is published separately then it belongs in the external module repo.

[carlescufi]

Currently, the west module dependency points to https://github.com/feilongfl/hal_gd32.

Could you please describe in the main body of this PR where this code comes from?

[feilongfl]

@feilongfl thank you for this PR. Regarding the .dtsi files in the https://github.com/feilongfl/hal_gd32 repo, are those present in the upstream repository that this was taken from? If they are not, then you should put them in the main zephyr tree instead.

In general the policy is: if it's written exclusively for Zephyr it should be in the main zephyr tree. If it's part of a cross-RTOS HAL or library that is published separately then it belongs in the external module repo.

I got it, i will move these dtsi code to zephyr prj.

Could you please describe in the main body of this PR where this code comes from?

most of these code was download from gigadevice's website, -> Documents & Software -> Firmware Library

[nandojve]

Hi @carlescufi ,

Do you think Zephyr project can add at least hal_gigadevice ? I have an gd32f403 minimal working too. It was just a test but I can clean up e fix docs and that can be very useful. GigaDevices ARM firmwares are pretty easy to be used with Zephyr.

• hal_gigadevice - need check licenses
• gd32f403 - need clean up and fix docs.

GigaDevices provides a firmware library and tools for all ARM and RISC-V at GigaDevices Download Site .

[feilongfl]

I've move *.dtsi from module to zephyr repo and migrate to latest version.

[feilongfl]

I've migrated this pr to latest main branch. If somewhere need modify, just let me know.

@carlescufi

[nandojve]

Hi @feilongfl !
Two comments only.

[gmarull]

LGTM, a couple of minor comments before approval

[gmarull]

I think this should be:

group1 {
    pinmux = <I2C0_SCL_PB6_NORMP>, <I2C0_SDA_PB7_NORMP>;
    drive-open-drain;
};

[feilongfl]

Although the eval board SCL have pull-up resistors, but I'm not sure as IIC master, does SCL needs to be open-drain?
😕

[gmarull]

You still need it, e.g. for https://www.i2c-bus.org/clock-stretching/

[nandojve]

Hi @feilongfl,
Thank you so much.

[tianrking]

LGTM