t2-cli: Crash report: Error: No device found in bootloader mode

Error: No device found in bootloader mode
    at t2-cli\lib\usb-connection.js:334:19
    at USB.Connection.exec.USB.Connection._receiveMessages.USB.Connection.open.setAltSetting.then.then.USB.Connection.setAltSetting.USB.Connection.end.USB.Connection.enterBootloader.Promise.then.USB.Connection._waitUntilInBootloader.USB.Connection._findBootedDeviceBySerialNumber (t2-cli\lib\usb-connection.js:318:10)
    at retry [as _onTimeout] (t2-cli\lib\usb-connection.js:295:12)
    at Timer.listOnTimeout (timers.js:92:15)

Full report is at -0x6cf53c42

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 16 (11 by maintainers)

Most upvoted comments

I just encountered this error while testing on a windows 10 machine.

rwaldron on Oct 17, 2016

@rwaldron Yes, prior to using PowerShell, I tried using both cmd.exe, as well as Git Bash.

Update: As you mentioned cmd.exe, I tried all CLI tools that I had previously used - Git Bash, PowerShell and cmd.exe, and I actually got it to update only from cmd.exe.

It worked like a charm, without running cmd.exe as an administrator - below is the output of the t2 update command:

INFO Looking for your Tessel...
INFO Connected to <MY_TESSEL_DEVICE>.
INFO New firmware version found...0.0.16
INFO Updating <MY_TESSEL_DEVICE> to latest version (0.0.16)...
INFO Downloading files...
INFO Download complete!
INFO Updating OpenWRT (1/2)
INFO Transferring image of size 15.47 MB. This will take 2-4 minutes...
INFO Transfer complete.
INFO Starting OpenWRT update.
INFO Please do not remove power from Tessel.
INFO This process will take at least 2 minutes...
INFO Configuration is saved during update.
INFO Updating firmware (2/2)
INFO Firmware update complete!
INFO Updated <MY_TESSEL_DEVICE> from  0.0.13  to  0.0.16

vzamfirescu on Mar 25, 2017

I’m getting the following issue from Windows 10 issue

jdnichollsc on Feb 7, 2017