• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 33 subscribers
  • Views 917 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

How to initialize TUSB3410 without EEPROM to use as normal UART-USB-Bridge-Mode to transmit data to RS232-Terminal or Lab View

Simon D.
Prodigy 200 points
Other Parts Discussed in Thread: TUSB3410

Hello!


I use the fpga-adc-eval board TSW1200EVM to develope a new measurement system. On the TSW1200 board is a TUSB3410 that works as a uart-usb bridge for communication between fpga and pc.

Ti provides a software to drive the board via PC - therefor they programmed an eeprom for the TUSB3410.

Now, I wanne use the TUSB3410 for my application and without the Ti software: I have to receive the data via com-port terminal or lab view.

If I access com-port 3, I get the message, that this port is used by an other program (even, if i reboot the pc) - the board connects with the pc with "TSW1200EVM".

I removed the I2C eeprom and the TUSB3410 connected to the pc with "TUSB3410 Boot Device". Then the pc ask for a driver that i cant find....

I read the datasheets several times...

My requirements are a normal uart-usb bridge with 8 bit, no parity, variable baudrate, 2 stop bits, and I have no VID and no PID, so I wanne use the Ti default VID and PID.

So my questions are:

- is it right that i need not to program a EEPROM, because, if there is no EEPROM, the TUSB connects to the PC via default VID and PID and then I can write the firmware?

- how can i tell the TUSB3410 my requirements? I have to write the LCR, DLL and DLH Register. Is it the usbuart3410.inf file that contains this informations?

- where can I find a driver for the TUSB3410 default connection (without EEPROM installed)?


Regards and thank you in advance!


S. Darsch

 

 

  • 0
    TI__Intellectual 2170 points

    Hello,

    About your questions:

    1) FW is loaded into the 3410's RAM space using a driver (in this particula case our VCPor Virtual COM Port driver).  It's recommended to use your own VID and PID, and those can be customized via a BIN file that can be burned in an external EEPROM.

    2) A 3410 w/o EEPROM will enumerate using the bootcode already embedded in the device. It won't be recognized unless you use the proper driver interface. Our VCP driver will load the FW and then it wil show it up as a COM port so you can use as a RS-232 interface in your system.

    3) Our VCP driver can work even w/o EEPROM.

  • 0 in reply to Ismael Duron10236
    Prodigy 200 points

    Hello,

    I tried to use the TUSB without EEPROM:

    I removed the EEPROM and connected the board to the usb port. After that, the pc asked me for a driver and I set the directory to "TUSB3410 EEPROM Burner Installer". After the driver was installed I checked if the EEPROM Burner recognizes the TUSB Chip - and it works - so I could program and erase the eeprom via EEPROM burner. But there was no virtual com port I could access (because, there is no firmware for the TUSB???).

    So, I erased the eeprom and I opened the "Header Generator". I choosed the " umpe3410.i51" and "VCP-3410-FW_in_EEPROM.CFG" (these files are located in the Header Generator directory as example) and generate with the generator a *.bin file that I transfered into the eeprom that I erased before... After that, I reconnect the TUSB Chip, and the pc recognized the chip as "TUSB3410 EECode NonSer" but with a "!" behind, because he found no driver - and because of that, there was no virtual com port (?)

    So my questions now are:

    - are the things I described above right?

    - what steps are necessary to get the virtual com port in the device manager

    - is the *.inf file only necessary if the firmware shoud be downloaded by the host  - is it not necessary if the firmware is stored in the eeprom together with the configuration?


    Regards Simon

     

     

  • 0 in reply to Simon D.
    TI__Intellectual 2170 points

    Hi,

    1) Things you described are not completely correct. EEPROM burner app needs a special driver to burn FW. This driver will not enumerate the TUSB3410 as a Virtual COM port. 

    On the contrary, our in order to have your TUSB3410 device look like a Virtual COM port, you need another driver. This driver will load FW from the host PC for you, so you don't need to burn FW in the EEPROM.

    2) By the time you burned FW in EEPROM (generating the BIN with 'umpe3410.i51' and 'VCP-3410-FW_in_EEPROM.CFG'), the 3410 will load FW from the EEPROM instead from the host. With this, you need to install the VCP driver. You see that exclamation symbol, since no VCP driver has been properly install on the system.

    3) The INF file is necessary to install the driver, regardless where the FW is being loaded from. 

     

    NOTE: I suggest using a different PC to try the VCP driver. Both EEPROM burner driver and VCP driver cannot coexist together.