Repository navigation
Jibo DFU Toolkit 1.0.5
1.0.5 is the recommended current release. This update improves USB timeout handling with clear diagnostics, incomplete-file cleanup and guided restarts.
What's new
- Clear USB timeout details. An unanswered read reports a USB-link timeout, including its block, queue depth and block size, and removes the incomplete file.
- Guided restart after a timeout. The toolkit explains how to shut Jibo down, re-enter RCM, choose Enter DFU with ShofEL, and start the same operation again. It does not retry in an unusable DFU session.
- One-request-at-a-time follow-up read. The next read of the affected partition or skills chunk queues one request at a time, once. A second timeout stops the operation rather than starting a retry loop. Var reads show the recovery instructions without scheduling a slower read.
- Explicit readback status. A restore/update readback timeout clearly says the write is not verified and directs you to restart the same reviewed operation.
Downloads
- Windows x64 — WSL 2 + WSLg + usbipd-win.
- Linux x86_64 — glibc 2.35+ / Ubuntu 22.04+.
- macOS Apple silicon — macOS 15+; Apple-silicon USB remains experimental.
- macOS Intel — macOS 15+.
These downloads are unsigned; Mac apps are not notarized. SHA256SUMS, license notices, original build receipts and matching corresponding sources are included in the release assets.
Backup and calibration safety
Keep a complete, verified backup from the same Jibo before writing. Choose Keep this Jibo's calibration (recommended). Flash without calibration (unsafe) uses generic settings: camera, motion, hearing and setup may not work properly. Never substitute another robot's backup or calibration.
Keep USB connected until the operation finishes, and keep your logs and backups. After an interrupted write, use the normal reviewed recovery flow and a verified same-robot backup. Installing this host toolkit does not undo writes to a robot or reset/delete WSL Linux. This is a toolkit update, not a robot firmware release.
Validation
Native Windows source checks and the existing Linux/macOS build checks passed. Physical Windows 11 + WSL + usbipd full backups, real-device flash/restore/readback and the benefit of slower reads have not been validated for this release; the original USB timeout's hardware cause is not established. Automated USB fixtures do not replace those hardware checks.
Corresponding source and build provenance
- Linux / Windows payload corresponding source
- macOS Apple-silicon corresponding source
- macOS Intel corresponding source
The original reviewed binaries and matching sources were built from 2bc1694e8a1b76ab39709e12a6d80e534bd204ba. The release tag points to reviewed main at 2afc92a4b9f0bea5a52015f831d96619b3abd6ca, including the accepted three-file fixture/test-only repair; no product or packaging code changed between those revisions.
The original Windows build run had two failing USB test phases. After the test-fixture repair, the complete original native Windows source recipe passed all 49 phases. That is source-test acceptance, not a new binary build: these are the unchanged original downloads and build receipts. GitHub's automatic Source code archives show the release tag; use the corresponding-source assets above for the exact shipped build and its dependencies.