• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 34 subscribers
  • Views 723 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.

TUSB3410

Nogcas
Intellectual 260 points
Other Parts Discussed in Thread: MSP430F2013, TUSB3410, MSP430F1612

Hi,

I am pretty new in USB communication stuff. So will need a lot of help here. Ok, my situation here is: I have MSP430F2013, and I would like it to communicate with PC through USB. I read about TUSB3410 and knew that it has I2C communication which is also available on F2013. However, that's I2C in TUSB3410 is on Master mode only (if I dont miss anything). So should it be possible to use TUSB3410 for communicating between MSP430F2013 and the PC?

Will TUSB3410 transfer the data that it received from a Slave (F2013) to PC through USB? Are there any documents that I should read to do that interface?

Regards,

  • 0
    TI__Expert 7435 points

    Nogcas,

    MSP430 platform has parts that have USB device integrated and come with pre-packaged apps that enable you to communicate with the PC.  Can you consider that as another option, seems to be more simpler one and also better at throughput.

    regards

    swami

  • 0 in reply to swami
    Intellectual 260 points

    I am trying to develop a system on MSP430 launchpad. It should do ADC from F2013 and then transfer data through USB from the Launchpad to PC.

    With that's in mind, I reprogrammed the MSP430F1612 in the emulator side (by using FET-UIF, connect to TP holes in PCB from 1->7 to the UIF), to make it works like a bridge.

    However, I am now have a problem with the TUSB. I tried to download the driver (TUSBWINVCP) but it could not recognized the USB. So I tried another method that using EEPROM burner. Here are the steps I did:

    1. Took out the R23, which connects SCL of TUSB to SCL of EEPROM (this step similar to isolating step in the EEPROM burner user guide - just disconnect their SCL pins).
    2. Install the EEPROM burner.
    3. After the EEPROM burner finished, I connected the Launchpad to the PC.

    However, my PC still does not recognize the USB... I even tried to Update Driver through the Device manager but it still doesnt work. I am using Windows 7. Should it be a problem? Any suggestions or recommendations?

    Best Regards,

     

  • 0 in reply to Nogcas
    Guru 17650 points

    Hi Nogcas,

    spamming the community because of a $4.95 tools is great fun, isn't it?

    Read this: http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/p/57046/203427.aspx#203427

    aBUGSworstnightmare

  • 0 in reply to Nogcas
    TI__Genius 16430 points

    The TUSBWINVCP Driver is associated with specific VID/PID combinations.  What does your TUSB3410 hardware consist of?  Do you have an EEPROM attached for USB descriptors?

    The EEPROM burner will not help the USB be recognized.

    When you downloaded the TUBWINVCP software, did you run both Setups?  The first setup.exe only places all the files for all of the different OSs supported on your PC.  You then need to run the second setup.exe that is placed by the first to actaully install the correct driver for the OS you are using.

    The VCP Software package includes both the PC-side Windows Vista and Windows XP drivers as well as the device-side firmware that runs on the 8052 in the TUSB3410.  Note that the download is only the object code versions and is not an  actual full installation.  It rather places the files on the PC.  The default location is under Program Files\Texas Instruments.  It places a SETUP.exe file on the PC that needs to be run in order to install the driver in the Windows directory based on the operating system being used - Vista vs XP and 32-bit vs. 64-bit.  There is a Implementation Video that steps through the usage of this software and the other utilities.

  • 0 in reply to DHarmon
    Intellectual 260 points

    Hi,

    Sorry it takes long time to reply. Anyway, I am be able to reprogram the MSP430F1612 to only provide clock to the TUSB3410. So at this time, I am running the TUSB3410 without EEPROM and it runs as a default TUSB device. This works enough for me. The launchpad is small, cheap but it indeed has a great potential. I love it!!!