Background: Due to the epidemic this year, chips have skyrocketed in the second half of the year, and the company’s chips are in short supply. The original chips used are those of st and BGI. The price is good, no more than five yuan. Now we get the goods, st The price of the chip has risen by about 30 yuan, which is too much to bear, so the development of domestic chips has been accelerated.
table of Contents
2. The possible root cause of the problem
One, the problem
The j-link debugger option cannot be found when debugging the GD32E23 series chips, but the j-link can be found in the projects of other chips, and it can also be debugged normally. I use keil version 5.25 and j-link version 4.86b. Because the chips debugged before are all arm-m0 or arm-m3 kernels, it is thought that the problem may be related to the m23 kernel used by GD32E23.
2. The possible root cause of the problem
On the SEGGER official website, it is found that the version of j-link supporting GD32E2 series is V6.88
On the official website of keil mdk, it is found that the j-link version supported by the latest software version (2020/12/24 23:22) is 6.86
Therefore, according to the description of these two versions, GD32E2 is not yet able to perform normal debugging, but the relevant information on the official website of MCU shows that you can use j-link with keil for chip debugging. So you can only try to upgrade the keil and j-link drivers separately for testing.
Three, the solution
1. Because the keil upgrade is more complicated, I first tried to upgrade the j-link and use V6.89b to upgrade. The result was that it did not work. It was the previous situation. The method of restarting the computer did not work, so only Can take the road to upgrade keil.
2. Choose to upgrade keil. Because my colleague has a good keil 5.29 installation package, I decided to try to install keil 5.29 first. After the installation was completed, I found that the j-link option appeared, and the problem was temporarily solved. But what is strange is that the j-link version that comes with this version is V6.4, and it can also recognize j-link, which may be a compatibility problem.
Four, possible problems
1、j-link报The connected j-link is defective. proper operation cannot be guaranteed
After updating the j-link driver, the error The connected j-link is defective. proper operation cannot be guaranteed.
After searching for information, it was found that the j-link firmware and j-link driver were not compatible. It can be solved by upgrading j-link firmware or lowering the version of j-link driver. What I use here is to upgrade the j-link firmware to solve the problem.
Before upgrading:
After upgrade
Five, sum it up
GD32E230 has requirements for the development environment, or the problem of unrecognized chip will occur;
1. Keil must be 5.26 or above board
2. The jlink driver must be version 6.88 or above
3. D:\Keil_v5\ARM\Segger\jlinkARM.dll in the keil installation directory must be a 6.88 or higher board
4. jlink must be a board version above V9.0
If these conditions are met, there will be no unrecognizable chip.