• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 34 subscribers
  • Views 371 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.

TUSB8044A: TUSB8044A Error Frames to the USB host without connected devices

Bernd Mönnicke
Prodigy 10 points
Part Number: TUSB8044A

Hello,

I have a new product in development and the customer have add the TUSB8044A USB hub to connect more devices on the USB host. On the third device is an STM32F205 with USB ORG FS only device connected. The USB communication between the STM32F205 and the USB host (PC) works without problems. But in the USB upstream I have many error frames with unknown type.

All other 3 downstream USB ports are not connected at the moment.

The error frames comes also when the STM32F205 is hold in power on reset. So I can say that this not come from my software.

How can comes this errors?

What can I do to remove this?

Thanks for Our help,

Bernd

  • 0
    TI__Guru**** 176281 points

    HI, Bernd

    Where did you place the analyzer? Please see this link, https://www.totalphase.com/blog/2019/12/what-causes-split-and-orphaned-packets-and-how-do-i-eliminate-from-a-usb-capture/. I wonder if the issue exists because the analyzer will see all messages sent from the USB host controller, but not able to see the USB device sending the upstream messages.

    Thanks

    David

  • 0 in reply to David (ASIC) Liu
    Prodigy 10 points

    Hi David,

    thanks for the hint. Now I changed my setup. The Beagle USB 480 Analyser is connected to an Ubuntu machine and the USB Device (TUSB8044A host) is connected to an Win7 machine.

    Now I see more failure.

  • 0 in reply to Bernd Mönnicke
    TI__Guru**** 176281 points

    Hi,

    Are you placing the Beagle Analyzer between the Win 7 machine and the upstream port of the hub or between the downstream port of the hub and the STM32F205? The orphaned packet is not a defined USB packet type. The orphaned packet is more related to how the Beagle Analyzer decodes the USB traffic that labels any packet without a response. A hub also retransmits packets destined for itself. the Beagle would still see orphaned packets from the communication between the hub and the host.

    Does the Win 7 machine actually communicate to the STM32F205 through the hub without any issues?

    Thanks

    David

  • 0 in reply to David (ASIC) Liu
    Prodigy 10 points

    Hi,

    the Beagle Analyser is between the upstream port and the Win7 machine. I can't connect it between the STM32F205 and the downstream port of the hub. booth are on the same PCB. An yes, the comminucation between the WIn7 machine and the STM32F205 over USB works without problems.

    The failure messages comes from the hub. I can't hold the STM32F205 in POR and the failure messages also available.

    I've seen that the hardware peaple have equip the I2C EEPROM to the TSUB8044A without programming. Is this a problem for the TUSB8044A?

    Best regards,

    Bernd

  • 0 in reply to Bernd Mönnicke
    TI__Guru*** 144765 points

    If the  EEPROM is blank, the hub will enter a programming mode.

    Regards

    brian 

  • 0 in reply to Brian Zhou
    Prodigy 10 points

    I've read that the hub creates an USB 2.0 device for the EEPROM. Exists a tool to program the EEPROM?

    And can come this error frames from this?

  • 0 in reply to Bernd Mönnicke
    TI__Guru*** 144765 points

    sorry for the delay, if you remove EEPROM, the error still there?

    Regards

    Brian

  • 0 in reply to Brian Zhou
    Prodigy 10 points

    sorry it is not allowed me to change the hardware. and I have not enougth time to send it back to change it by my customer.

    I need a tool for the access to this EEPROM over USB. Exists a tool for this? Or is this only a fake in the documentation and this is not working or available?

    An I think here are experts for the devices and can me answer my questions "And can come this error frames from this?". It's not nice to answer my question by testing it with my customer's hardware.

  • 0 in reply to Bernd Mönnicke
    TI__Guru*** 144765 points

    I sent error message to our system and see what his comment.

    Regards

    Brian

  • 0 in reply to Brian Zhou
    TI__Guru*** 144765 points

    Bernd:

        Sorry for late reply. here is the comment from our designer:

    1: Orphaned isn’t a USB term. as USB 2.0 hosts broadcast all packets,  it could have been addressed to another hub, either above or on a separate tree, and would appear to be orphaned to an analyzer in this path.

     2: Maybe that other hub is embedded in the host.

    3: Customer  can check for broadcast tokens addressed to a device above or outside the tree by looking at the device addresses in the capture. The addresses aren’t shown in the capture as far as I can see.

    4: If the capture is on a DFP of the hub with a HS device connected to it, all of the hub’s transactions would show up on that DFP, but none of the hub’s responses would, since they are sent only to the host.

    Regards

    Brian