GD32E507V-START
Overview
The GD32E507V-START board is a hardware platform that enables prototyping on GD32E507VE Cortex-M33 High Performance MCU.
The GD32E507VE features a single-core ARM Cortex-M33 MCU which can run up to 180 MHz with flash accesses zero wait states, 512kiB of Flash, 128kiB of SRAM and 80 GPIOs.
Hardware
GD32E507VET6 MCU
1 x User LEDs
1 x User Push buttons
1 x USART (RS-232 at J1 connector)
GD-Link on board programmer
J-Link/SWD connector
For more information about the GD32E507 SoC and GD32E507V-START board:
Supported Features
The gd32e507v_start board supports the hardware features listed below.
- on-chip / on-board
 - Feature integrated in the SoC / present on the board.
 - 2 / 2
 - 
      Number of instances that are enabled / disabled. 
Click on the label to see the first instance of this feature in the board/SoC DTS files. - 
      
vnd,foo - 
      Compatible string for the Devicetree binding matching the feature. 
Click on the link to view the binding documentation. 
gd32e507v_start/gd32e507 target
Type  | 
Location  | 
Description  | 
Compatible  | 
|---|---|---|---|
CPU  | 
on-chip  | 
ARM Cortex-M33 CPU1  | 
|
Clock control  | 
on-chip  | 
Gigadevice RCU - Clock Controller1  | 
|
Counter  | 
on-chip  | 
||
DAC  | 
on-chip  | 
GigaDevice GD32 series DAC module1  | 
|
DMA  | 
on-chip  | 
GD32 DMA controller2  | 
|
Flash controller  | 
on-chip  | 
There are three types GD32 FMC1  | 
|
GPIO & Headers  | 
on-chip  | 
||
I2C  | 
on-chip  | 
GigaDevice GD32 I2C3  | 
|
Input  | 
on-board  | 
Group of GPIO-bound input keys1  | 
|
Interrupt controller  | 
on-chip  | 
ARMv8-M NVIC (Nested Vectored Interrupt Controller)1  | 
|
on-chip  | 
GigaDevice External Interrupt Controller1  | 
||
LED  | 
on-board  | 
Group of GPIO-controlled LEDs1  | 
|
on-board  | 
Group of PWM-controlled LEDs1  | 
||
Multi-Function Device  | 
on-chip  | 
Gigadevice RCU1  | 
|
MMU / MPU  | 
on-chip  | 
ARMv8-M MPU (Memory Protection Unit)1  | 
|
MTD  | 
on-chip  | 
Flash memory binding of GD32 FMC v11  | 
|
Pin control  | 
on-chip  | 
GD32 AFIO1  | 
|
on-chip  | 
GD32 Pin Controller (AFIO Model)1  | 
||
PWM  | 
on-chip  | 
||
Reset controller  | 
on-chip  | 
Gigadevice RCU - Reset Controller1  | 
|
Serial controller  | 
on-chip  | 
||
SRAM  | 
on-chip  | 
Generic on-chip SRAM1  | 
|
Timer  | 
on-chip  | 
ARMv8-M System Tick1  | 
|
Watchdog  | 
on-chip  | 
GD32 free watchdog timer1  | 
|
on-chip  | 
GD32 window watchdog timer1  | 
Serial Port
The GD32E507V-START board has one serial communication port. The default port is USART0 with TX connected at PB6 and RX at PB7. USART0 is exposed as a virtual COM port via the CN3 USB connector.
Programming and Debugging
The gd32e507v_start board supports the runners and associated west commands listed below.
| flash | debug | attach | rtt | debugserver | |
|---|---|---|---|---|---|
| jlink | ✅ | ✅ | ✅ | ✅ | ✅ | 
| pyocd | ✅ (default) | ✅ (default) | ✅ | ✅ | ✅ | 
Before programming your board make sure to configure boot jumpers as follows:
JP3/4: Select 2-3 for both (boot from user memory)
Using GD-Link or J-Link
The board comes with an embedded GD-Link programmer. It can be used with pyOCD provided you install the necessary CMSIS-Pack:
pyocd pack install gd32e507ve
J-Link can also be used to program the board using the SWD interface exposed in the JP1 header.
Build the Zephyr kernel and the Hello World sample application:
west build -b gd32e507v_start samples/hello_world
Run your favorite terminal program to listen for output. On Linux the terminal should be something like
/dev/ttyUSB0. For example:minicom -D /dev/ttyUSB0 -oThe -o option tells minicom not to send the modem initialization string. Connection should be configured as follows:
Speed: 115200
Data: 8 bits
Parity: None
Stop bits: 1
To flash an image:
west build -b gd32e507v_start samples/hello_world west flash
You should see “Hello World! gd32e507v_start” in your terminal.
To debug an image:
west build -b gd32e507v_start samples/hello_world west debug