APM32F407 TINY BOARD - Geehy Link On-Board problems

Dev-1997

Hi,

I’m trying to program and debug APM32F407 TINY on Eclipse IDE, using GEEHY-LINK on-board, but when I try to debug, I get the following message:
Open On-Chip Debugger 0.12.0-rc2+dev-00019-g9d925776b-dirty (2022-11-22-17:13)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport “swd”. To override use ‘transport select <transport>’.
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: unable to find a matching CMSIS-DAP device

I’ve already added the arm gnu toolchain, xpack build tools and open ocd bin folder inside PATH (environmental variables), and I added the same directories inside Eclipse IDE. The device manager recognize the board as a CMSIS-DAP device through USB port, and I could build an example project. I’ve already added the SVD path and I typed the following command in OpenOCD config: -f interface/cmsis-dap.cfg -f target/apm32f4x.cfg.
Could you please help me understand how to solve the problem?

Dev-1997

Dev-1997 It’s important to emphasize I could program and debug the target board using external Geehy-Link, so the problem is the Geehy-Link on-board.

Geehy

Dev-1997 hi, regarding the issue you are experiencing with the on-board Geehy-Link, we recommend using the Zadig to change the driver for the “Geehy Link WinUSB Interface 2”, as shown in the attached image. The image illustrates that the “unrecognized device” issue present before the modification can be successfully resolved after updating the driver.

1. OpenOCD Error - Unable to recognize CMSIS-DAP device

2. Replacing the device driver using the Zadig tool

3. PyOCD recognition status comparison before and after driver replacement

4. OpenOCD successfully connected and recognized the debug interface

Additionally, for debugging in the Eclipse GCC environment, we suggest obtaining the OpenOCD version that supports the APM32F407 from the Geehy Community. Alternatively, you can use PyOCD to parse the official Geehy PACK for debugging.

Please let us know if you need any further assistance.

Dev-1997

Even doing the driver replacement, the Geehy-Link on-board debugger didn’t work. See it below:

I’ve downloaded OpenOCD and the xPack build tools from Geehy’s GitHub, and the GNU compiler from a link provided here in the Geehy Community. I verified that the .cfg file is included in the OpenOCD folder, and it is present. However, the issue persists. Do you have any other recommendations?

Yang Chao

Dev-1997 Hi, if the on-board Geehy Link does not emulate as a CMSIS-DAP WinUSB device, it is possible that the current driver is based on HID protocol and not support CMSIS-DAP V2 features. In this case, please refer to the Chapter 3.6 of the application note AN1093 from Geehy’s document center.
https://global.geehy.com/uploads/tool/AN1093_APM32_Eclipse%20Development%20Tutorial%20under%20APM32%20Arm%20MCU%20Windows%20System.pdf

Dev-1997

I’ve tried the procedure in Chapter 3.6 of the app note AN1093, but the error of not recognizing the Geehy Link on-board persists. Do you have any workarounds to solve the issue?

Geehy

Dev-1997

Since our previous attempts to reset the USB driver were unsuccessful, I would like to help you upgrade the firmware of the onboard Geehy Link as a next step.

You mentioned earlier that you have a fully functioning standalone Geehy Link Debugger. I highly recommend using it to connect directly to the onboard Geehy Link’s own SWD interface (please ensure it is connected to this specific interface, rather than the simulated SWD lines connected to the main MCU).

By doing this, you will be able to unlock and access the APM32F103CBT6 chip and flash its firmware to a newer version that supports CMSIS-DAP V2. You can refer to the instructions and the necessary program files provided in the link below to flash the firmware yourself:
https://www.geehy.com/uploads/tool/GEEHY-LINK%20Upgraded%20%20Guide%20V1.0.zip

For some context, based on the screenshot you provided, the key difference between your software version and the one our engineers use is the absence of “WinUSB”. If the firmware is flashed successfully, you will be able to use an upgraded version of the onboard Geehy Link that includes this feature.

However, if this process still does not work, physically disconnecting this daughterboard might be the smartest decision moving forward.

Dev-1997

Ok I can try the procedure, but could you please send the files for APM32F407IG?
You have sent the apm32f10x files:

Yang Chao

Dev-1997 Hi, the apm32f10x firmware is targeting the MCU on the Geehy Link part of the board, which is currently using APM32F103CBT6. With this chip using CMSIS-DAP V2 firmware, and enum to the computer under WinUSB, I believe this driver copes with GNU ecosystem better.