Re: USB Hub

Hi,

Glad to hear you solved your problem.

You say your Hub has a USBHPWR and USBPEN pin. I think you mean the PXA 270.

It could be possible that the state of the USBHPWR line is reflected in one
of the USB registers. In that case, it could be possible that the OHCI
driver needs a small adaption to ignore this state change. This is purely a
speculation from my site. You say you disabled the overcurrent protection.
How did you do that?

regards,

Luc

"Jeyanthi Jayakumar" <JeyanthiJayakumar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:77159B31-51F5-4A66-AB3C-6AD9FC72C8FC@xxxxxxxxxxxxxxxx
Hi Cool,
My USB Hub is working fine . But i have a problem in that. The Hub has two
pins USBHPWR and USBPEN for its power switching. I don't want to use those
for its operation so i tried to change the alternate function.USBPEN, i
have
changed to Alternate function 1 and it is working. I want USBPWR pin (GPIO
88) as an GPIO for my application. If i change the Alternate function as
0(actually 1), the Hub itself not working and no power.

Is there any connection with this pin and any other thing. Even i have
disabled the Overcurrent protection. Even then it is not working. If i
disable the overcurrent protection and make the pin for ALT Function 1
then
it is working. Since In my system i am using it as input to PXA for some
other requirement. I want to change that pin function.

Kindly help me. Thanks in Advance.


"Luc Cool" wrote:

Hi,

I just wonder how you use it as USB 2.0 compatible? I just had a quick
look
at the data sheets, and I thought it was a USB 1.1 compatible device.

Normally, a USB device identifies itself with a 3 word number. Hub
devices
have a unique combination of these numbers, identifiing themself as hub
device. So, if your chip comes up as a unidentified USB device,
something is
wrong. If CE sees a unidentified USB device, it will come up with a
window
asking for the driver to install for it. In your case, this might happen
before your gwes is initialised so that you don't see it on your device.
It
could be helpfull if you could reset the hub chip alone and observe what
happens afterwards, in debug information and on the screen.

regards.



"Jeyanthi Jayakumar" <JeyanthiJayakumar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:7853E72E-A599-452B-B7B3-39667004827F@xxxxxxxxxxxxxxxx
I have tried the USB hub directly to the USB port instead of Mouse.
That
is
also working but the thing is first i have connected USB2.0 compatible
Hub
it
was not recognising. And after that tested with 1.1 compatible Hub and
it
was
recognised and i even connected mouse to that Hub and worked,
everything
is
fine.

And we use the chip compatible to USB2.0 in our H/W. That side also we
need
to analyse.

"Luc Cool" wrote:

Hi,

Do you see any debug messages during the startup of the OS? If you
see
no
debug output at all, you should verify the following things:

Under platform, settings, build options, make sure that "Enable ship
build"
(WINCESHIP=1) is unmarked.

Search for the functions OEMWriteDebugByte and OEMInitDebugSerial.
and
make
sure that these contain the code needed to send the bytes to a
serial
port
on your platform. Also make sure that the windows CE driver for that
port is
not loaded so that it's resources are available for the debug output
and
both doesn't conflict.

If you only have no debug output from your USB driver, you should
search
in
the sources of that driver for:

the "DBGPARAM dpCurSettings= ...." There you can change the
different
zones
that show debug output. You might turn them all on in the beginning.

Suspend should indeed go high during normal operation of the hub
chip.
Are
you sure the EXTMEM line has the right level, and the oscillator is
running
as expected?

The USBPWR and overcurrent signals are not needed to test the hub.
There
purpose is mainly to protect the supply against excessive power
consuming
USB devices. Sometimes, protection is simply done with electronic
(selfreparing)fuses. It all depends of price and expected robustness
of
the
final design.

The hub routines are implemented in the USB host driver. So, if you
have
that one running (And since your mouse is working if you connect it
directly, I assume you have), your platform should see the hub as
well,
without the need to add additional catalog items.

