Teensy 4.1 does not detect USB

Status
Not open for further replies.
S

saikangwarrior

Member
Dear teensy masters,

I am facing issues trying to upload a the code onto my Teensy 4.1.
However, the uploading fails with the following messages.
"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."


As there is no reset button on 4.1, I tried to test the same code and wire on another teensy of the same model
If I connect the USB to a different Teensy 4.1, the blink example code successfully uploads and the led blinks.
I don't think this is a driver issue or wire connectivity as it works on another device.

For your information, the teensy was previously working fine. This problem only appeared suddenly when I uploading a new code I was working on.
Could my bootloader be corrupted? What should I do?
 
Teensy has Program not Reset? Just one button for Program mode? :: "As there is no reset button on 4.1"

What happens when the Button is pressed ? RED LED near the USB connector go ON? Does the upload happen?

On TeensyLoader "Help / Verbose Info" opens a window of the device interactions that may show something.

Bootloader is a separate MCU chip - it can get destroyed or disconnected or made inoperable - but not corrupted in any normal sense.


Unplug the Teensy and hold the Button while plugging it in and a second after.
Then do an upload of code built with USB Type : Serial for the T_4.1
 
Hi defragster,

My apologies, it's my mistake.
It also seems the vendor I bought it from removed the button from Teensy. That's why I was lost.
I managed to short the pins together to simulate pressing of the button and the upload took place. Thank you for the suggestion.

I think it would be quite risky if I were to always short the pad to go into PROGRAM mode.
I think something disabled the boards ability to go into program mode? Is there a way to make it go into PROGRAM mode automatically again?

In case it helps, The log is as below
174015.256 (post_compile 1) Begin, version=1.52, high-res time
174015.506 (loader) Teensy Loader 1.52, begin program
174015.620 (loader) File firmware.hex. 358486 bytes, 4% used
174015.695 (loader) Listening for remote control on port 3149
174015.695 (loader) initialized, showing main window
174015.729 (loader) remote connection 1468 opened
174015.729 (post_compile 1) Sending command comment Teensyduino 1.52 - WINDOWS (teensy_post_compile)
174015.730 (loader) remote cmd from 1468 comment Teensyduino 1.52 - WINDOWS (teensy_post_compile)
174015.732 (loader) remote cmd from 1468 status
174015.736 (loader) HIDwin32 vid04F3 pid3091 ver0002
174015.736 (loader) HIDwin32 vid04F3 pid3091 ver0002
174015.736 (loader) HIDwin32 vidDEED pidFEED ver0101
174015.737 (loader) remote cmd from 1468 dirCUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41
174015.737 (loader) remote cmd from 1468 filefirmware.hex
174015.737 (post_compile 1) Status 1, 0, 0, 0, 0, 0, CUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41, firmware.hex
174015.737 (post_compile 1) Sending command dirCUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41
174015.737 (post_compile 1) Sending command filefirmware.hex
174015.787 (loader) File firmware.hex. 358486 bytes, 4% used
174015.792 (loader) remote cmd from 1468 status
174015.794 (loader) remote cmd from 1468 autoon
174015.794 (post_compile 1) Status 1, 0, 0, 0, 0, 0, CUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41, firmware.hex
174015.794 (post_compile 1) Sending command autoon
174015.795 (post_compile 1) Disconnect
174015.806 (loader) remote connection 1468 closed
174015.806 (post_compile 2) Running teensy_reboot CUsers.platformiopackagestool-teensyteensy_reboot.exe teensy_reboot.exe -board=TEENSY41
174015.807 (loader) remote connection 1468 opened
174015.840 (reboot 3) Begin, version=1.52, high-res time
174015.840 (reboot 3) LoadLibrary cfgmgr32 ok
174015.840 (reboot 3) LoadLibrary ntdll ok
174015.842 (reboot 3) found_usb_device, id=usb#vid_16c0&pid_0483#9145780#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
174015.842 (reboot 3) found_usb_device, loc=usb014000003 Port_#0003.Hub_#0001
174015.842 (reboot 3) found_usb_device, hwid=USBVID_16C0&PID_0483&REV_0280
174015.842 (reboot 3) found_usb_device, devinst=00000004
174015.842 (reboot 3) add loc=usb014000003, class=Ports, vid=16C0, pid=0483, ver=0280, serial=9145780, dev=usb#vid_16c0&pid_0483#9145780#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
174015.842 (reboot 3) comport_from_devinst_list attempt
174015.842 (reboot 3) found Ports in classguid_list at index=0
174015.842 (reboot 3) port COM29 found from devnode
174015.842 (reboot 3) found_usb_device complete
174015.848 (loader) remote connection 1476 opened
174015.848 (loader) remote cmd from 1476 showarduino_attempt_reboot
174015.848 (loader) got request to show arduino rebooting message
174015.849 (reboot 3) found Teensy Loader, version 1.52
174015.849 (reboot 3) Sending command showarduino_attempt_reboot
174015.850 (loader) remote cmd from 1476 comment Teensyduino 1.52 - WINDOWS (teensy_reboot)
174015.850 (loader) remote cmd from 1476 status
174015.851 (reboot 3) Sending command comment Teensyduino 1.52 - WINDOWS (teensy_reboot)
174015.852 (reboot 3) Status 1, 1, 0, 0, 0, 0, CUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41, firmware.hex
174015.852 (reboot 3) do_reset (serial) COM29
174019.401 (loader) Verbose Info event
174345.855 (loader) remote cmd from 1476 status
174345.861 (reboot 3) Status 1, 1, 0, 0, 0, 0, CUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41, firmware.hex
174345.861 (reboot 3) status read, retry 0
174345.961 (loader) remote cmd from 1476 status
174345.966 (reboot 3) Status 1, 1, 0, 0, 0, 0, CUsersDocumentsmanualsCopperhillTeensyCANTeensyLCD-CANFD.piobuildteensy41, firmware.hex
174345.966 (reboot 3) status read, retry 1

