2685 views|0 replies

174

Posts

1

Resources
The OP
 

[GD32L233C] + 1. Unboxing & Development Environment Setup [Copy link]

This post was last edited by chrisrh on 2022-1-4 17:59

1. Unboxing

I communicated and placed an order on TMALL on the afternoon of December 31, 2021 and applied for the board. It was delivered on the first afternoon of the following year. It was so fast.

The express packaging was very tight. When I first received it, I thought it was like this.

0

Or something like this

As a result, the packaging is a bit unworthy of the price .

Looking at other people's unboxing pictures, they put it in a small bag and tied it with a rubber band to prevent the board from running away. I don't even have the rubber band.

After power on, four LED running lights flash;

2. Soldering pin headers (colorful ones look better)

3.Environment configuration:

Download datasheet and DFP from the event link/official website

GigaDevice GD32L233 trial experience, opening the energy-saving "chip" era! (eeworld.com.cn)

GigaDevice (gd32mcu.com)

Download DFP and install it

Installation

Finish

4. Run the demo program

Open GD32L233C_START_Demo_Suites Projects 01_GPIO_Running_LED and run

Come up and pounce directly on the street...

I found that the compiler version was not good. I used Keil 5.20. It might be that the M23/M33 core is newer and the old compiler is incompatible. I need a version above 5.25 to run and read the core normally.

I checked the official website and found that the GD forum said the development environment:

1. Development environment: KEIL IAR Eclipse, etc.

2. Development tools: J-Link U-Link GD-Link. Tools of other brands have many types and firmware versions, so you need to try them and there is no guarantee that they will work. GD-Link uses CMSIS-DAP mode. If you use Keil, you need version 4.74 or above to support CMSIS-DAP mode.

3. For the M23 core (E23 series) and the M33 core (E5 series), IAR version 7.8 or above, or KEIL version 5.25 or above is required, J-Link version 9 or above, and U-Link version 2 or above.

For RISC-V core (VF series), you need to use an open source environment to load GCC, or use the latest version of IAR, and use GD-Link or I-Jat as the simulation tool.

4. The official website provides common materials such as plug-ins, firmware library routines, development board routines, Datasheet, User Manual, as well as development guides, hardware development guides, common host computers (GD-Link, ISP, DFU, IAP, etc.) and common demos (RTOS, simulated IIC, simulated serial port, virtual serial port, serial port simulated SPI, IAP, etc.). Currently, the routines are all based on the firmware library, and there are no register version routines. The information can be downloaded from the official website.

5. Since most people have used other brands before, there are many transplantation and replacement requirements. Any two independently designed chips, even if they are compatible, cannot be completely consistent. It is recommended to use actual tests as the standard. The official chip library and routines are the most suitable for your own chip. It is recommended that you use GD's library for development.

Share someone else's keil525 version

Link:

链接已隐藏,如需查看请登录或者注册

Extraction code: huag

After updating keil, run again, OK

For the new kernels of the M23/M33 series, it would be much better to note the version requirements of the development tools in readme.txt;

This post is from GD32 MCU
 

Guess Your Favourite
Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京B2-20211791 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号
快速回复 返回顶部 Return list