• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 1090 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TUSB8020B: EEPROM programming tool for the hub

David Kirschner21
Prodigy 75 points
Part Number: TUSB8020B
Other Parts Discussed in Thread: TUSB8040

Dear TI team,

I have been searching for the EEPROM programming tool for the TUSB8020B hub, but i couldn't find it anywhere. I have seen in a previously closed posts, that you have sent it via email. Could you please also send it to me to the following email address?

david.kirschner [at]joanneum.at

Or actually probably i am not the only one who needs it, could you please post the download link of the software tool?

Thank you in advance!

Best regards,

David

  • 0
    TI__Guru**** 167276 points
    Handled through email.

    Thanks
    David
  • 0 in reply to David (ASIC) Liu
    Prodigy 75 points
    Thanks David, i have received the email, however our system mail security replaced the attachment with a txt:
    "Symantec Mail Security replaced TUSB8040 EEPROM Programmer 1.0.0.1.zip with this text message. The original text contained prohibited content and was deleted."

    Could we find another solution? (Btw. Will the TUSB8040 be suitable for 8020 as well? To be honest, in some hidden forum entry, i have found meanwhile an EEPROM programmer (TUSB80xx) which was shared for the 8040 chip, and i have thought it will work, but when i cannot our board, the program complains, that it doesnt find any 8040 device....and in the main folder there are .cat and .inf file only for the 8040. Therefor i was thinking maybe i need the specific programmer for the 8020.)

    Thanks in advance!
    David
  • 0 in reply to David Kirschner21
    Prodigy 75 points
    Btw. the hub is already on our custom pcb with an msp mcu. Does that influence the connection to the hub? after we load an empty usb project onto the mcu, but the device appears in the device manager as "Unknown USB Device (Device Descriptor Request Failed".

    Even though an eeprom is connected, and SMBUSz/SS_DN2 pin is pulled up, i am not sure the hub enters into programming mode at all....
  • 0 in reply to David Kirschner21
    TI__Guru 60870 points
    Hi David,

    If the hub has an unprogrammed EEPROM attached it will automatically go into programming mode and when it connects to the host it will appear as a USB programming endpoint instead of as a hub. If a previously programmed EEPROM is attached, you will need to force the programming driver to load on the USB 2.0 instance of the hub. Please accept my friend request and I can send you the EEPROM tool directly.

    Also, the hub should work even if the EEPROM is not attached / programmed. Is the MCU upstream or downstream of the hub?

    Regards,
    JMMN
  • 0 in reply to JMMN
    Prodigy 75 points
    Hi JMMN,

    Hm...for sure we havent programmed the EEPROM so far. MCU is in the 2.0 downstream of the hub. PC is upstream. But now i am confused, because as i understand now, the hub enters in programming mode (if an unprogrammed eeprom is connected), but it will exit after a while, and start working properly, won't it? Therefore i see the mcu and i can program, right?
    But in this case, what is the time window, in which i can start the eeprom programming tool on windows? If i start before i power the board, the software wont find the hub. If i do it afterwards, is there a chance the hub has already exited from the programming mode?
    Because i assume the hub doesnt work simultaneously properly and in programming mode.

    Regards,
    David
  • 0 in reply to David Kirschner21
    TI__Guru 60870 points
    Hi David,

    The hub will stay in programming mode under the following conditions:

    1. (SMBUS mode) SMBUSz asserted and the SMBUS host has not set/cleared the cfg active bit in the hub registers.
    2. (I2C mode) SMBUSz not asserted, SDA and SCL pulled high and a blank EEPROM attached.

    The hub does not automatically leave programming mode after a set amount of time.

    Regards,
    JMMN
  • 0 in reply to JMMN
    Prodigy 75 points
    Thanks for all the help you provided, it turned out, the clock signal for the MSP430 is not configured properly (we use crystal on X2), most likely this caused the problem of not entering into programming mode or not recognised by the host..