We made a custom carrier board based off of the Mallow eval board. The USB hub doesn’t seem to be working. In the USB5744T datasheet to mentions “Microchip provides a comprehensive software programming tool, Pro-Touch, for configuring the USB5744 functions” does this HUb need to be programmed before it can work? Does Toradex configure this hub on it’s eval boards?
Also the says the i2c address is 0x2D, but that address does not show up on any i2cdetects I’ve done…even on the Mallow Board. Is this the right address?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, I don’t have specific information about whether the USB5744T hub needs to be programmed before it can work or if Toradex configures this hub on its evaluation boards. However, typically, USB hubs like the USB5744T may require configuration to enable certain features or to set specific parameters, which could be done using tools like Microchip’s Pro-Touch.
Regarding the I2C address, if the datasheet specifies 0x2D as the address but it does not show up in your i2cdetect scans, there could be several reasons for this:
The hub might not be powered or connected correctly.
The I2C bus might not be initialized or configured properly.
There could be a mismatch in the I2C address due to different configurations or versions.
I recommend checking the hardware connections and ensuring that the I2C bus is correctly set up. If the issue persists, consulting the USB5744T datasheet for any additional configuration steps or reaching out to Toradex technical support for assistance might be necessary.
Please, also check if these links can help you solve your problem:
Assuming that no special configurations have to be done, what kinds of things could make the hub not be recognized. I copied the Mallow USB Hub schematic, the USB are routed in differential pairs. I got 200K going to ground for the shared pads (see mallow schematic), power voltages are good, reset is 3.3v, VBUS det is 3.3v. All the USB line are correct (P goes to P, N goes to N ). R180 and R181 are no pop, so no I2C is going to the Hub Chip. Nothing downstream is connected.
I just can’t figure out why the OS won’t recognize it.
We have the USB5742BT integrated on our custom carrier board. No I2C communication or configuration on the IC side is required. The upstream port of the IC is directly connected to the SOM’s USB including superspeed pins, functioning seamlessly as a USB 3.0 hub.
If everything on your carrier board is done correctly, the hub should work out of the box. If you have a Mallow board, you can insert the module there and check if the hub on the Mallow board works as expected to verify that there is no issue with the flashed software.
The only clue that I have is pin 40 is connected to GND with a 200k resistor. On the Mallow board this read as 0v, but on my custom board it’s read as 3.3v It’s that way on multiple of my custom board, so I think I cam rule out a chip damaged issue.
good to know it should work with defaults it has on the chip.
Trying to see if the osc is working too, but All I get is noise on both my board and the Mallow, kinda hard to verify.
I did manage to measure the crystal. It doesn’t look like it’s started oscillating. I’m pretty certain this is the reason. I’ll make an update once I change out the load caps.
