[Ftdi-usb-sio-devel] 2 requests: (1) add new VID/PID, (2) Add Feature
                
                Brought to you by:
                
                    bryder
                    
                
            
            
        
        
        
    | 
     
      
      
      From: <du...@du...> - 2016-01-16 21:29:55
      
     
   | 
Request #1
    Please add:
    Vendor id:    0403
    Product id:    a6d1
    Description:  Texas Instruments XDS100v3
    What is it? A Combination JTAG probe and Serial Port developers kit.
    This is commonly embedded in multiple development boards offered by
TI.
    TI Also provides design details, and several 3rd parties make
clones.
Additional detail here (and user manual)
    http://www.ti.com/lit/ug/swru321a/swru321a.pdf
    Specifically Section 4.1.2.2 - Page 9/32
    Also see:  Figure 6, Page 13/32 
    This shows the design "built into" an example development board.
    Note: This design is replicated in multiple places not just this
board.
    Schematics etc can be found in Appendix A of the document. 
Request #2
    By default the driver for the FT2232H - loads *TWO* serial ports.
    In this case, it *should*not* load two ports, it should load only
one port.
On Windows -it works differently. The FTDI driver reads the EEPROM and
determines which ports should have serial interfaces, and which should
not.
The request here is to act like windows and read the attached EEPROM and
examine the bit that identifies what each port *should* and *should* not
be configured as a serial port.
For example - 
step 1: You'll need an FTDI device with the FTDI drivers configured.
step 2: Run the FT_PROG (windows) application (this tool is used to
program the EPROM)
Step 3: Select DEVICES -> SCAN AND PARSE
Step 4: You'll find the FT_EEPROM in the menu
Step 5: Expand the "Hardware Specific" tab
Step 6: Expand the "Port A" (or B, or C ... ) tab and the "Driver"
sub-tab.
Take note:  Radio Buttons:  "Virtual COM Port" vrs "D2XX Direct"
The request here is this:
If the port is marked as VIRTUAL COM port, the driver should load for
this comport.
If the port is marked as D2XX - do not configure the port as a comport.
Thanks.
S
 |