2533 views|2 replies

7

Posts

0

Resources
The OP
 

[GD32E503 Review] How to Play with GD32E503-Environment Construction [Copy link]

 

After receiving the development board, the first thing we need to do is light up the LED light, then we are done.

The MDK version I am using now is 5.27, which is a very new version. I have previously developed the GD32E103/f103 chip using this version, and it went quite smoothly.

Step 1: Install packs, gd32e503 packs (I think the mdk's automatic installation packs are difficult to install, but fortunately the official provides corresponding packs, which we can install quickly).

Step 2:

The official website provides a lot of sample codes:

Open the sample code 01_GPIO_Running_LED. As soon as the sample code is opened, the following error pops up:

It seems that 5.1.1 can't be used... This problem is a bit embarrassing. I searched the Internet and couldn't find the specific reason. Then I spent an hour or two and still couldn't solve it. Sometimes I often encounter such inexplicable problems. According to experience, this is a problem with the development environment... So, I went to the MDK official website and checked whether there is the latest mdk and updated it~~~ It really let me find the 5.33 version, and then installed it all the way~ After the installation is complete, I directly opened the sample code~, ok, no problem. Although I don't know what the reason is, it was solved after all. Could it be that 5.27 does not support the m33 kernel? Or something else, I won't pursue it here, and those who are interested can go deeper. Let's proceed to the next step.

Step 3: Turn on the program debug and download. The gd32e503v development board integrates an onboard debugger - GDLINK. The following are the settings required when using MDK for debugging (be sure to choose the right programmer).

Furthermore, after compiling, you can click the debug button to write the program into the chip. At this time, another question pops up:

It's very simple, the problem is that flash is not selected. Let's add it in the settings.

Finally, click debug, you can burn and debug smoothly. If you execute at full speed, you will see the LED running lights on the development board.

In summary, I have finally gotten started. Sometimes some problems are always inexplicable, but there must be a solution. Sometimes you can't find it online, so you can think about it again. Sometimes reinstalling the environment is also a good method.

All information can be obtained by contacting me, QQ: 181428254

This post is from Domestic Chip Exchange

Latest reply

Is there a version conflict? It is unlikely that the M33 kernel is not supported. I seem to have encountered this problem before.   Details Published on 2021-1-18 14:54

赞赏

1

查看全部赞赏

 
 

1942

Posts

2

Resources
2
 

Is there a version conflict? It is unlikely that the M33 kernel is not supported. I seem to have encountered this problem before.

This post is from Domestic Chip Exchange

Comments

It's more likely a version conflict. I wanted to just update the compiler version, but after many attempts, all failed. Finally, I had to update EDK, and then it worked.  Details Published on 2021-1-18 23:22
 
 
 

7

Posts

0

Resources
3
 
w494143467 posted on 2021-1-18 14:54 Is there a version conflict? It is unlikely that the M33 kernel is not supported. It seems that this problem has been encountered before.

It's more likely to be a version conflict. I wanted to just update the compiler version, but after many attempts, all failed. Finally, I had to update EDK, and then it worked.

This post is from Domestic Chip Exchange
 
 
 

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