TUSB2036 is initializing and entering in SUSPEND MODE.

Hello Douglas,

Your RC circuit of R=2,2K and C=0.1uf will give you a reset "window" of about 200us, in order to approach to the 3ms you have to change your R to 22K ohm.

Can you send your schematics for review.

Regards.

Thanks Elias,

To tell you the truth I did the RC externally. In series of Resetout# net.

I send the schematics in your e-mail. But I haven't added the RC. I did it externally.

Best Regards,

Douglas Cogubum

Hello Douglas,

You have to make sure your reset circuit gives a 1ms to 3ms "reset window", this timing begins after the Vcc lines have reached its 90%, also some passive components to the DP0/DM0 lines (22pF caps to gnd). What are you using as your USB host? Are you able to capture some bus traces?

Regards.

Hello Elias,

Sorry for the delay to answer, but Monday and Tuesday was holiday in Brazil.

We're using a mouse and a keyboard usb, both are usb 1.1

I'm not able to capture some bus trace, the clock starts and the chip enters in SUSPEND mode. Then, every signal stops.

Did you see the schematics? Did you found any mistakes there?

Best regard,

Douglas.

Hello Douglas,

Your schematic looks correct, please focus on the be below statements:

Per USB specification any USB device can start to enter SUSPEND after 3ms of bus inactivity but they must be in the suspend state by 10 ms of bus inactivity and only 2.5mA supply current is provided. So, the host can suspend the hub if it sees 3 ms of no bus activity.
If the downstream devices pull more than 500 mA of current, the hub goes in to SUSPEND state since it is violation of USB specs. Also, if the reset timing isn’t accurate or if the host doesn’t load the hub class driver correctly, the hub goes in to SUSPEND state and shows us as an “Unknown device” in device manager.

Regards.

Hello Elias,

We've done some test since yesterday with success.

We connected DP0 and DM0 directly to a computer. So the PC is the upstream.

The OS was Windows 7 and ubuntu and both case the PC recognized the hub and the peripherals. I connected a pen drive(usb 2.0) and a usb mouse(usb 1.1) in the other port.

Both peripherals work fine without any problem.

So, It should be a driver problem. We're trying to find a driver compatible with kernel 2.6.32 or import ubuntu's usb driver to our distribuition(Angstrom).

We really thanks for your help.

Best Regards,

Douglas.

Hello Elias,

One more thing, is there any issue between TUSB2036 and SMSC USB3320?

Because the SMSC USB3320 is the interface between ARM processor and the HUB. And in this case, it doesn't work.

Best Regards,

Douglas.

Hello Elias,

Just another question... Is the upstream port usb 2.0 or usb 1.1?

Best Regards,

Douglas.

Hello,

The TUSB2036 only supports Low speed and Full speed.

Regards.

Hello,

Let me see if I understand, The TUSB2036 supports usb 2.0 and usb 1.1, or only 1.1 with full or low speed?

I understand that upstream port is a usb 1.1 with a low or full speed not a usb 2.0 wich is Hi speed, Am I right?

Thanks,

Douglas.

Douglas,

The USB 2.0 is a specification that defines three different speeds of operation - USB low-speed (1.5 Mbps), USB full-speed (12 Mbps), and USB high-speed (480 Mbps).  The USB 2.0 specification superceded (replaced) the USb 2.2 specification. Low-speed & full-speed are identically to what they were prior to the new spec being released.

To be complaint a peripheral device must support at least one speed.

A hub can be compliant if it only supports LS & FS and is intended for "embedded" applications.
 
The TUSB2036 supports a max data transfer rate of USB full-speed.  High-soeed devices will work, they will just be limited in throughput.

Thanks Dan,

I'll search for how I can configure it as full-speed.

Regards,

Douglas.

The configuration is done by hardware.

If you want the hub to be a full-speed device, you must populate a 1.5K pull up from DP0 to 3.3V

If you want the hub to be a low-speed device, you must populate a 1.5K pull up from DM0 to 3.3V

Regards.