2288 views|2 replies

2

Posts

0

Resources
The OP
 

GD32F103RC burning problem [Copy link]

When burning GD32F103RC, use J-Flash to burn. After burning once with GD32F103RC as the chip model, choose STM32F103RC for decryption, and then burn the program without encryption. After burning, it is found that the program is abnormal. After changing to a new MCU, continue to choose STM32F103RC model to burn without problems. Will there be problems when choosing GD32F103RC to burn for the first time? (The program uses ST library)

This post is from GD32 MCU

Latest reply

I have been using the GD32 burning option and it has been working fine. I also use the gd32 library for programming. [attach]639318[/attach]   Details Published on 2022-9-6 10:23
 

2865

Posts

4

Resources
2
 

I have been using the GD32 burning option and it has been working fine. I also use the gd32 library for programming.

This post is from GD32 MCU
 
 
 

2

Posts

0

Resources
3
 

Solved. When I used J-Flash to burn and encrypt, I selected GD32F103. When I decrypted, I selected STM32F103. This caused the problem when I burned the program again. Solution: Use J-Flash to select the chip model STM32F103 to perform an encryption and decryption operation. There will be no abnormality when burning the program again.

This post is from GD32 MCU
 
 
 

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