Probe driver mismatch

The selected probe driver does not match the connected hardware.

PROBE_DRIVER_MISMATCH

Symptoms

  • Connecting fails immediately with a driver mismatch error.
  • The probe enumerates but behaves like a different adapter type.

Likely causes

  • A different probe was plugged in than the one the session was configured for.
  • The probe runs alternative firmware (e.g. an ST-Link reflashed as J-Link, or DAPLink firmware on an on-board probe) so its USB identity no longer matches expectations.

How to fix it

  1. Identify the actual probe

    Check the USB descriptor: lsusb (Linux) or Device Manager (Windows) shows the vendor — 0483 is ST, 1366 is SEGGER, DAPLink appears as a CMSIS-DAP device.

  2. Select the matching probe in MCUHex

    Pick the entry that matches the real hardware from the device list, then reconnect.

  3. If you reflashed the probe firmware

    Probes converted between ST-Link and J-Link firmware keep their new identity — select the type that matches the current firmware, not the sticker on the board.

Related errors