• Resolved

Compiler/TUSB8041: I would like to know what's the order to install firmware on TUSB8041

Prodigy 235 points

Replies: 23

Views: 185

Part Number: TUSB8041

Tool/software: TI C/C++ Compiler

Hi, TI!

I'm a media artist mostly doing coding and somehow, I manage to design the USB - C Hub based on TIDA-03027. 

It has got TPS65982 and TUSB8041. after manufacturing the board,  I'm trying to install firmware on both TPS65932 AND TUSB8041.

Do I need to install Firmware on TPS65982 first, and move to TUSB8041?

I would like to know right order to install.

via Aardvark debugger, TPS65982 can be connected and responding, but TUSB8041 is currently not responding via USB - C port.

I just wonder that's because firmware for TPS65982 is not installed yet.  

If you give me any hint about installing firmware, it would be great help. 

Best,

WOOJUN

  • Hi Woojun,

    So the TUSB8041 does not require firmware or external configuration if you have SMBUSz pin pulled high.  Even if you plan to use a SMBUS or I2C host to configure the hub, can you try setting SMBUSz high just to confirm the USB data lines are routed correctly?

    What type of firmware are you trying to install?

    Thanks,

    JMMN

  • In reply to JMMN:

    Thanks for the reply.

    I meant TUSB80XX EPPROM_programming utility.

    If I ran the program, it said no device is detected.

    is this program is unnecessary? but still wonder why it didn't detect the TSUB8041.

    Best,

    WOOJUN

  • In reply to JMMN:

    probably, I need to get SMBUS pulled high. it is DNP at the moment. 

    Best,

    WOOJUN

  • In reply to WOOJUN LEE:

    Hello Woojun,

    You do not need to use the programming utility unless you have an I2C EEPROM connected to the hub.  The programming utility will only load if the hub is in programming mode.  For I2C, the hub defaults to programming mode when it sees a blank EEPROM connected.  If the EEPROM is already programmed, the driver for the programming utility needs to be force loaded on the USB 2.0 instance of the hub.

    Do not set SMBUSz low unless you are going to use a SMBUS host to configure the hub.

    Please note that your GRSTz circuit needs to be changed.  Remove the external pullup and replace the pulldown with a 1uF or 2uF capacitor, the hub will not work reliably with the current circuit.

    Regards,

    JMMN

  • In reply to JMMN:

    Hi JMMN!

    Thank you very much!  I find your reply very helpful. really appreciate it.

    actually, I've got a I2C EPPROM connected to the hub like below.

    in this case, so should I remove the EPPROM? or just leave it? 

    and is it ok the programming utility does not find the hub connected? I understand it is unnecessary to use the utility. 

    I just worried that something is not right. just wand to make sure. 

    Best,

    WOOJUN

  • In reply to WOOJUN LEE:

    Hello Woojun,

    If you have a blank EEPROM connected to the hub, it should go into programming mode by default.  SMBUSz is floating or pulled high, correct?

    Can you screenshot your Device Manager USB section or install usbview.exe or USB Device Tree Viewer and send a screen shot of what is reported?

    Thanks,

    JMMN

  • In reply to JMMN:

    Hi ZMMN

    Yes, EPPROM is connected to hub and SMBUSz is floating now. I will try to have it pulled high soon by adding 10k resistor on DNP.

    At the moment, I can not see the hub in Device Manager USB section. it is not recognised.

    Do you think that the hub is going to be recognised when SMBUSz is pulled high?

    Best,

    WOOJUN

  • In reply to WOOJUN LEE:

    Hello Woojun,

    SMBUSz float should be ok, can you confirm that USB_VBUS input to the hub is high?

    Can you share the schematic between the hub and the upstream port?

    Also, please confirm you have updated the GRSTz circuit.

    Regards,

    JMMN

  • In reply to JMMN:

    Hi ZMMN!

    Here is the schematic, which is basically almost identical to TIDA-03027.

    Upstream port & TUSB8041

    1.Yes USB_VBUS is high. but, 90.9k resistor is replaced with 91k resistor.

    2. GRST still has external pullup. I will update as you suggest. this might be the reason that the hub is not recognised?

  • In reply to WOOJUN LEE:

    Hi Woojun,

    Pleaser remove the pullup on GRSTz and replace the pulldown with 1 uF capacitor

    I see a couple of issues on the Type-C port connections:

    Usually both USB 2.0 pin sets are shorted together on the Type C port ( pin A6 to B6, pin A7 to B7) so that when the connector is flipped is still works at USB 2.0 speeds.

    Also, you have the SSTX pins connect to the SSRX signals.  SSTX pins should be connected to SSTX signals (and SSRX pins to SS RX signals).

    Regards,

    JMMN