Config for GD32 MCUs

Sysprogs forums Forums VisualGDB Config for GD32 MCUs

This topic contains 9 replies, has 4 voices, and was last updated by  Johanan 1 week ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
  • #30026


    There are some problems with purchasing microcontrollers from ST manufacturer.
    Now there are a lot of their clones. The most popular is GigaDevice. Therefore, the question arises with the support of these microcontrollers.
    Can you help with creating a debug support project? For example, for GD32F330.


    • This topic was modified 9 months, 1 week ago by  Kanifol.
    You must be logged in to view attached files.


    Sorry, we do not have any plans for supporting the Chinese clones of the ST devices. If you would like to get reliable development experience, please consider purchasing a genuine ST device and a genuine VisualGDB license.



    These are not ” Chinese clones of the ST devices”. These are geniuine devices with ARM licence. Shure they are pin to pin compatibile (and peripherial as well) with ST.  Gigadevices MCUs are fully suported by IAR or KEIL compilers.




    We generally cannot advise STM32-compatible devices that are not manufactured by ST (or for ST) to our users due to the following concerns:

    1. Many of the components of the ST software library are published under this license, that explicitly limits it to ST devices:

      This software or any part thereof, including modifications and/or derivative works of this software, must be used and execute solely and exclusively on or in combination with a microcontroller or microprocessor device manufactured by or for STMicroelectronics

      We are aware that some of the vendors provide their own software libraries, however the original ST libraries compatible with the genuine ST devices offer a wider selection of components, examples and libraries. Hence, we recommend using the original ST devices instead.

    2. We did a brief research on the availability of the ST-compatible devices on major distributors (DigiKey and Mouser). At the time of checking, they did not carry any of the devices we checked.
    3. We considered adding support for the STM32 Blue Pill board to Analyzer2Go some time ago and ran a few stress tests on some of the boards. As a result, the boards we tested stopped working. We did a brief online search involving the part number on one of the boards and found a few posts warning about the ST clones.
    4. Comparing Google Trends for STM32 and some of the compatible device families showed a heavy bias towards the STM32-related search inquiries. We concluded that focusing on improving the STM32 integration will make our product relevant to a larger user base, than adding support for STM32-compatible devices not manufactured by ST.
    5. We believe that the STM32 devices gained their popularity due to exceptionally well-designed and maintained software libraries, examples and configuration tools. As these tools are available free of charge and are funded by the sales of the genuine STM32 devices, and as an official ST partner, we believe it would be fair to advise our users to use the genuine STM32 parts.

    After carefully reviewing the factors mentioned above, we decided to not officially support them. That said, VisualGDB is very flexible and offers various workarounds in case you would like to target the devices that are not supported officially:

    1. VisualGDB is fully integrated with the IAR and Keil compiler, so you can simply install it and pick it in the Embedded Project Wizard if you would like to target a device not directly supported by VisualGDB.
    2. You can also try creating a project manually as shown in this tutorial. This will also work with any device that is not directly supported by VisualGDB, but is based on a supported core (e.g. ARM).
    • This reply was modified 3 months, 1 week ago by  support. Reason: clarified the reasons for not supporting the devices


    GD32FXXXX  is not compatible with STM32, it is legit and can be purchased at Digikey, Mouser and any other component supplier.

    These are ARM devices, and in todays chips shortage, many of us are working very hard to find some solutions to the huge shortage. Using GigaDevice is some what a solution.  I think you should reconsider adding these ARM chips to VisualGDB. STM32 chips are simply unavailable, at almost any price.



    Thank you for your feedback. We will continue monitoring the relative popularity of different device families and will consider directly supporting the ones becoming more popular.



    Actually STM32F303CC can be used as a target for GD303CC, However I am using GD32F303VG, which has 1024K flash and 96K SRAM.

    Is there a simple way to tweak the device configuration so this full memory range can be used?

    ( I changed the linker script, but the it is not enough)




    As we have explained above, using the ST drivers with a non-ST device would be directly against the ST license terms, and may result in undefined behavior. We do not advise anyone to do it and cannot provide any help with it.



    Well,  as already said,  you can’t use ST drivers  as the chips are not compatible. You need to use GD driver library and remove all ST files from the project. I don’t see any problem in using gcc for this chip.



    The easiest way to use GD devices with VisualGDB is to import the Keil project in the GD examples template. Then Visual GDB ask for the chip, select any CortexM(x) from the available list according to the Cortex core, set correct link script according to available memories. Now you have a project with all hardware drivers  that complies. Add your own sources as needed.

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.