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

Thread: T 3.2 windows 7 driver ?

  1. #1
    Senior Member
    Join Date
    Apr 2019
    Posts
    158

    T 3.2 windows 7 driver ?

    I have a customer who has plugged in a programmed T3.2

    device manager sees the device as a usb serial device - but has not found a driver for it

    is there a specific driver that will work ?

    pls advise

  2. #2
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    6,675
    Yes Windows 7 requires a driver to be installed. See the Teensyduino install page: https://www.pjrc.com/teensy/td_download.html
    There is a Windows Serial Installer link there.

  3. #3
    Senior Member
    Join Date
    Apr 2019
    Posts
    158
    Quote Originally Posted by KurtE View Post
    Yes Windows 7 requires a driver to be installed. See the Teensyduino install page: https://www.pjrc.com/teensy/td_download.html
    There is a Windows Serial Installer link there.

    what is the name of the exact driver it uses ?

    can i install it manually ?

  4. #4
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    6,675
    Sorry I don't remember the details: The installer program which you could see from the previous post is: https://www.pjrc.com/teensy/serial_install.exe

    But where it actually copies the files and the like? I don't remember. I moved off of Windows 7 when 10 came out.

  5. #5
    Senior Member
    Join Date
    Apr 2019
    Posts
    158
    it uses USBSER.SYS

    is there a way to rename the device so it does not appear as 'Teensy USB Serial' in device manager ?

  6. #6
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,840
    Quote Originally Posted by Gadget999 View Post
    is there a way to rename the device so it does not appear as 'Teensy USB Serial' in device manager ?
    Yes, there is a way, but it's not free. You will need a code signing certificate. This is the best place I've found.

    https://www.ksoftware.net/code-signing-certificates/

    The cheap OV type is fine.

    Once you have your code signing cert, then edit CDCACM.INF (or course you can edit this file all you like... but Windows will not use it without a matching & properly signed .CAT file). Near the end you'll find these lines. Change them to whatever you like!

    Code:
    [Strings]
    MFGNAME="PJRC.COM, LLC."
    DEVNAME="Teensy USB Serial"

    The main complication you will encounter is use of Hardware-id vs Compatible-id. PJRC's "CDCACM.INF" uses these lines to match to devices:

    Code:
    [DeviceList]
    %DEVNAME%=DriverInstall,USB\Class_02&SubClass_02&Prot_01
    
    [DeviceList.NTamd64]
    %DEVNAME%=DriverInstall,USB\Class_02&SubClass_02&Prot_01
    By default, Microsoft's tools will not allow you to sign this. The easiest solution is to change this to match to vendor and product id, instead of class, subclass, protocol. Or you can try to work around the tools... but that is very difficult and as far as I know there are no tutorials or examples anywhere. You can find numerous sites and examples for INF files using hardware id matching.

    Microsoft's tools are part of the free (but enormous download) Windows Driver Kit. You don't need the rest of the WDK, but as far as I know that's the only way to get the 2 small command line utils.

    First you run INF2CAT, to create an unsigned .CAT file which matches the .INF file. Then run SIGNTOOL to sign the .CAT file using your code signing certificate.


    Years ago PJRC stopped distributing the raw .INF file. Most Windows users prefer the installer. While it is possible to install the .INF without an installer program, our experience was many users got stuck trying to install it manually. It became too much of a tech support burden, and created a barrier for many Windows users. So we no longer distribute the raw .INF and .CAT files on the PJRC website.

    After you've run the Teensyduino installer, you can find it somewhere in C:\Windows\inf (which is a hidden folder). But Windows renames it to an auto-generated "oem" name, so there's no simple & easy directions I can give you. Instead, I'll attach a zip file with CDCACM.INF and CDCACM.CAT which the Teensyduino installer uses when you install into Windows 8 or earlier.

    But remember, after you change anything in the .INF file, you must create a new .CAT file with a proper digital signature. You must have a valid code signing certificate to create the signature.
    Attached Files Attached Files

  7. #7
    Junior Member
    Join Date
    Dec 2019
    Posts
    8
    That's really interesting that you don't need an EV certificate to sign the driver. Will drivers signed with that OV cert still work in Windows 10? It doesn't appear so, looking at the ksoftware.net page.

  8. #8
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    21,840
    I do not have direct experience with this, but everything I've seen says you only need the EV cert to sign actual binary code. So if you were to write your own replacement for USBSER.SYS and sign that, you'd need the expensive EV cert. The cheap OV one is supposed to be enough for signing INFs.

    But again, this is not based on direct experience. Because Microsoft finally included a INF with Windows 10 to cause their own USBSER.SYS to work with devices implementing the USB communication class standard, I have not needed to make any INFs for Windows 10.

  9. #9
    Senior Member
    Join Date
    Apr 2019
    Posts
    158
    is it possible to use regedit to modify the 'device description' ?

    i tried to edit the registry but was unable to save changes

    ---------------------------------------------------------------------

    a lot of my customers use windows 7

    could you give us that want to use the Teensy as a redistributed product a version of CDCACM.INF / .CAT that is described as 'USB Serial'

Posting Permissions

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