Jxmcu — Driver

; jxmcu.inf
[Version]
Signature="$WINDOWS NT$"
Class=Ports
ClassGuid=4d36e978-e325-11ce-bfc1-08002be10318
Provider=%ManufacturerName%
DriverVer=01/15/2024,1.0.0.0
[Manufacturer]
%ManufacturerName%=DeviceList, NTamd64
[DeviceList.NTamd64]
%DeviceDesc%=DriverInstall, USB\VID_1234&PID_5678
[DriverInstall]
Include=usbser.inf
Needs=UsbSer
AddReg=DriverInstall.AddReg
[DriverInstall.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider" jxmcu driver
[Strings]
ManufacturerName="Jingxin Microelectronics"
DeviceDesc="JXMCU Virtual COM Port"

Before downloading any driver, you must identify which specific version of JXMCU you own. There are three common variants: ; jxmcu

| Variant | USB Vendor ID (VID) | Typical Driver | Best For | | :--- | :--- | :--- | :--- | | JXMCU-103 | 1A86 | CH340/CH341 | Basic serial flashing (Arduino clones) | | JXMCU-F4 | 0483 | STM32 Virtual COM Port | High-performance debugging (STM32F405 based) | | JXMCU-Link | 2E3C | CMSIS-DAP v2 | Professional debugging + Drag-and-drop programming |

How to check: Plug your board into your PC, open Device Manager (Windows) or lsusb (Linux). Look for an unknown device labeled "JXMCU" or a generic "USB Serial Converter."

Prerequisites:

Procedure:

Verification: Right-click the device → Properties → Driver tab. Version should match the installed one.

Unlike generic STM32 or Atmel chips, JXMCUs often integrate proprietary bootloaders and custom USB Vendor IDs (VID) / Product IDs (PID). The JXMCU driver is specifically designed to handshake with these bootloaders. Generic drivers like usbser.sys (Windows) or cdc_acm (Linux) may detect the device but fail to establish a stable debugging link. Before downloading any driver, you must identify which

For firmware upload/debugging (like ST-Link, J-Link, or CMSIS-DAP):

Users acquiring a JXMCU module often face installation difficulties due to the lack of official documentation in the packaging.