Skip to content

XM10 Extension Module SDK v2.5.1

Release date: 2026-07-29 | Target HW: Rev 2.0 only (Rev 1.1 unaffected) | KIT H10 FW: v2.3.0+

✅ Confirmed (2026-07-30) — v2.5.1 firmware is confirmed working. If the board still seems to hang after you update, the cause may be your debugging environment, not the firmware (breakpoints left over from a previous session, or an outdated ST-LINK firmware). Check the "Debugging caveats" section below first.


At a glance

An urgent fix for Rev 2.0 boards that stopped part-way through boot. No feature changes.

  • Symptom — power the board and the LEDs stay dark, and no COM port (USB serial) shows up on your PC. The firmware is stuck mid-boot.
  • Affected versions — Rev 2.0 firmware of v2.4.1 and v2.5.0. v2.4.0 and earlier are not affected.
  • Rev 1.1 is unaffected — the code that caused this never existed on Rev 1.1. Keep using your current build.
  • What to do — Rev 2.0 users: download Rev2.0.zip, rebuild, and upload.
  • Bootloader (optional) — a newer bootloader build (2026-07-30) with a stability improvement is attached. The existing bootloader keeps working fine, so this is not required — update when convenient.

What happened?

An internal setting made very early in boot was not released in time, so the board could not get past the USB preparation step and stopped there. The USB hardware is not broken. This release makes sure that setting is always released, and adds a second safety net that checks it once more at the very start of boot.


Does this affect my board?

Check Affected?
Board has an RJ45 Ethernet port (= Rev 2.0) + firmware is v2.4.1 or v2.5.0 Yes — update to v2.5.1
Board has no RJ45 port (= Rev 1.1) No — keep using it
Rev 2.0 but firmware is v2.4.0 or earlier No (updating is still recommended)

If your board boots and a COM port appears on your PC, you are not affected.


How to update

  1. Download Rev2.0.zip below and extract it (to a path with no spaces or non-ASCII characters).
  2. Open it in STM32CubeIDE and build.
  3. Upload with PhAI Studio USB upload. The bootloader is already installed — no need to reinstall it.

If the board is already stuck and PhAI Studio cannot connect, flash it once directly over SWD (ST-Link).


Debugging caveats — "I updated and it still looks stuck"

If the board still appears to hang at the same place after updating to v2.5.1, the cause may be your debugging environment rather than the board or the firmware. Try these in order:

  1. Upgrade your ST-LINK firmware — STM32CubeIDE menu Help → ST-LINK Upgrade. An outdated ST-LINK firmware can make perfectly good firmware look as if it has stopped while you debug.
  2. Remove all breakpoints from previous sessions — Run → Remove All Breakpoints.
  3. Still stuck? Unplug every cable, fully power-cycle the board, then connect power only — no debugger. If the LEDs come up and a COM port appears, the firmware is fine. (State left behind by a debugger is only cleared by a full power cycle.)

Downloads

File Target board
Rev2.0.zip XM10 Rev 2.0 (newer board with the RJ45 Ethernet port) — v2.5.1
Rev1.1.zip XM10 Rev 1.1 (early development board) — identical to v2.5.0 (unchanged)

This fix only applies to Rev 2.0, so Rev1.1.zip is the same file as in v2.5.0. Rev 1.1 users can keep the copy they already have.

Release attachments

File Purpose
AGR_Bootloader.bin XM10 bootloader — new build, 2026-07-30 (flash once over SWD; after that, upload firmware via PhAI Studio USB)
SUIT_H10_Binary_20260716.zip KIT H10 (CM · MD · ESP32) firmware — update via USB stick
SUIT_ContentsFiles.zip KIT H10 content files (motions, sounds) — on the same USB stick

The bootloader has been replaced with a newer build (2026-07-30) — it improves boot stability. The previous bootloader keeps working fine, so this is not required — but if you get a chance to flash over SWD, updating to the latest build is recommended. The KIT H10 firmware and content files are unchanged from previous releases — if you have already installed them, there is nothing else to do. See bootloader upload and KIT H10 firmware.


Compatibility

Item Impact
User code (Control_Setup / Control_Loop) No change — just rebuild
APIs (CDC etc.) No change
Examples No change (Rev 2.0: 45, Rev 1.1: 42)
Bootloader Optional update — the existing one keeps working; updating to the latest build (stability improvement) is recommended
KIT H10 firmware / content files Unchanged — no update needed
Rev 1.1 Unaffected