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

Thread: T4.0 stopped uploading code

  1. #1
    Junior Member
    Join Date
    Apr 2021
    Posts
    3

    T4.0 stopped uploading code

    Howdy forum,

    I'm using T4.0 with StepStick DRV8825 stepper drivers for a while without issue. All of the sudden, I am unable to program my T4.0. I get the following fault:

    Teensy did not respond to a USB-based request to enter program mode.
    Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.
    Interestingly, the T4.0 shows up in Device Manager on the expected port, and runs the last program as expected (minus being able to interface with the serial COM). This is the second T4.0 that this has happened to!

    I have verified that the rest of the cable/tool are fine by programming an alternative T4.1 without issue. I can see 3.3V on the power pin as expected (although I haven't scoped it).

    Any thoughts on what I can do to debug/recover these would be much appreciated!

    Thanks,
    Jim

  2. #2
    Senior Member
    Join Date
    Jul 2014
    Posts
    3,150
    Did pressing the program mode button help?
    Is there another connection to Teensy running as zombie and locking USB port?

  3. #3
    Junior Member
    Join Date
    Apr 2021
    Posts
    6
    I also am having this issue with a brand new 4.0 ive never used.

    Im trying to do the initial upload but the teensyduino loader refuses to see and use the device.

    in device manager I see 2 HID devices VID16c0 PID 0486 MI_00 and MI_01

    and after pressing the button the built in blink sketch stops and I only see the device once as VID 1fc9 PID 0135

    I assume this is expected on the device end since its not configured for showing as a normal serial port out of box (again brand new never used and just soldiered to a also brand new prop shield) doing the 15 second reset it does the same thing still.

    maybe its an issue with a newer build of windows?

  4. #4
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,907
    Running the newest version of Windows for last years as it has evolved and never any trouble with Windows 10. In fact this machine is on the not yet released 2021 Half One release on the Dev channel.

    For a NEW Teensy the process is to open IDE to a simple BLINK sketch - perhaps add something like this to the start of setup() to see printing confirmation on Serial Connect:
    Code:
    void setup() {
    	while (!Serial) ; // wait
    	Serial.println("\n" __FILE__ " " __DATE__ " " __TIME__);
      // ...
    }
    Then with USB:Serial set in Tools with Teensy 4.0 selected - do a Verify build and when it completes you will see an active Teensy Loader window.
    Now Press the Program Button on the Teensy

    Confirm the Tools / Port selection has the Teensy HID device selected, so when SerMon is activated it will open to the right device

    This should put the Loader into action for Programming.

    Open SerMon - if it doesn't open - check the 'Tools / Port selection' again for a change and presence of the T_4.0 online.

    If not Try another high quality USB cable. The T_4.0 runs at 480 Mbps speed and can be more demanding than a prior 12 Mbps Teensy.

  5. #5
    Junior Member
    Join Date
    Apr 2021
    Posts
    6
    Its communicating its just not trying at all to upload the sketch. I have 4.0 selected, the HID port, USB type : serial, loading the "HelloSerialMonitor" example.

    the teensy loader Verbose mode log even detects it upon disconnect reconnect:

    Code:
    02:05:53.724 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
    02:05:53.725 (ports 5): found_usb_device, id=\\?\usb#vid_16c0&pid_0486#6216520#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    02:05:53.725 (ports 5): found_usb_device, loc=usb:10003/0/0/5/1    Port_#0001.Hub_#0004
    02:05:53.725 (ports 5): found_usb_device, hwid=USB\VID_16C0&PID_0486&REV_0279
    02:05:53.725 (ports 5): found_usb_device, devinst=00000005
    02:05:53.725 (ports 5): add: loc=usb:10003/0/0/5/1, class=USB, vid=16C0, pid=0486, ver=0279, serial=6216520, dev=\\?\usb#vid_16c0&pid_0486#6216520#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    02:05:53.725 (ports 5): hiddev_from_devinst_list: iface=1
    02:05:53.725 (ports 5): found_usb_device complete
    02:05:53.726 (ports 5): usb_add: usb:10003/0/0/5/1  [no_device] (Teensy 4.0) RawHID
    02:05:53.741 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    02:05:53.742 (ports 5): update_usb_device, devinst list change, old had 1, new has 3
    02:05:53.742 (ports 5): hiddev_from_devinst_list: iface=1
    02:05:53.743 (ports 5): usb_add: usb:10003/0/0/5/1  [no_device] (Teensy 4.0) RawHID
    02:05:53.779 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    02:05:53.780 (ports 5): update_usb_device, devinst list change, old had 3, new has 5
    02:05:53.780 (ports 5): hiddev_from_devinst_list: iface=1
    02:05:53.780 (ports 5):   00000019: path=\\?\hid#vid_16c0&pid_0486&mi_01#8&ef4b83c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
    02:05:53.780 (ports 5): hid, found devinst=00000019
    02:05:53.780 (ports 5): hid, found devinst=00000018
    02:05:53.780 (ports 5): usb_add: usb:10003/0/0/5/1  hid#vid_16c0&pid_0486 (Teensy 4.0) RawHID
    and on button press:

    Code:
    02:10:52.078 (ports 5): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
    02:10:52.079 (ports 5): remove: loc=usb:10003/0/0/5/1
    02:10:52.079 (ports 5): usb_remove: usb:10003/0/0/5/1
    02:10:52.079 (ports 5): nothing new, skipping HID & Ports enum
    02:10:52.101 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    02:10:52.101 (ports 5): nothing new, skipping HID & Ports enum
    02:10:52.266 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    02:10:52.267 (ports 5): nothing new, skipping HID & Ports enum
    02:10:52.280 (ports 5): WM_DEVICECHANGE DBT_DEVICEARRIVAL
    02:10:52.281 (ports 5): nothing new, skipping HID & Ports enum
    02:10:52.301 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    02:10:52.301 (ports 5): nothing new, skipping HID & Ports enum
    02:10:52.322 (ports 5): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    02:10:52.322 (ports 5): nothing new, skipping HID & Ports enum
    02:10:53.756 (ports 5): purge, name=hid#vid_16c0&pid_0486 (Teensy 4.0) RawHID, loc=usb:10003/0/0/5/1, age=1.677 sec
    running Windows 21343, arduino 1.8.13, Teensyduino 1.53

    tried different cables that work with other devices (which shouldnt even be an issue since again it IS BEING detected just not being written to) even tried on my laptop (same newest build of windows though)

  6. #6
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,078
    Have you tried the 15 second button press to fully wipe the flash memory?

  7. #7
    Junior Member
    Join Date
    Apr 2021
    Posts
    6
    yes it does the quick red blink and then it sits there until I remove and repower it, then its back to the steady blink its done from the start. I ordered this 4.0 august 21st 2019 (loader says serial=6216520) but its just been in its sealed delivery box until yesterday. has there been any updates to the loader or something that may not work with an old unit? I just tried an older 3.2 and its working and uploading fine with all the same setup making this even weirder.

  8. #8
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,907
    Quote Originally Posted by CatCommando View Post
    yes it does the quick red blink and then it sits there until I remove and repower it, then its back to the steady blink its done from the start. I ordered this 4.0 august 21st 2019 (loader says serial=6216520) but its just been in its sealed delivery box until yesterday. has there been any updates to the loader or something that may not work with an old unit? I just tried an older 3.2 and its working and uploading fine with all the same setup making this even weirder.
    When you say 'removed power'?
    > That should not be needed, and if the RED LED was in the 'sits there' state and power was removed the Restore was not yet complete - possibly just the failure to fully blank the remainder of the flash?

    Holding the 15 seconds gives the blink to release the button.
    On releasing the button the RED LED goes bright on until the Restore is fully complete
    Then the Teensy will restart to the BLINK LED after the RED LED goes out.

    At that time with no repower interruption needed the Teensy should preset the HID interface to the PC while blinking.

    Perhaps the 15 sec Restore process needs to be performed again to completion without power interruption.

  9. #9
    Senior Member
    Join Date
    Jul 2014
    Posts
    3,150
    @defragster, he said
    I ordered this 4.0 august 21st 2019 (loader says serial=6216520) but its just been in its sealed delivery box until yesterday.
    not sure if the wipe+reload test is already implemented last summer?

  10. #10
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,907
    Yes, the beta included testing of the 15 second restore.

    Once the Teensy is packed by PJRC the Restore Blink sketch is FROZEN in a no re-write block - so that had to be perfected before production. That code was completed and the 15s Restore was ready - same as on the T_3.5 and 3.6 when it shipped

  11. #11
    Junior Member
    Join Date
    Apr 2021
    Posts
    3
    Quote Originally Posted by WMXZ View Post
    Did pressing the program mode button help?
    Is there another connection to Teensy running as zombie and locking USB port?
    It's un-responsive to program mode button during any attempts to upload. No obvious other Teensy connections, to verify, I've tried re-starting the PC and immediately gone to attempt to upload code, and have also uninstalled device in Device Manager. Just tried another T4.0 that I can upload to without issue.

    Jim

  12. #12
    Junior Member
    Join Date
    Apr 2021
    Posts
    3
    Quote Originally Posted by PaulStoffregen View Post
    Have you tried the 15 second button press to fully wipe the flash memory?
    Hi Paul,

    Yes, I tried the 15 second wipe on both un-responsive devices without luck. Confirmed I was able to do this on a responsive T4.0.

    Jim

  13. #13
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    3,697
    rule out a PC issue, try another PC

  14. #14
    Junior Member
    Join Date
    Apr 2021
    Posts
    6
    >When you say 'removed power'?
    That should not be needed, and if the RED LED was in the 'sits there' state and power was removed the Restore was not yet complete - possibly just the failure to fully blank the remainder of the flash?

    Holding the 15 seconds gives the blink to release the button.
    On releasing the button the RED LED goes bright on until the Restore is fully complete
    Then the Teensy will restart to the BLINK LED after the RED LED goes out.

    My T4 doesnt seem to behave like that. on power on it starts the built in blink sketch, upon holding the reset it does a brief red flash on the second LED next to the usb and then nothing at all. the other led does not come on and it stays in this state until the power is removed (which is why I thought it had to be done)

    here is a short video of it doing what I describe.



    it does the same thing on my laptop with the same build of windows and also under Ubuntu. this teensy has never been used and until I added the prop shield yesterday has been in its anti static sleeve and USPS box since I purchased it.

    its clearly still functional as it shows in device manager both as its usual VID/PID and then as the different one when trying to be programmed. the teensy loader is communicating and can read the serial number. the same cable and 2 computers(both newest arduino/teensyduino) can program a T3 fine as well.

    Im at a loss on what to do now.

  15. #15
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    24,078
    Quote Originally Posted by JSch View Post
    Yes, I tried the 15 second wipe on both un-responsive devices without luck. Confirmed I was able to do this on a responsive T4.0.
    Sounds like a defective or damaged board. I asked Robin to contact you directly. If you can, please try to find the 6 digit order number from your purchase.

  16. #16
    Junior Member
    Join Date
    Apr 2021
    Posts
    6
    wow that would be awesome. guess I should have tested it back then instead of saved it for a good project. its been effectively time capsuled during corona times so the info was still with it. Order 356127

    if this helps Click image for larger version. 

Name:	t4order.jpg 
Views:	9 
Size:	120.1 KB 
ID:	24304

  17. #17
    Junior Member
    Join Date
    Apr 2021
    Posts
    6
    woops thought the last part was to me.. my bad

Posting Permissions

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