GD32H759 Evalboard (GD32H759I-EVAL).

The following article explains all necessary steps to create an Embedded Wizard UI application suitable for the GD32H759 Evalboard (GD32H759I-EVAL) from GigaDevice.

Please follow these instructions carefully and step by step in order to ensure that you will get everything up and running on your target. In case you are not familiar with Embedded Wizard, please read first the chapter basic concepts and the Quick Tour tutorial to understand the principles of Embedded Wizard and the GUI development workflow.

First, make sure you have all of the following items:

If you just want to run our GUI demos on your GD32H759 Evalboard without building the different examples, you can simply flash the binary file of the Embedded Wizard Master Demo.

The Embedded Wizard Master Demo combines a variety of examples within one huge demo application. It can be used for presentations and showcases. Each demo application can be activated from a common main menu. To return back from a demo application to the main menu, a small home button appears on top of every demo. Additionally, the Master Demo contains an auto-demo mode that presents one demo application after the other. The auto-demo starts automatically and stops as soon as the user touches the screen.

In order to flash the binary file to your target, please follow these steps:

'Master Demo' running on GD32H759 Evalboard.

The provided Embedded Wizard Build Environment for GD32H759 Evalboard contains everything you need to create, compile, link and flash an Embedded Wizard UI application for the GD32H759 target. After unpacking, you will find the following subdirectories and files:

For the first bring up of your system, we recommend to use the example 'HelloWorld':

Example 'HelloWorld' within Embedded Wizard Studio.

The following steps are necessary to generate the source code of this sample application:

The following steps are necessary to build and flash the Embedded Wizard UI sample application using the GCC ARM embedded toolchain:

If everything works as expected, the application should be built and flashed to the GD32H759 target.

Example 'HelloWorld' running on GD32H759 Evalboard.

All other examples can be created in the same way: Just open the desired example with Embedded Wizard Studio, generate code and rebuild the whole application using simply:

In order to create your own UI project suitable for the GD32H759 target, you can create a new project and select the GD32H759 Evalboard project template:

As a result you get a new Embedded Wizard project, that contains the necessary Profile attributes suitable for the GD32H759 Evalboard:

The following profile settings are important for your target:

Now you can use the template project in the same manner as it was used for the provided examples to compile, link and flash the binary.

After generating code, please follow these steps, in order to build your own UI application:

Most of the project settings are taken directly out of the generated code, like the color format or the screen orientation. Only a few additional settings can be configured directly within the Makefile, like the usage of the FreeRTOS operating system. All other settings can be made directly within the file ewconfig.h, which contains general configuration settings for the target system.

In order to receive error messages or to display simple debug or trace messages from your Embedded Wizard UI application, a serial terminal like 'Putty' or 'TeraTerm' should be used.

During a successful application startup, the console displays the following information:

This terminal connection can be used for all trace statements from your Embedded Wizard UI applications or for all debug messages from your C code.

If you want to use the IAR Embedded Workbench instead of the GCC ARM embedded toolchain, please follow these instructions:

The subdirectory \Application\Project\EWARM contains a template project that is commonly used for all provided Embedded Wizard examples. All Embedded Wizard examples will store the generated code within the common \Application\GeneratedCode folder.

The generated code of an Embedded Wizard example is imported automatically to the IAR Embedded Workbench project using the Project Connection mechanism.

To establish this automatic project import a post process has to be added to the Profile settings within Embedded Wizard Studio:

After the Embedded Wizard code generation the installed post process will generate a ewfiles.ipcf file, that controls the import to the IAR Embedded Workbench project.

After returning to IAR Embedded Workbench, the latest generated code and the suitable Embedded Wizard Platform Package will be imported to the IAR Embedded Workbench project (depending on the color format and the screen orientation selected in the Embedded Wizard Profile).

If the color format or the screen orientation was changed, please do a complete rebuild of the IAR Embedded Workbench project.

If you want to use the Keil MDK-ARM toolchain instead of the GCC ARM embedded toolchain, please follow these instructions:

The subdirectory \Application\Project\MDK-ARM contains a template project that is commonly used for all provided Embedded Wizard examples. All Embedded Wizard examples will store the generated code within the common \Application\GeneratedCode folder.

The generated code of an Embedded Wizard example is imported automatically to the Keil MDK-ARM project using the CMSIS PACK mechanism.

The following steps are needed to establish this automatic project import:

After the Embedded Wizard code generation the installed post process will generate a ewfiles.gpdsc file, that controls the Keil MDK-ARM project import.

In Keil MDK-ARM a dialog appears: "For the current project new generated code is available for import". After confirmation, the latest generated code and the suitable Embedded Wizard Platform Package will be imported to the Keil MDK-ARM project (depending on the color format and the screen orientation selected in the Embedded Wizard Profile).

If the color format or the screen orientation was changed, please do a complete rebuild of the Keil MDK-ARM project.

In order to bring-up an Embedded Wizard generated UI application on your GD32H759 custom hardware, you can use the provided Embedded Wizard Build Environment for GD32H759 Evalboard as a template. For general information about porting Embedded Wizard to custom hardware, please refer to the article Custom Hardware Integration.

For GD32H759 Evalboard-based custom hardware, the following target-specific adaptations are typically necessary:

The following section contains the version history of the Build Environment (including Graphics Engine and Runtime Environment) for GD32H759 Evalboard. These release notes describe only the platform specific aspects - for all general improvements and enhancements please see the Embedded Wizard release notes.