Command timed out

The SDK server did not respond to a command in time.

COMMAND_TIMEOUT

Symptoms

  • One operation (flash, read, connect) hangs and eventually times out.
  • The SDK process is still alive but stops answering.
  • Subsequent commands also fail until a restart.

Likely causes

  • A USB transfer wedged inside the SDK — typically after a probe glitch — leaving the worker stuck.
  • The target stopped responding mid-operation and the SDK is blocked waiting for it.
  • The host machine is heavily loaded or went to sleep mid-command.

How to fix it

  1. Retry once

    A single timeout after sleep/resume is often transient — retry the operation first.

  2. Restart the SDK

    If commands keep timing out, restart the SDK process. Replug the probe as well so the OS clears any wedged USB transfer.

  3. Check the target

    If timeouts always happen on the same operation, the target may be the blocker — see the connect timeout guide for connect-under-reset.

Related errors