Target support not installed

pyOCD knows which MCU this is but has no support pack for it installed.

CORTEX_M_UNSUPPORTED_TARGET

Symptoms

  • The target connects but is identified only as generic Cortex-M.
  • Flashing is unavailable or fails with a missing memory map.
  • A newly released MCU variant is not in the target list.

Likely causes

  • pyOCD identifies targets by a database of parts (built-in + CMSIS packs); an unknown part falls back to generic cortex_m — debuggable, but with no flash algorithm or memory map.
  • The exact target was never selected, so auto-detection stopped at the generic fallback.
  • The probe reports the board (Nucleo, Discovery), pyOCD knows the part, but its CMSIS pack is not installed — pyOCD refuses to connect rather than falling back.
  • MCUHex supports SWD-based ARM Cortex-M targets only — JTAG-only parts (e.g. TI C2000) are outside the supported set.

How to fix it

  1. Install the support pack

    When pyOCD names the part but has no pack for it, MCUHex opens the chip picker by itself with that part already selected. Click Install pack, then continue — the connection is retried with the pack in place. From a console the same step is a single command.

    python -m pyocd pack install stm32g070rbtx

  2. Select the exact MCU

    Pick your part number in the Target selector in the MCUHex footer (e.g. STM32G474RETx). This loads the correct memory map and flash algorithm.

  3. Confirm the family is supported

    MCUHex targets SWD-capable ARM Cortex-M devices (ST-Link, J-Link, DAPLink probes). If your part is JTAG-only or non-ARM, it will not work regardless of settings.

  4. Very new parts

    If the part is newer than the target database, the vendor’s CMSIS pack may not be integrated yet — tell us which part you need via the feedback form.

Related errors