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

Thread: Teensy 3.2 recognized but not uploading

  1. #1

    Teensy 3.2 recognized but not uploading

    Hey all,

    I have a Teensy 3.2 that is showing a strange issue. It has been programmed with "USB type: MIDI" and is running its program fine and when I plug it into my windows 10 computers it shows up as a "Teensy MIDI" in Device manager. Yet when I try to program it, nothing happens. The two tiny chips next to the usb connector are getting quite warm, so I expect it to be a hardware problem, but since the program is still running and the driver seems to load just fine, I would like to rule out a software fix before trashing the board.

    Any help would be much appreciated!

    I have pasted below the info from the Teensy loader verbose info:

    As I plug in the usb cable:
    Code:
    10:09:10.075 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
    10:09:10.076 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0485#2375270#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    10:09:10.076 (ports 5): found_usb_device, loc=usb:0/140000/0/3    Port_#0003.Hub_#0001
    10:09:10.076 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0485&REV_0200
    10:09:10.076 (ports 5): found_usb_device, devinst=00000006
    10:09:10.076 (ports 5): add: loc=usb:0/140000/0/3, class=USB, vid=16C0, pid=0485, ver=0200, serial=2375270, dev=\\?\usb#vid_16c0&pid_0485#2375270#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    10:09:10.076 (ports 5): hiddev_from_devinst_list: iface=1
    10:09:10.077 (ports 5): found_usb_device complete
    10:09:10.078 (ports 5): usb_add: usb:0/140000/0/3  [no_device] (Teensy) MIDI
    10:09:10.161 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:09:10.190 (ports 5): update_usb_device, devinst list change, old had 2, new has 3
    10:09:10.190 (ports 5): hiddev_from_devinst_list: iface=1
    10:09:10.236 (ports 5): usb_add: usb:0/140000/0/3  [no_device] (Teensy) MIDI
    10:09:10.961 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:09:10.962 (ports 5): update_usb_device, devinst list change, old had 3, new has 4
    10:09:10.962 (ports 5): hiddev_from_devinst_list: iface=1
    10:09:10.963 (ports 5):   0000000E: path=\\?\hid#vid_16c0&pid_0485&mi_01#7&156f78&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
    10:09:10.964 (ports 5): hid, found devinst=0000000E
    10:09:10.965 (ports 5): usb_add: usb:0/140000/0/3  hid#vid_16c0&pid_0485 (Teensy) MIDI
    10:09:11.730 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:09:11.730 (ports 5): update_usb_device, devinst list change, old had 4, new has 6
    10:09:11.731 (ports 5): hid, found devinst=0000000E
    10:09:11.732 (ports 5): usb_add: usb:0/140000/0/3  hid#vid_16c0&pid_0485 (Teensy) MIDI
    As I press the program button:
    Code:
    10:10:00.276 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
    10:10:00.316 (ports 5): remove: loc=usb:0/140000/0/3
    10:10:00.316 (ports 5): usb_remove: usb:0/140000/0/3
    10:10:00.316 (ports 5): nothing new, skipping HID & Ports enum
    10:10:00.316 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:10:00.354 (ports 5): nothing new, skipping HID & Ports enum
    10:10:01.068 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:10:01.068 (ports 5): nothing new, skipping HID & Ports enum
    10:10:01.105 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
    10:10:01.106 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0485#2375270#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    10:10:01.106 (ports 5): found_usb_device, loc=usb:0/140000/0/3    Port_#0003.Hub_#0001
    10:10:01.106 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0485&REV_0200
    10:10:01.106 (ports 5): found_usb_device, devinst=00000006
    10:10:01.106 (ports 5): add: loc=usb:0/140000/0/3, class=USB, vid=16C0, pid=0485, ver=0200, serial=2375270, dev=\\?\usb#vid_16c0&pid_0485#2375270#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    10:10:01.106 (ports 5): hiddev_from_devinst_list: iface=1
    10:10:01.107 (ports 5): found_usb_device complete
    10:10:01.108 (ports 5): usb_add: usb:0/140000/0/3  [no_device] (Teensy) MIDI
    10:10:01.819 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:10:01.820 (ports 5): update_usb_device, devinst list change, old had 2, new has 4
    10:10:01.820 (ports 5): hiddev_from_devinst_list: iface=1
    10:10:01.820 (ports 5):   0000000E: path=\\?\hid#vid_16c0&pid_0485&mi_01#7&156f78&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
    10:10:01.821 (ports 5): hid, found devinst=0000000E
    10:10:01.822 (ports 5): usb_add: usb:0/140000/0/3  hid#vid_16c0&pid_0485 (Teensy) MIDI
    10:10:02.573 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    10:10:02.573 (ports 5): update_usb_device, devinst list change, old had 4, new has 6
    10:10:02.574 (ports 5): hid, found devinst=0000000E
    10:10:02.574 (ports 5): usb_add: usb:0/140000/0/3  hid#vid_16c0&pid_0485 (Teensy) MIDI
    Thanks a lot for any input!

  2. #2
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    22,497
    Quote Originally Posted by Somnitec View Post
    The two tiny chips next to the usb connector are getting quite warm
    Oh that's not good.

    It is normal for the voltage regulator nest 3.3 and pin 23 to get warm, if your project consumes extra power from the 3.3V line. But the bootloader chip near pins 1 & 2 should not heat up. There's a chance your board may have been damaged somehow.

    Normally pressing and holding the pushbutton should stop everything from running, and when you release it Teensy is supposed to appear as a HID device that Teensy Loader recognizes. For troubleshooting, keep the tiny Teensy Loader window visible on your screen, and turn off Auto mode, so it doesn't immediately reprogram it but instead shows you whether it detects the hardware.

    If pressing the button no longer stops Teensy from running and make it appear in Teensy Loader, your board may be unable to load any new code.

  3. #3
    I completely unsoldered all of the connections, resoldered the vUSB patch, yet it is still working in exactly the same way. Nothing shows on the teensy loader when pressing the button or plugging in, but the verbose connection shows exactly as above. The teensy itself seems to stop running fine when the button is pressed.

    Since my other teensy boards are running just fine, I might just give up on this one. Thanks for checking it out and the quick reaction!

Posting Permissions

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