• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 33 subscribers
  • Views 562 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.

EEPROM address with TUSB3410

javier martin45bits
Prodigy 100 points

Other Parts Discussed in Thread: TUSB3410

Hi, I´m working with the TUSB3410 device. I´m making a simple board just for test very simples USB-MSP430 communications.

In my system I will download the firmware of the TUSB microcontroller from the host (PC). So in the EEPROM device I will only put the descriptors, that are around 140 bytes. 

My question is How the TUSB knows the address of the EEPROM devices ?? because it have to read the descrptors bytes.


I have seen the two examples that TI provide and I saw they use 0x50 like a EEPROM address in both. I don´t know why.

Thanks very much, I hope you can help me

regards 

javier

  • 0
    TI__Guru* 76130 points

    Hello Javier,

    Regarding the communication between the TUSB3410 and the EEPROM: there are defined offset address where the TUSB3410 will look at the boot up process, these values are defined in the boot-code of the bridge.

    In order to program your own descriptor values you need to follow the instructions described on the TUSBWINVCP Customization Guide at the following link  http://www.ti.com/lit/an/slla319/slla319.pdf

    Regards.

  • 0 in reply to Elias Villegas M.
    Prodigy 100 points

    Hello Elias. Thanks for replying.

    I didn`t mean the address of the data into de EEPROM. Any device in I2C protocol needs a address, that is 7 bits long and one bit W/R. In my system I will use a Microchip EEPROM 24LC512. And I can choose the address of this device. But, again, How the TUSB3410 knows this address ???

    regards

    Javier

  • 0 in reply to javier martin45bits
    TI__Guru* 76130 points

    Hello Javier,

    The TSUB3410 does not have to know the serial number of the EEPROM.

    The detection of the external EEPROM is performed via hardware at power-up by the presence of the pull-up. When an EXTERNAL EEPROM is detected the boot code performs a read operation to search for a valid code; in this operation the external EEPROM returns its serial number, if it is valid then TUSB3410 stores this value on the SERNUM7 register, if the serial number is not valid, the TSUB3410 keeps a preloaded serial number.

    Regards.

  • 0 in reply to Elias Villegas M.
    Prodigy 100 points

    Ok, I`m going to put it this way:

    If you want to invite you girlfriend to the cinema, and you are in your house, How do you do ?? ANS: you take the phone, then you dial her phone number, and then you talk to her and invite.

    But if you don´t have her phone number you can`t do it.

    If the TUSB3410 don`t have the "EEPROM phone", he can´t talk to him. So my question is How the TUSB3410 knows the " EEPROM phone number " ??? 

    the phone number is dual to the I2C slave address.

    can you understand me now Elias ?

    many thanks for replay man

    Regards.

    javier

     

  • 0
    Guru 320450 points

    The device address commonly used for I²C EEPROMs is 0x50, and this is indeed what all the suggested EEPROMs use.

    The manual says (section 11.2) that the TUSB3410 searches device addresses 0 and 4, and this is indeed what the code in the Bootcode Source Listing (SLLC139) uses.
    In practice, it appears to work anyway …

  • 0 in reply to Clemens Ladisch
    Prodigy 100 points

    Thanks very much Clemens. That clarifies my doubts.

    regards