Native GD32 support for Aquila v1.0.1

[bmourit]

Description

This adds support for Aquila v1.0.1 boards that shipped with GD32F103RC

Requirements

None

Benefits

This extends the GD32 native support to Aquila v1.0.1 GD32F103RC boards

Configurations

Configuration changes are similar to Creality v4.2.2 MFL. Serial port is 0 instead of 1

[bmourit]

Just wanted to mention as well. It was also linked in with the original platform support of GD32 but I think it just got missed. We need the changes of the PR I made in the u8glib repo in order to be able to actually compile and use the default LCD. Should I make a bug report here? I did everything in that repo itself.

[Nuck-TH]

I think page should be taken from structure of ini for stm32 - there should be separate sections for MCUs with mcu specific parameters and compiler flags/defines, and boards should extend them with board-specific things.

[bmourit]

I think page should be taken from structure of ini for stm32 - there should be separate sections for MCUs with mcu specific parameters and compiler flags/defines, and boards should extend them with board-specific things.

I'm fine with however it is done. It is a little different than the maple environment though since that is still the same MCU target whereas this is a different one. This one wont build or support the STM32, so it isn't interchangable like Maple. I do agree though that sharing as much as possible is ideal, so long as it is clear to the user. Marlin has done an excellent job with that so for, so however it is decided I fully support. :)

The chip shortage really made this messy though, with boards of the same printer/version shipped randomly with GD32/STM32/HC32 etc. A somewhat unique situation.

I suspect anything like that will likely be after the 2.1.3 release though, since it is already in beta.

EDIT:
I just re-read you comment. As far as the gd32.ini goes, we could do that. If we do plan to eventually add most/all boards then this may be useful. With only 2 boards as of right now, it just seemed a little overkill. But again, I'm fine with either.