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

Thread: after upgrading to Arduino IDE 1.8.7 and Teensy loader 1.44 no teensy boards detected

  1. #1

    after upgrading to Arduino IDE 1.8.7 and Teensy loader 1.44 no teensy boards detected

    I recently upgraded to the latest Arduino IDE, 1.8.7 and the latest version ot teensyduino, 1.44 on my windows 7, 64 bit professional system. Now the IDE doesn't find any teensy boards. I've tried a couple of different ones 3.2 and 3.5 with two different cables and different USB ports both built-in and on a pci adapter. Nothing cleared this error. I restarted the system. I deleted the com 16 device using device manager then plugged in a 3.5 board. It installed the Com 16 back but in the IDE it isn't labeled as a teensy 3.5. I even went back to basics and loaded blink with just serial usb selected.

    The ide gives this error.

    No Teensy boards were found on any USB ports of your computer.
    Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.

    pressing the program button did nothing.

    The loader gave me this

    10:48:22.093 (ports 5): callback C2C5
    10:48:41.370 (post_compile 14): Begin, version=1.44, 1ms res time
    10:48:41.376 (loader): remote connection 276 opened
    10:48:41.380 (post_compile 14): Sending command: comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)
    10:48:41.380 (loader): remote cmd from 276: "comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)"
    10:48:41.385 (loader): remote cmd from 276: "status"
    10:48:41.398 (loader): remote cmd from 276: "dir:C:\Users\JimD\AppData\Local\Temp\arduino_buil d_695028\"
    10:48:41.398 (post_compile 14): Status: 1, 1, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_434 248\, Millennium_V1-00.ino.hex
    10:48:41.398 (post_compile 14): Sending command: dir:C:\Users\JimD\AppData\Local\Temp\arduino_build _695028\
    10:48:41.402 (post_compile 14): Sending command: file:Blink.ino.hex
    10:48:41.403 (loader): remote cmd from 276: "file:Blink.ino.hex"
    10:48:41.411 (loader): File "Blink.ino.hex". 10520 bytes, 4% used
    10:48:41.418 (loader): remote cmd from 276: "status"
    10:48:41.429 (post_compile 14): Status: 1, 1, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_695 028\, Blink.ino.hex
    10:48:41.429 (post_compile 14): Disconnect
    10:48:41.440 (loader): remote connection 276 closed
    10:48:41.661 (post_compile 15): Begin, version=1.44, 1ms res time
    10:48:41.667 (loader): remote connection 792 opened
    10:48:41.672 (loader): remote cmd from 792: "comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)"
    10:48:41.672 (post_compile 15): Sending command: comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)
    10:48:41.678 (loader): remote cmd from 792: "status"
    10:48:41.690 (post_compile 15): Status: 1, 1, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_695 028\, Blink.ino.hex
    10:48:41.690 (loader): remote cmd from 792: "dir:C:\Users\JimD\AppData\Local\Temp\arduino_buil d_695028\"
    10:48:41.690 (post_compile 15): Sending command: dir:C:\Users\JimD\AppData\Local\Temp\arduino_build _695028\
    10:48:41.694 (post_compile 15): Sending command: file:Blink.ino.hex
    10:48:41.694 (loader): remote cmd from 792: "file:Blink.ino.hex"
    10:48:41.701 (loader): File "Blink.ino.hex". 10520 bytes, 4% used
    10:48:41.709 (loader): remote cmd from 792: "status"
    10:48:41.720 (post_compile 15): Status: 1, 1, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_695 028\, Blink.ino.hex
    10:48:41.720 (post_compile 15): Disconnect
    10:48:41.730 (post_compile 16): Running teensy_reboot: "C:\Program Files (x86)\Arduino\hardware\teensy\..\tools\teensy_rebo ot.exe" teensy_reboot.exe "-board=TEENSY35" "-port=COM16" "-portlabel=COM16" "-portprotocol=serial"
    10:48:41.731 (loader): remote connection 792 closed
    10:48:41.737 (loader): remote connection 792 opened
    10:48:41.783 (reboot 17): Begin, version=1.44, 1ms res time
    10:48:41.783 (reboot 17): location = COM16
    10:48:41.783 (reboot 17): portlabel = COM16
    10:48:41.783 (reboot 17): portprotocol = serial
    10:48:41.783 (reboot 17): Serial device COM16 will be tried first
    10:48:41.783 (reboot 17): LoadLibrary cfgmgr32 ok
    10:48:41.783 (reboot 17): LoadLibrary ntdll ok
    10:48:41.787 (reboot 17): nothing new, skipping HID & Ports enum
    10:48:41.793 (loader): remote connection 276 opened
    10:48:41.798 (reboot 17): Disconnect
    10:48:41.812 (loader): remote connection 276 closed
    10:48:41.820 (loader): remote connection 792 closed

  2. #2
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    2,802
    did you disable your antivirus before installing teensyduino? also teensyduino must be instealled AFTER the IDE is installed
    1.8.7 and 1.44 work fine here

  3. #3
    this may be a dup since my previous post didn't show up. I did a clean install - uninstalled arduino ide. stopped antivirus then installed arduino ide and teensyduino code. I did notice that the IDE installed usb drivers and so did the teensydino. I accepted both. I removed the com 16 device and when I plugged in a 3.2 board (same with 3.5 board), the device was detected as a USB serial on com 16. When I try to upload blink into either board I keep getting this error.


    No Teensy boards were found on any USB ports of your computer.
    Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.

  4. #4
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    2,802
    you tried holding the program button before plugging teensy in the PC?

  5. #5
    just tried and got the same result. In the past, in the ide, the board type
    came up next to the com port. I know the board is com 16 since that is what comes up after I delete it and plug the board in. now it just says com 16.

  6. #6
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    2,802
    try to goto device manager port settings of com16 and force it to use a different port number

  7. #7
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,655
    Quote Originally Posted by jrdarrah View Post
    pressing the program button did nothing.
    First, let's focus on this. This can be seen as 2 different problems.

    #1: You can't upload programs onto your Teensy at all, even if you press the button on the Teensy. Your Teensy is forever stuck running the LED blink program that was loaded onto it at PJRC when the board was tested.

    #2: You can upload programs, but only by pressing the button. Your Teensy almost certainly is running something other than the original LED blink. For reasons unknown, Arduino can't cause it to reboot automatically... so you're forced to do the extra inconvenient step of pressing the button.

    The words in your most recent message sound like case #2. But since you wrote "pressing the program button did nothing" originally, maybe this is really case #1.

    Then again, you said you're getting COM16. The original blink uses RawHID, not serial, so the only way to get a new COM port is by successfully uploading at least once. So, I must admit, I'm confused by this combination of things you've said....

    Assuming we really are in case #1, can you please confirm 2 things? First, when you power up the Teensy just by plugging in the case, the LED should blink slowly. Every Teensy is programmed at PJRC with the LED blink example. So if you've *never* managed to program your Teensy, if should still have that original blink program on it. Thing #2: when you press the button, you should notice the LED stops blinking. This is an important distinction from "did nothing". If the LED is blinking and the button truly does nothing, not even stop the LED from blinking, then we're looking at a completely different type of problem (like a mechanical failure of the button).

    If you're actually seeing case #2, the behavior before pressing the button isn't clearly known because the Teensy will have whatever program was previously uploaded. In this case, keep the Teensy Loader window visible on your desktop. When you press the button, that window is supposed to respond. It reprograms your Teensy very quickly if Auto Mode is turned on (which is the default if Arduino has compiled your code). For testing whether USB works, turning off the Auto mode in the Teensy Loader window can really help. Then it's easy to see if Teensy is recognized by the Teensy Loader when you press the button, even if you happen to not be watching during the very brief time is takes to upload new code.

  8. #8
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,655
    Since you're using Windows 7, here's a couple known problems that can affect access to COM ports.

    But please remember Teensy uses HID protocol, not serial, for uploading. So when you've pressed the button on Teensy, and if Teensy Loader isn't in Auto Mode where it quickly reprograms and reboots your Teensy (before you have time to look at the Windows Device Manager), you should see Teensy appear as a HID device. It should *never* be COM16 after you've pressed the button (unless of course Teensy Loader is using Auto Mode to successfully reprogram it and reboot back to your freshly programmed code - which *is* the default behavior when everything is working properly).

    Recently Audodesk Print Manager has been reported to interfere with access to COM ports. It may be mistaking Teensy for a 3D printer.

    https://forum.pjrc.com/threads/40632...l=1#post191406

    Windows 7 (and all pre-10 versions of Windows) have a serial driver bug (in USBSER.SYS) which causes the COM port to be unresponsive the next time it appears, if any program had the port open while Teensy rebooted or the cable was unplugged.



    Generally this is not an issue if you use only Arduino, because the Arduino Serial Monitor automatically closes when you click Upload. But if you have other software like CoolTerm accessing the port when you press the button or upload code or unplug the cable, then the next time Teensy appears you can hit this issue.

    Again, this bug is only for COM port access. Teensy uses HID for programming, so even if you've hit this problem, you should still see Teensy Loader recognize the device when you press the button. If Teensy Loader is not using Auto Mode, you should still see Teensy appear in the Windows Device Manager as a Human Interface Device while it's in programming mode. If things aren't working, I recommend first looking for the HID stuff.

    You can also set Teensy > USB Type in Arduino to Keyboard or RawHID, which will cause Teensy to use only HID protocol (not serial) when it runs your program. Even if you need a COM port for some reason, that might be worth a try to help figure out if these problems are only with Microsoft's serial driver (which is quite buggy in Windows 7) or with any type of USB communication. The good news is all versions of Windows have a good quality HID driver built in... which is reason Teensy was designed to use only HID protocol for uploading.

    Hopefully this helps?

  9. #9
    Latest attempt. I uninstalled the com16 device and plugged in a new 3.5 still running blink. I see the led flashing slowly.

    in device manager com16 came up as usb serial device so it is the teensy.

    in arduino IDE i brought up blink and get the same error - No teensy boards found. in the loader window it did change to blink.ino.hex. I turned off automatic mode and verbose information.

    Pressing the program button made the led quit blinking so I'm guessing the button worked. Nothing showed up in the verbose window except a string of these messages

    16:14:14.897 (ports 19): callback C2B7
    16:15:13.969 (ports 19): callback C2B7
    16:16:13.983 (ports 19): callback C2B7
    16:17:13.997 (ports 19): callback C2B7
    16:18:14.010 (ports 19): callback C2B7
    16:19:14.024 (ports 19): callback C2B7
    16:20:14.038 (ports 19): callback C2B7
    16:21:14.058 (ports 19): callback C2B7

    As a final test with the button pressed first and no led blinking I tried loading using the ide and got these messages in the verbose window.

    16:21:55.904 (loader): file changed
    16:21:55.908 (loader): File "Blink.ino.hex". 9380 bytes, 4% used
    16:21:55.983 (post_compile 24): Begin, version=1.44, 1ms res time
    16:21:55.988 (loader): remote connection 448 opened
    16:21:55.989 (post_compile 24): Sending command: comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)
    16:21:55.989 (loader): remote cmd from 448: "comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)"
    16:21:55.990 (loader): remote cmd from 448: "status"
    16:21:55.999 (post_compile 24): Status: 1, 0, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_627 765\, Blink.ino.hex
    16:21:55.999 (loader): remote cmd from 448: "dir:C:\Users\JimD\AppData\Local\Temp\arduino_buil d_627765\"
    16:21:55.999 (post_compile 24): Sending command: dir:C:\Users\JimD\AppData\Local\Temp\arduino_build _627765\
    16:21:56.000 (loader): remote cmd from 448: "file:Blink.ino.hex"
    16:21:56.000 (post_compile 24): Sending command: file:Blink.ino.hex
    16:21:56.004 (loader): File "Blink.ino.hex". 9380 bytes, 4% used
    16:21:56.009 (loader): remote cmd from 448: "status"
    16:21:56.018 (post_compile 24): Status: 1, 0, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_627 765\, Blink.ino.hex
    16:21:56.018 (loader): remote cmd from 448: "auton"
    16:21:56.018 (post_compile 24): Sending command: auton
    16:21:56.019 (post_compile 24): Disconnect
    16:21:56.030 (loader): remote connection 448 closed
    16:21:56.262 (post_compile 25): Begin, version=1.44, 1ms res time
    16:21:56.267 (loader): remote connection 448 opened
    16:21:56.269 (post_compile 25): Sending command: comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)
    16:21:56.269 (loader): remote cmd from 448: "comment: Teensyduino 1.44 - WINDOWS (teensy_post_compile)"
    16:21:56.271 (loader): remote cmd from 448: "status"
    16:21:56.280 (post_compile 25): Status: 1, 1, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_627 765\, Blink.ino.hex
    16:21:56.280 (loader): remote cmd from 448: "dir:C:\Users\JimD\AppData\Local\Temp\arduino_buil d_627765\"
    16:21:56.280 (post_compile 25): Sending command: dir:C:\Users\JimD\AppData\Local\Temp\arduino_build _627765\
    16:21:56.282 (post_compile 25): Sending command: file:Blink.ino.hex
    16:21:56.282 (loader): remote cmd from 448: "file:Blink.ino.hex"
    16:21:56.287 (loader): File "Blink.ino.hex". 9380 bytes, 4% used
    16:21:56.292 (loader): remote cmd from 448: "status"
    16:21:56.302 (post_compile 25): Status: 1, 1, 0, 0, 0, 0, C:\Users\JimD\AppData\Local\Temp\arduino_build_627 765\, Blink.ino.hex
    16:21:56.302 (post_compile 25): Disconnect
    16:21:56.312 (loader): remote connection 448 closed
    16:21:56.312 (post_compile 26): Running teensy_reboot: "C:\Program Files (x86)\Arduino\hardware\teensy\..\tools\teensy_rebo ot.exe" teensy_reboot.exe "-board=TEENSY31" "-port=COM16" "-portlabel=COM16" "-portprotocol=serial"
    16:21:56.314 (loader): remote connection 784 opened
    16:21:56.359 (reboot 27): Begin, version=1.44, 1ms res time
    16:21:56.359 (reboot 27): location = COM16
    16:21:56.359 (reboot 27): portlabel = COM16
    16:21:56.359 (reboot 27): portprotocol = serial
    16:21:56.359 (reboot 27): Serial device COM16 will be tried first
    16:21:56.359 (reboot 27): LoadLibrary cfgmgr32 ok
    16:21:56.359 (reboot 27): LoadLibrary ntdll ok
    16:21:56.364 (reboot 27): nothing new, skipping HID & Ports enum
    16:21:56.370 (loader): remote connection 452 opened
    16:21:56.373 (reboot 27): Disconnect
    16:21:56.384 (loader): remote connection 452 closed
    16:21:56.389 (loader): remote connection 784 closed
    16:22:14.066 (ports 19): callback C2B7

    the 3.5 board is still dark but started blinking after I unplugged the usb cable and then plugged it back in again. Paul, based on your post I think I have problem #1.

  10. #10
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,655
    Quote Originally Posted by jrdarrah View Post
    Latest attempt. I uninstalled the com16 device and plugged in a new 3.5 still running blink.
    ....
    in device manager com16 came up as usb serial device so it is the teensy.
    Is this a brand new Teensy 3.5? If it has been previously used, this would make sense. But a brand new Teensy should *NEVER* appear as a COM port when first plugged in. We program them to first appear as RawHID.

    the 3.5 board is still dark but started blinking after I unplugged the usb cable and then plugged it back in again. Paul, based on your post I think I have problem #1.
    If you really have problem #1, all this focus on COM ports is a wrong path to take. Teensy uses HID protocol. After you've pressed the button, assuming Teensy Loader is not in Auto Mode (and quickly uploading successfully), you need to look in the Windows Device Manager for a HID device with ID 16C0 / 0478. Here's what you should see:

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

    Just to repeat yet again, after you press the button, Teensy is NOT SUPPOSED TO BE A COM PORT. You should not see COM16 (unless COM16 is something else not your Teensy). The Teensy should be a "HID-compliant device" in Windows Device Manager.

  11. #11
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,655
    I should mention, the most common USB problem is charge-only cables made for cell phones. Those cables have only the power wires. They save cost by not even using wires for the data pins.

    Perhaps that COM16 you're seeing isn't actually Teensy at all? If it's something unrelated, then everything else you've described could be explained by simply a bad USB cable.

  12. #12
    As a final test for tonight I went back to my previous levels -- 11.8.4 for the IDE and 1.39 for the loader I thought it was 1.42 but the previous installer was at 1.39. In the loader I see it doing something...

    a bunch of these messages in the loader

    18:31:18.318: remote cmd: "status"
    18:31:18.320: status data sent
    18:31:18.323: remote cmd: "status"
    18:31:18.325: status data sent
    then remote connection closed.

    What I don't see is any messages on the IDE of success in uploading or any change to the led I modified blink to stay on yet it sill blinks. So the programming failed.

    turning off the auto mode and pressing the button turned off the LED but nothing showed up in the verbose window.

    How can I get the 1.42 loader to see if for some reason on my system 1.44 doesn't work? Thanks for sticking with this.

  13. #13
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,655
    Quote Originally Posted by jrdarrah View Post
    pressing the button turned off the LED but nothing showed up in the verbose window.
    Pretty sure you have a defective USB cable.

    Does any new HID device show up in the Windows Device Manager after pressing the button, when the LED is no longer blinking? It's supposed to look like this:


  14. #14
    You may be on to something. I tried a third USB cable and everything worked. At 1.8.4 and 1.39. Tomorrow I'll repeat with everything up level and post the results.

  15. #15
    It also works with IDE 1.87 and loader 1.44. It was the cable. I looked at the two I tried and failed with. Both were similar and grabbed from my cable box. I'm thinking now that they were from an old phone charger and only had the supply wires but not the data. I just put them in the trash since I bought a new one today which works just great Thanks for the help.

  16. #16
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    2,802
    im just surprised you managed to get a com16 with a power cable

  17. #17
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,655
    Maybe the COM16 was something else?

    @jrdarrah - The way to tell, if you're willing to look into this, would be using the Windows Device Manager "details" tab, like in the screenshot on msg #13. Click the drop-down list and choose "Hardware Ids". That info can tell us what COM16 really is - or at least which vendor and product ID is has.

  18. #18
    This is what came up on com16 -- FTDIBUS\COMPORT&VID_0403&PID_7A58. I associated this with the teensy, but I just ran a test without a teensy attached to the usb port and com 16 still comes up. It popped up when I plugged in the teensy and did scan for hardware changes. never tried scanning without the teensy plugged in. I guess I didn't take my problem solving far enough.

    The only possible device that might have this is the amazon firetv adapter. Thanks for the help. How do I trace the VID-PID back to a manufacturer?

  19. #19
    Senior Member
    Join Date
    Dec 2016
    Location
    Montreal, Canada
    Posts
    2,802
    http://www.catalog.update.microsoft....f-a2b5b89bffb7

    aparently belongs to benq FTDI adaptor
    you can just google the vidpid and see what the results bring

    vids/pids are usually based on different hardware, like models and submodels.

  20. #20
    thanks. I do have a Benq monitor.

Posting Permissions

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