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

Thread: Teensy 4.1 not detected on Windows 10

  1. #1
    Junior Member
    Join Date
    Feb 2021
    Posts
    16

    Teensy 4.1 not detected on Windows 10

    My PC does not recognize my newly purchased Teensy 4.1.
    It recognizes my Arduino thru the same USB port, but not my Teensy.
    I have also tried connecting the Teensy to different USB ports. Same result.

    When I plug in the USB cable, the light on the Teensy 4.1 blinks. So it is getting power. I have tried 3 different USB cables and got the same outcome of the Teensy receiving power, but not being recognized.
    When I push the tiny button on the Teensy, the blinking orangish-red light stops blinking. And the little tiny red-red light right next to the USB port on the Teensy comes on.
    So, it is doing something. But my PC can't recognize it for some reason.

    When I go to Tools > Port on the Arduino IDE, Port is grayed out. I can't pick a port.
    The TinyLoader does not recognize the board either.

    I have tried the gimmick of unplugging the USB cable, and keeping the button on the Teensy pressed while plugging it back into the PC. That did not work either.
    Any ideas or recommendations will be much appreciated.

  2. #2
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany
    Posts
    8,225
    Please reboot the PC, choose Teensy 4.2 from the menu , load the blink example and try to upload it it.
    If that does not work, klick on "Help" from the loader menu and post the verbose info that will be displayed (copy & paste the contents, please no schreenshot.)
    That will help, maybe.

    Maybe try a 4th cable. We had several useres here who had to try all their cables...

  3. #3
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    Thanks Frank, but I don't see Teensy 4.2 as an option. Are you referring to the menu chain in Arduino IDE, Tools > Board > Teensyduino > Teensy 4.1?

  4. #4
    Senior Member
    Join Date
    Apr 2014
    Location
    Germany
    Posts
    1,424
    Isn't this normal? New Teensies come as HID devices, they don't have serial enabled by default. If you expect to see the board as serial device in Windows you need to upload a sketch compiled with the USB Option Serial first (as Frank described above),

  5. #5
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    14:10:38.624 (post_compile 1): Begin, version=1.53, high-res time
    14:10:38.756 (loader): Teensy Loader 1.53, begin program
    14:10:38.814 (loader): File "TeensyCode.ino.hex". 16084 bytes, 25% used
    14:10:38.829 (loader): Listening for remote control on port 3149
    14:10:38.829 (loader): initialized, showing main window
    14:10:38.897 (loader): remote connection 1344 opened
    14:10:38.898 (loader): remote cmd from 1344: "comment: Teensyduino 1.53 - WINDOWS (teensy_post_compile)"
    14:10:38.898 (loader): remote cmd from 1344: "status"
    14:10:38.898 (post_compile 1): Sending command: comment: Teensyduino 1.53 - WINDOWS (teensy_post_compile)
    14:10:38.900 (loader): HID/win32: vid:046D pid:C52B ver:1203
    14:10:38.900 (loader): HID/win32: vid:258A pid:1007 ver:0100
    14:10:38.901 (loader): HID/win32: vid:258A pid:1007 ver:0100
    14:10:38.901 (loader): HID/win32: vid:258A pid:1007 ver:0100
    14:10:38.901 (loader): HID/win32: vid:046D pid:C52B ver:1203
    14:10:38.901 (loader): HID/win32: vid:046D pid:C52B ver:1203
    14:10:38.902 (loader): HID/win32: vid:258A pid:1007 ver:0100
    14:10:38.902 (loader): HID/win32: vid:046D pid:C52B ver:1203
    14:10:38.902 (loader): HID/win32: vid:046D pid:C52B ver:1203
    14:10:38.902 (loader): HID/win32: vid:046D pid:C52B ver:1203
    14:10:38.903 (loader): remote cmd from 1344: "dir:C:\Users\bu\AppData\Local\Temp\arduino_build_ 80980\"
    14:10:38.903 (loader): remote cmd from 1344: "file:TeensyCode.ino.hex"
    14:10:38.903 (post_compile 1): Status: 1, 0, 0, 0, 0, 0, C:\Users\bu\AppData\Local\Temp\arduino_build_80980 \, TeensyCode.ino.hex
    14:10:38.903 (post_compile 1): Sending command: dir:C:\Users\bu\AppData\Local\Temp\arduino_build_8 0980\
    14:10:38.903 (post_compile 1): Sending command: file:TeensyCode.ino.hex
    14:10:38.912 (loader): File "TeensyCode.ino.hex". 16084 bytes, 25% used
    14:10:38.912 (loader): remote cmd from 1344: "status"
    14:10:38.912 (loader): remote cmd from 1344: "auton"
    14:10:38.922 (post_compile 1): Status: 1, 0, 0, 0, 0, 0, C:\Users\bu\AppData\Local\Temp\arduino_build_80980 \, TeensyCode.ino.hex
    14:10:38.922 (post_compile 1): Sending command: auton
    14:10:38.923 (post_compile 1): Disconnect
    14:10:38.943 (loader): remote connection 1344 closed
    14:10:38.997 (post_compile 2): Begin, version=1.53, high-res time
    14:10:38.997 (loader): remote connection 1348 opened
    14:10:38.997 (loader): remote cmd from 1348: "comment: Teensyduino 1.53 - WINDOWS (teensy_post_compile)"
    14:10:38.997 (loader): remote cmd from 1348: "status"
    14:10:38.997 (loader): remote cmd from 1348: "dir:C:\Users\bu\AppData\Local\Temp\arduino_build_ 80980\"
    14:10:38.997 (loader): remote cmd from 1348: "file:TeensyCode.ino.hex"
    14:10:38.997 (loader): File "TeensyCode.ino.hex". 16084 bytes, 25% used
    14:10:38.999 (post_compile 2): Sending command: comment: Teensyduino 1.53 - WINDOWS (teensy_post_compile)
    14:10:39.000 (post_compile 2): Status: 1, 1, 0, 0, 0, 0, C:\Users\bu\AppData\Local\Temp\arduino_build_80980 \, TeensyCode.ino.hex
    14:10:39.000 (post_compile 2): Sending command: dir:C:\Users\bu\AppData\Local\Temp\arduino_build_8 0980\
    14:10:39.000 (post_compile 2): Sending command: file:TeensyCode.ino.hex
    14:10:39.013 (loader): remote cmd from 1348: "status"
    14:10:39.018 (post_compile 2): Status: 1, 1, 0, 0, 0, 0, C:\Users\bu\AppData\Local\Temp\arduino_build_80980 \, TeensyCode.ino.hex
    14:10:39.018 (post_compile 2): Disconnect
    14:10:39.044 (loader): remote connection 1348 closed
    14:10:39.044 (loader): remote connection 1352 opened
    14:10:39.044 (loader): remote connection 1356 opened
    14:10:39.044 (post_compile 3): Running teensy_reboot: "C:\Program Files (x86)\Arduino\hardware\teensy\..\tools\teensy_rebo ot.exe" teensy_reboot.exe "-board=TEENSY41" "-port=COM3" "-portlabel=(null)" "-portprotocol=(null)"
    14:10:39.053 (reboot 4): Begin, version=1.53, high-res time
    14:10:39.053 (reboot 4): location = COM3
    14:10:39.053 (reboot 4): portlabel = (null)
    14:10:39.053 (reboot 4): portprotocol = (null)
    14:10:39.053 (reboot 4): LoadLibrary cfgmgr32 ok
    14:10:39.053 (reboot 4): LoadLibrary ntdll ok
    14:10:39.055 (reboot 4): nothing new, skipping HID & Ports enum
    14:10:39.056 (reboot 4): Disconnect
    14:10:39.075 (loader): remote connection 1356 closed
    14:10:39.075 (loader): remote connection 1352 closed
    14:10:41.287 (loader): Verbose Info event

  6. #6
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany
    Posts
    8,225
    Yes, the 4.2 was a typo, sorry.
    Your Teensy is not beeing detected.

    Either a wrong cable or the Teensy is broken.

  7. #7
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    How often are the Teensys broken? Does PJRC stand behind their product and ship out a working one?

  8. #8
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany
    Posts
    8,225
    I never saw a *new* broken teensy.
    It's almost impossible, because PJRC needs to install the bootloader, which only works if the Teensy is working.
    Then, it blinks, which means the bootloader was installed successfully. This requires working USB.

    Its way more likely that tha cable is wrong or there is a problem with it.
    Or the PC? Have you rebooted, as I suggested? Do you use a HUB?

  9. #9
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    I do not use a HUB. Have tried it on 2 different PCs with 3 different USB cables.
    I have also rebooted as you had recommended.

  10. #10
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany
    Posts
    8,225
    Cable: Have you tried your smartphone or an other device?
    Which OS are you using? Windows, Linux , MAC?

  11. #11
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    I use Windows 10.

  12. #12
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,728
    When the Teensy is plugged in does pressing the 'Button' take the Teensy into Bootloader mode and show the RED LED? If connected and TeensyLoader is active does it show any signs of seeing the Teensy in the GUI or the Verbose info ?

    Is the Teensy as received? Without anything soldered or connected since received?

    Any chance it was damaged in shipping? Do a quick comparison of the PCB top and bottom to the images of the T_4.1 on the PJRC.com website to assure no components got knocked off perhaps?
    Last edited by defragster; 02-03-2021 at 09:54 PM.

  13. #13
    Senior Member
    Join Date
    Apr 2020
    Location
    DFW area in Texas
    Posts
    229
    @defragster:

    From the other thread where 3D2Code has also discussed this problem (which seems to indicate that it is not "as received"):

    Quote Originally Posted by 3D2Code View Post
    It looks like I possibly have a bad Teensy4.1 (yes, after having soldered the Teensy on to the CNC board).
    It gets power. Stops blinking the light when I push the tiny button on it. But when it comes to communicating with the Arduino IDE - no dice
    Mark J Culross
    KD5RXT

  14. #14
    Junior Member
    Join Date
    Feb 2021
    Posts
    16
    Hi All,

    Turned out it was the USB cable. I purchased a brand new cable from Micro Center and it seems to have fixed the problem.
    I owe the PJRC folks an apology for my lack of attention. I think the USB cable was already mentioned several times.

    Anyhow, now, I can see the Teensy on the Arduino IDE. When I tried to load the blink fast program The Teensy Loader actually showed a response, and said Reboot OK. I changed the delay in the program to make sure that the linking led was due to the program and not some other default behavior. and the frequency of the blinking changed. So it seems to be working.

Posting Permissions

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