Adapter Stops Responding
Most cases recover without unplugging anything. Start at the top of the ladder and go down only when a step does not help. Then check Known Situations for a documented cause and fix.
The Recovery Ladder
Section titled “The Recovery Ladder”| Step | How | What it clears |
|---|---|---|
| 1. Reconnect | Mission Control 3: Disconnect, then Connect. PyCosmicSDK: close the Device and open a new one. | A stuck session in the host software |
| 2. Reset the adapter | PyCosmicSDK: device.reboot(into=ResetTarget.RUNTIME), then open the adapter again. | Interface roles left configured, a stuck SPI bulk transfer, a busy I3C engine |
| 3. Replug USB | Unplug the adapter’s USB cable, wait 5 seconds, plug it back in. | An adapter that no longer answers any command, including the reset |
| 4. Power-cycle the target | Set the target voltage to 0 V and back, or switch the target’s own supply off and on. | A target that holds the bus or dropped off it |
import timeimport pycosmicsdkfrom pycosmicsdk import Device, ResetTarget
serial = pycosmicsdk.list_devices()[0].serial_number # pick the adapter
with Device.open(serial=serial) as device: device.reboot(into=ResetTarget.RUNTIME)
# The adapter re-enumerates; wait until it is listed again (typically under 1 s).while not any(d.serial_number == serial for d in pycosmicsdk.list_devices()): time.sleep(0.1)
with Device.open(serial=serial) as device: print(device.info.fw_version)What a reset keeps and what it does not:
- Every interface must be initialized again.
- A reset cannot help an adapter that has stopped decoding commands: the reset command never arrives. Replug USB.
Replug, do not just reset, when:
- Every command times out, or PyCosmicSDK raises
AdapterNotAnsweringErroragain on a new handle. - A program crashed, or was killed, in the middle of a transfer.
- The adapter is listed but no program can open it.
Known Situations
Section titled “Known Situations”| Symptom | Cause | Fix |
|---|---|---|
A flash status (WIP) poll over SPI does not finish | The SPI read clock is above what the wiring supports, so read data can be shifted by one bit | Lower the SPI clock for reads, verify the data, and bound the poll. |
Older firmware has other known problems that later releases fixed, so update to the latest firmware first. To check the firmware version and update it, see Updating Firmware.
Collect Information for Support
Section titled “Collect Information for Support”Send these to [email protected]:
-
Adapter, serial number and firmware version:
python -c "import pycosmicsdk; print([(d.model.name, d.serial_number, d.hw_version, d.fw_version) for d in pycosmicsdk.list_devices()])"On Linux, an empty serial number means the udev rule is missing. See Solving USB Connection Issues on Linux.
-
Host: operating system and version, and whether the adapter is on a hub.
-
Software and version: Mission Control 3 (desktop or mc3.binho.io) or PyCosmicSDK (
python -c "import pycosmicsdk; print(pycosmicsdk.__version__)"). -
Actions taken: the last commands before it stopped, the wiring and the target voltage. In Mission Control 3, export the Transaction Log from the tool.
-
What recovered it: reconnect, reset, replug, or none.
-
On Linux: the kernel log from the moment it stopped:
sudo dmesg | tail -n 50.

