APM32F103C8T6 variant not working with DAPLink firmware - only shows as COM4
Hardware
WeAct Studio Mini Debugger with APM32F103C8T6 chip (128KB NVM confirmed in STM32CubeProgrammer)
Problem
After flashing the DAPLink firmware, the device only shows up as a COM port (UART bridge) in Device Manager. The main MCU USB is not enumerating — it shows as "Unknown USB Device (Device Descriptor Request Failed)" briefly and then disappears, leaving only COM4.
Firmwares tried
stm32f103xb_bl_crc.hex + stm32f103xb_if_crc.hex from the Firmwares/DAPLink folder → Unknown USB Device
apm32f103cbt6_rom.hex from Dump/DAPLink → only COM4, no USB device at all
Flashing method
SWD via another STLink using STM32CubeProgrammer, full chip erase before each attempt.
Question
Is there a specific firmware build for the APM32F103C8T6 variant? The STM32 DAPLink firmware does not appear to be compatible with the APM32 chip's USB clock configuration.
APM32F103C8T6 variant not working with DAPLink firmware - only shows as COM4
Hardware
WeAct Studio Mini Debugger with APM32F103C8T6 chip (128KB NVM confirmed in STM32CubeProgrammer)
Problem
After flashing the DAPLink firmware, the device only shows up as a COM port (UART bridge) in Device Manager. The main MCU USB is not enumerating — it shows as "Unknown USB Device (Device Descriptor Request Failed)" briefly and then disappears, leaving only COM4.
Firmwares tried
stm32f103xb_bl_crc.hex+stm32f103xb_if_crc.hexfrom the Firmwares/DAPLink folder → Unknown USB Deviceapm32f103cbt6_rom.hexfrom Dump/DAPLink → only COM4, no USB device at allFlashing method
SWD via another STLink using STM32CubeProgrammer, full chip erase before each attempt.
Question
Is there a specific firmware build for the APM32F103C8T6 variant? The STM32 DAPLink firmware does not appear to be compatible with the APM32 chip's USB clock configuration.