AN154 GD32VW553 Quick Development Guide Table of Contents Table of Contents ......................2 List of Figures ........................ 4 List of Tables ........................5 Introduction to development board ..............6 1.1. Picture of real development board ................6 1.1.1. The START development board ..................... 6 1.1.2.
Page 3
AN154 GD32VW553 Quick Development Guide 5.3. Code running in SRAM ....................28 Revision history ....................29...
AN154 GD32VW553 Quick Development Guide List of Figures Figure 1-1. The picture of the START development board ..............6 Figure 1-2. The picture of the START development board ..............7 Figure 1-3. List of devices and drivers ...................... 9 Figure 1-4. Configuration of serial port ..................... 9 Figure 2-1.
AN154 GD32VW553 Quick Development Guide List of Tables Table 1-1. Boot mode ........................... 8 Table 6-1. Revision history ........................ 29...
AN154 GD32VW553 Quick Development Guide Introduction to development board Picture of real development board 1.1. The START development board 1.1.1. The START development board consists of a baseboard and a module equipped with the GD32VW55x Wi-Fi+BLE chip. Figure 1-1. The picture of the START development board Developers mainly focus on the following parts of the development board, which have been marked in the figure.
AN154 GD32VW553 Quick Development Guide Figure 1-2. The picture of the EVAL development board Developers mainly focus on the following parts of the development board, which have been marked in the figure. Boot mode (Boot PIN); Power supply port (power supply);...
AN154 GD32VW553 Quick Development Guide Figure 1-3. Development Board Type Configuration Boot mode 1.2. GD32VW55x can boot from ROM, FLASH, or SRAM. The level selection of the two pins BOOT0 and BOOT1 in the BOOT SWD box of the development board determines the boot mode. See Table 1-1.
AN154 GD32VW553 Quick Development Guide Download interface 1.4. For START development board, in addition to the firmware download through the debugger mentioned in the previous section, if debugging is not required and only the firmware needs to be downloaded, it can also be downloaded by dragging it into the USB disk. Connect the development board to the computer through a USB cable, and the DAPLINK disk as shown Figure 1-4.
AN154 GD32VW553 Quick Development Guide Building development environment Build a development environment before compiling and burning the firmware. The development tool currently used is GD32Eclipse IDE. Installation of GD32Eclipse IDE 2.1. Unzip GD32EclipseIDE_v1.0.7.17420.7z. Check the toolkit, whose content is as shown in Figure 2-1.
AN154 GD32VW553 Quick Development Guide What developers must know Before getting started with development, first understand the members of the SDK execution program group, how to correctly configure the SDK. SDK execution program group 3.1. SDK will finally generate two main execution programs: MBL (Main Bootloader) and MSDK (Main SDK), which will eventually be burned to FLASH to run.
AN154 GD32VW553 Quick Development Guide SRAM layout 3.2.2. The configuration file is GD32VW55x_RELEASE\config\config_gdm32.h. Modify the following macro definition values to plan the SRAM space occupied by the executable program segments MBL and IMG. These values are offset addresses, and the base address is defined at the beginning of the file.
AN154 GD32VW553 Quick Development Guide macro definition values to specify the version No. However, only RE_IMG_VERSION affects future user upgrades. MBL only supports local upgrade, while IMG supports online upgrade. The version No. released by the SDK is consistent with RE_IMG_VERSION.
AN154 GD32VW553 Quick Development Guide GD32Eclipse IDE project This chapter introduces how to compile and debug the SDK under GD32Eclipse IDE. The project group consists of two projects: MBL/MSDK. MSDK includes Wi-Fi protocol stack, BLE protocol stack, peripheral drivers, applications, etc. MBL is mainly responsible for selecting the correct firmware to run from two MSDK firmware (one is the current firmware and the other is the upgraded one) to run.
AN154 GD32VW553 Quick Development Guide In the File menu, click Open Projects from file System, as shown in Figure 4-3. Open Projects from file System. Figure 4-3. Open Projects from file System Select the project path GD32VW55x_RELEASE\MBL\project\eclipse, as shown in Figure 4-4.
AN154 GD32VW553 Quick Development Guide Close the welcome interface, and the MBL project is shown in Figure 4-5. MBL project interface. Figure 4-5. MBL project interface Import the MSDK project In the File menu, click Open Projects from file System, as shown in Figure 4-3.
AN154 GD32VW553 Quick Development Guide View the MSDK and MBL project interfaces, as shown in Figure 4-7. MSDK and MBL project interfaces. Figure 4-7. MSDK and MBL project interfaces Compilation 4.2. Check the configuration of the project compilation tool Right-click the project, and click Properties, as shown in Figure 4-8.
AN154 GD32VW553 Quick Development Guide Figure 4-8. Opening Properties of the project Select C/C++ BuildSettings, and click the Toolchain Settings tab, as shown in Figure 4-9. Toolchain Settings. The default path is the tools in the IDE directory and does not need to be changed. Click Apply...
AN154 GD32VW553 Quick Development Guide Figure 4-9. Toolchain Settings Compile the MBL project Right-click the project, and click Build Project, as shown in Figure 4-10. Compiling the MBL project.
AN154 GD32VW553 Quick Development Guide Figure 4-10. Compiling the MBL project The compilation result is as shown in Figure 4-11. MBL compilation result.
AN154 GD32VW553 Quick Development Guide Figure 4-11. MBL compilation result Compile the MSDK project Right-click the project, and click Build Configurations—>Set Active—><target project> in order. as shown in Figure 4-12. target project selection, the default target project is msdk.
AN154 GD32VW553 Quick Development Guide Figure 4-13. Compiling the MSDK project The compilation result is as shown in Figure 4-14. MSDK compilation result. Figure 4-14. MSDK compilation result Images generated by SDK After MSDK compilation completed, images output GD32VW55x_RELEASE\scripts\images path, as shown in Figure 4-15.
AN154 GD32VW553 Quick Development Guide used for production and burned into blank FLASH. Figure 4-15. Images output Download 4.3. Refer to 1.4 Download interface, drag and drop image-all.bin to burn. Debugging 4.4. Debugging configuration First select the MSDK project, and then click Debug Configuration in the debug drop-down list, as shown in Figure 4-16.
AN154 GD32VW553 Quick Development Guide Figure 4-17. MSDK debug configuration Start debugging Click the target MSDK in the debug drop-down list to start debugging. Figure 4-18. Starting MSDK debug After the debug session is established, click Debug > Thread under the Browse tab to start debugging, as shown in Figure 4-19.
AN154 GD32VW553 Quick Development Guide DAPLINK disk recognition 5.1. When the START development board is used, if the serial port in the Device Manager cannot be recognized as "mbedSerialPort (COMx)", such as Windows 7 and below, the Mbed serial port driver needs to be installed.
AN154 GD32VW553 Quick Development Guide No image error 5.2. Print ERR: No image to boot (ret = -5). Reason: An error occurs during the previous boot of WIFI_IOT, and the MBL records operation exception of the IMAGE. If another IMAGE is not burned or also has a boot exception, this message will be printed.
Page 29
AN154 GD32VW553 Quick Development Guide Revision history Table 6-1. Revision history Revision No. Description Date Initial release Dec.5, 2023...
Page 30
Important Notice This document is the property of GigaDevice Semiconductor Inc. and its subsidiaries (the "Company"). This document, including any product of the Company described in this document (the “Product”), is owned by the Company under the intellectual property laws and treaties of the People’s Republic of China and other jurisdictions worldwide.
Need help?
Do you have a question about the GD32VW553 and is the answer not in the manual?
Questions and answers