.....(retries 50 times)

174351.148 (reboot 3) Teensy did not respond to a USB-based request to automatically reboot.
174351.170 (loader) remote connection 1476 closed
174351.174 (loader) remote connection 1468 closed
Click to expand...
 
Can you please post a photo??

After that, send it back. ALL teensies have a button.
Where did you buy it?
 
Looks like you're using an old version of the software. 1.54 is the latest.

https://www.pjrc.com/teensy/td_download.html

Updating may or may not make any difference. 1.54 did fix some obscure bugs which could cause a board to not boot up, or to stop responding for 1.7 seconds. These problems were not common (the reason they escaped notice on earlier versions) but when they do happen, they can cause hardware to appear to be not work. Update to 1.54 so you can be sure you're not experiencing these software problems.


I also want to know which vendor sold a board without the pushbutton!
 
Hi Frank and Paul,

Thank you for your help.
Surprisingly, after the reprogram, the issue seem to be dormant for now
Will upgrade to 1.54 to see if it will happen again.

Bought it from Copperhill, it's used as part of a CAN module.
index.jpg
 
Indeed - the Button is gone :(

Glad that helped ... should have mentioned TeensyDuino version 1.54 - but at 2AM here was time to go offline ...

Yes a running sketch with active 'Serial' can put the Teensy into bootloader mode - like the Program button would:
Code: 
	while ( Serial.available() ) {
		char cc = Serial.read();
		if ( 'b' == cc ) {
			Serial.print( "Bootloader !!!\n" );
			delay(10);
			asm("bkpt #251");
		}
	}

Or you can add a Button between the pins of " GND and Program " by the SD socket.
 
Last edited:
I think with my skills, it will be very difficult to add a new button with destorying other parts of the circuit. *oops*
That's a very suitable solution. Thank you for Frank B
 
I think the program button on the Teensy 4.1 from Copperhill is unintentionally missing.
The pictures on Copperhill's product page show the button.

Teensy_4.1_Triple_CAN_Board_with_240x240_IPS_LCD_2__13108.1590765555.500.750.jpg

Paul
 
I see. Then it might have been dislodged during shipping. I guess i will email them to check if I ever buy the module again. Would like to avoid the trouble in future modules
 
Status
Not open for further replies.
Back
Top