Another test you could try, is connecting a external hub to your
platform.
That way, you can see if your USB host driver is working fine and
can
work
together with a hub. If you get that working, you can concentrate
the
debugging on the hub chip and it's surrounding circuits. You didn't
accidentaly changed the D+ and D- line in the up or downstream
ports?

I know, it can sometimes be hard to convince your chief that a 20
dollar
hub
can save you a lot of debugging time.

regards,

Luc


"Jeyanthi Jayakumar" <JeyanthiJayakumar@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in
message news:D325A73E-7DF4-4DB4-9B8A-D99A36B44462@xxxxxxxxxxxxxxxx
U r right. We are working on new H/W platform. And i have tried
with
debug
build and when i connected mouse to the Hub no messages are
coming.Is
there
any other things that has to be done to see the debug messages?

And i have tested the signals in my Hub Chip. The Poweron signals
to
downstream ports are high(3.3V) and suspens is always Low.
Actually if
the
hub works properly, suspend pin should go High after some time if
no
action
in the port Right?

And also i doubt in the image what are drivers that has to be
added
and
not
to be added for the Hub?And thanks for ur suggestion to test the
chip
seperately. I shall try that also.

And do we really need the USBPWR and Overcurrent signals PXA for
this
Hub
to
work. Because these above mentioned functions will be performed by
Hub
itself
then why we need that one?

thanks and Regards
Jeyanthi.

"Luc Cool" wrote:

Hi,

you really should try to get the debug output. If you do a debug
build,
you
should see some messages the moment you connect your mouse to
the
hub.
You
should see the hub connecting as well during the OS startup.

I suppose it could be a hardware issue. Correct me if I am wrong
and
if
you
are not working on a new hardware design.

One thing you might try is isolating the upstream port data
lines of
the
chip and connecting them to a pc USB port (together with the
gnd) if
the
hub
chip is working correctly, you will find a "USB Root Hub" in the
"Device
Manager" under "Universal Serial Bus controllers" You only need
a
usb
cable,
good soldering experience and some patience to do this. This
way,
you
can
test the mouse as well on the pc.
Resetting the hub chip alone for a few seconds, and observing
the
debug
output afterwards, could be interesting as well. It depends on
the
reset
circuit if this is possible.

regards,

Luc


"Jeyanthi Jayakumar"
<JeyanthiJayakumar@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in
message
news:CEDC61D1-EC66-4871-98DB-7D6713C51F6F@xxxxxxxxxxxxxxxx
Hi,
Thanks Cool. But the thing is we have the Hub Chip in built in
our
H/W
board
and it is very difficult to remove that. So we are tryng with
the
same
chip
and oreover The mouse is geeting power but not working.
We don't know what to do?

"Luc Cool" wrote:

Hi,

you might check the supply voltage at the output of the hub.
It
might be
below 5V and to low for proper operation of the mouse. You
might
check
the
debug output of your OS when you connect the mouse to the
hub
and
when
you
connect the mouse directly to the platform. I am not aware
of
any
special OS
settings for the use of a USB hub. You might try a different
brand
of
hub as
well, preferrable a external powered hub, to see if the
problem
is
not
related to the hub. A couple of years ago, I did some tests
and
had
one
hub
working perfect while another refused to cooperate.

hope this helps.

regards,

Luc

"Jeyanthi Jayakumar" <Jeyanthi
Jayakumar@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in
message
news:3F5522A8-98F8-4A52-8359-B9CD7B3984EC@xxxxxxxxxxxxxxxx
Hi,

We have USB Hub TUSB2046 Chip connected to PXA270 and we
have
taken
out 4
ports for accessing. I have included the OHCI and USB HID
driver
for
mouse
to
the image and downloaded the image. But we are not able to
access
the
Hub
using mouse. Mouse is getting power but it is not
accessible.

With the same Image, we have connected the mouse directly
to
one
of
the
USB
port of PXA(bypassing Hub) and we are able to access mouse
and
a
Hub
of
1.1
compatibility.

Kindly suggest me if any settings to be done in the Image
for
the
Hub
Chip
or any drivers to be loaded specially for the Hub Chip.

And also pls suggest me any Hardware related issues.
Thanks in advance.














.