Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 7 of 7

Thread: Teensy 3.1 "Unable to Reboot" & "Download Error"

  1. #1
    Junior Member
    Join Date
    May 2016
    Posts
    5

    Teensy 3.1 "Unable to Reboot" & "Download Error"

    Hi All,

    I'm currently having issues programming a teensy 3.1 board through Teensyduino (in windows 7 32 bit). I get the same issue with a number of arduino scripts that I know are bug free.

    Recently the board has taken a while to reprogram (windows doesn't identify the usb device etc. and it takes a bit of playing around - unplugging and plugging the usb before it connects)

    Now I'm getting "Download Error" and "Unable to Reboot" errors in the Teensy window. The Teensy appears to be connected and I have the option of hitting the reboot and program buttons (they're green) in the teensy window.

    I've copied logs for both cases below and hope someone can identify the problem....

    Log when hitting the "Program" Button and getting "Download Error"

    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: HID/win32: waiting for device
    12:29:00: program: write error
    12:29:00: HID/win32: HidD_GetPreparsedData ok, device still online :-)
    12:29:00: end operation
    12:29:00: redraw timer set, image 11 to show for 4000 ms
    12:29:04: redraw, image 10


    Log when hitting the "reboot" button and getting the "Unable to Reboot"


    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: HID/win32: waiting for device
    12:43:55: begin wait_until_offline
    12:43:55: HID/win32: HidD_GetPreparsedData ok, device still online :-)
    12:43:58: offline failed, timeout after 50
    12:43:58: reboot error
    12:43:58: end operation
    12:43:58: redraw timer set, image 13 to show for 4000 ms
    12:44:02: redraw, image 10
    12:44:02: Verbose Info event

    Any help is appreciated with this (its making what should be a fairly simple project a very time consuming one!)

    Thanks in advance

  2. #2
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    22,990
    Something's really wrong with you USB or drivers. Any chance you can compare with another computer? Or try a different port, cable, and eliminate any USB hubs?

    These sorts of errors happen when the communication is getting corrupted, badly. Something is very messed up.

  3. #3
    Junior Member
    Join Date
    May 2016
    Posts
    5
    Thanks for the response. It seems strange. I had the same error with a different computer and about a week later the same Teensy board and computer worked perfectly and I haven't had any issues since.

  4. #4
    Senior Member Epyon's Avatar
    Join Date
    Apr 2013
    Location
    Belgium
    Posts
    443
    I had the same problem here, on different computers and with different cables. Seems to be working okay again now.

  5. #5
    Senior Member
    Join Date
    Jul 2014
    Posts
    2,884
    With T3.2 (i.e. new MKL02 Boot-chip) this types of problems increased. (seems the new chip is faster than the old one)
    As I use windows, I always found it instructive to keep the device manager open and to observe the refresh (which happens when something on USB changes) You will note that the times between refreshes may vary significantly. Unfortunately this is rather random, and we could not convince Paul to investigate the timings during the Boot process.

  6. #6
    Junior Member
    Join Date
    Sep 2017
    Location
    Bath, UK
    Posts
    5
    I'm having the same issue on a 2016 Macbook Pro, Teensy 3.1, Arduino 1.8.3, Teensy 1.37.

    Sometimes the software/hardware will get into a state where it refuses to boot. This persisted across a restart of the computer (!)

    Loading the Blink sketch onto a fresh Teensy (3.2) seems to have made everything happy again; my original Teensy (3.1) works again after this.

  7. #7
    Junior Member
    Join Date
    Mar 2020
    Posts
    1
    Quote Originally Posted by buildsucceeded View Post
    I'm having the same issue on a 2016 Macbook Pro, Teensy 3.1, Arduino 1.8.3, Teensy 1.37.

    Sometimes the software/hardware will get into a state where it refuses to boot. This persisted across a restart of the computer (!)

    Loading the Blink sketch onto a fresh Teensy (3.2) seems to have made everything happy again; my original Teensy (3.1) works again after this.
    I have the same problem but I don't have another Teensy to use. It seems I have to unplug my Teensy 3.2, restart my Mac, restart Teensy, Restart Arduino with Teensy and then SOMETIMES that works. Has there been another solution? It worked for a long time and then did some programming in SERCOMs and it started happening randomly. When it doesn't work, it seems like the TEENSY program doesn't recognize the re-connected TEENSY 3.2 board and pressing the button doesn't initiate a reboot.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •