This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

INF file needed for the USB bulk device example

The StarterWareUSB page says the INF file needed for the USB bulk device example can be downloaded from the StellarisWare download page. But that webpage no longer exists.  (The link goes to a company called "Luminary Micro", which TI acquired some years ago, and took down their webpages.)

Where can I now download the INF file needed for the USB bulk device example?

Thanks for your help.

-- Walter

  • StarterWare is derived from StellarisWare. The USB examples still have StellarisWare IDs in them. When TI moved from Stellaris to Tiva, they removed everthing Stellaris. That is until they realized StarterWare as dependent on the Stellaris Windows code. They brought it back here:

    www.ti.com/.../sw-usb-windrivers
    StellarisWare embedded USB drivers

    Who knows how long it will stay there. Also has the host side application for the usb bulk example.
  • Norman Wong,

    Thank you for your help in posting a link to a relevant TI file, called "SW-USB-windrivers-6459.zip".  I downloaded that file and it appears to contain incomplete information.  That is, the TI Starterware USB page says to install "The INF file ... located at windows_drivers/usb_dev_bulk.inf".  There is a directory called "windows_drivers" but no such file is in it, nor anywhere in that zip file.  Where is that .inf file? 

    The  TI Starterware USB page also says to download an application called "usb_examples/usb_bulk_example.exe".  But again, there is no such file, and in this case, no such directory. 

    The  TI Starterware USB page also mentions another file called "SW-USB-WIN". Perhaps that is located here.  Is that correct?  Is this another one of these huge Stellarisware packages to download, yet only a tiny fraction of it is actually needed for USB bulk device operation? 

    [Note to TI staff:  A forum search shows this problem discussed back several years already, yet there is still erroneous information (and dead links to "Luminary Micro", such as "StellarisWare download page")posted on the  TI Starterware USB page. Can some industrious TI employee please streamline this process of getting the USB port to work?]

    -- Walter

     

  • I downloaded the archive SW-USB-windrivers-6459.zip back in 2012. It does have the windows_drivers/usb_dev_bulk.inf file. I forgot about the other package SW-USB-WIN aka SW-USB-win-9107.msi. I remember installing both on my Windows XP machine. The USB serial and bulk drivers worked for me. That said, there are many forums threads about installation problems on other versions of Windows where a CoInstaller needs to run. Vaguely remember a lot of conflict between using libusb vs WinUSB.

    The scope and usb_bulk_example.exe applications must have come from the msi install. Never tried the scope thing. This MSI install is about 2MB. It is not the same as the StellarisWare install of 500MB. The StellarisWare archive contains SW-USB-windrivers-6459 and SW-USB-win-9107.msi. I eventually did download and install StellarisWare to access the source code for the windows applications.

  • Norman Wong,

    Thank you for your help and insight.  You are correct, the .inf file is contained in the SW-USB-windrivers-6459.zip file. (Though Windows Explorer lists it as a "Setup Information" file rather than a .inf file, duh, my mistake.)

    I have also found and downloaded the other file listed previously (SW-USB-win-9107.msi). So all the relevant TI files are now present and accounted for, (though I hope TI will update their Starterware USB page to eliminate the dead links, etc.)

    ******

    The .msi file says:

    Signing the drivers requires Windows Device Driver Kit ....

    Prior to running the signtool command, you must create a test certificate for use in signing your drivers and install this certificate on your machine. 

    1. Build catalog files for each driver ...
    2. Sign the catalog files with our software test certificate: ...

    This assumes that the "<YourTestCertificateName>" certificate has been installed on your build machine in the TestCertStore certificate store.

    All of that is cryptic to me ... It is yet another research program far outside the signal processing I need to get done.  I'll go study this for a while........