[SOLVED] UHCI Error: PORTSC LINE STATUS

[osdnlo]

Err.. we were talking about Full-Speed. This thread is getting jacked.

[eddyb]

Err.. we were talking about Full-Speed. This thread is getting jacked.

Were/should not. As in you should consider that his pen drive is High-Speed and not Full-Speed(if it's relatively new). Which means BIOS will use it via EHCI(otherwise it wouldn't be there a semaphore for BIOS handoff). And if the BIOS uses the EHCI(not necessary a specific device), it *will have to* set the Configure Flag bit, so the High-Speed devices get owned by EHCI. Once it's owned by EHCI, you have to do the reverse procedure. Hope you understand it now.

[prajwal]

I went through the EHCI document. Figured out how to check and perform handoff. I am now able to do handoff of (CF Bit Handoff) where in all EHCI ports are now connected to UHCI controller. P.S. Thanks Eddyb

Now I see a device attached on my 2nd UHCI controlller PORTSC + 0. But my first GetDeviceDescriptor SETUP packet stalled.

Stall bit is set, error counter is decremented to 0 and Timeout error bit is set

Any idea why the pendrive device is in stalled state. What should UHCI host controller driver do to get the device working ??

Thanks,
- MosMan

[eddyb]

I went through the EHCI document. Figured out how to check and perform handoff. I am now able to do handoff of (CF Bit Handoff) where in all EHCI ports are now connected to UHCI controller. P.S. Thanks Eddyb

Now I see a device attached on my 2nd UHCI controlller PORTSC + 0. But my first GetDeviceDescriptor SETUP packet stalled.

Stall bit is set, error counter is decremented to 0 and Timeout error bit is set

Any idea why the pendrive device is in stalled state. What should UHCI host controller driver do to get the device working ??

Thanks,
- MosMan

You're welcome . (Btw, the handoff is in extended capabilities and it's *BIOS* handoff, but i think it will still work with CF only, as it does for you)
As for the stalled endpoint, talk to XanClic, he is experiencing stalled endpoints on real hardware, too.

[XanClic]

Yes, you might want to answer to my corresponding topic Disabling EHCI that you have exactly the same problem as I do.

(Maybe it'll be getting more attention by then )

[prajwal]

I have done a clean Bios Handoff to make OS has the EHCI owner. Then I clear the CF Bit causing all ports to route to companion UHCI Controlle
I see the device attached to UHCI Controller port but it returns STALL handshake for the very first SETUP packet.

The blue tooth (which is not a high speed device) attached to UHCI Controller port enumerates fine. I mean, the I can successfully read all device details (Device Desc, COnfiguration, Interface and End point details and all string descs). The problem lies with the pen drive which is a High Speed device.

So, is it like the High speed usb pen drive (which I am using) does not support operation as Full-Speed device ?

Has anyone got a High Speed Device working on UHCI controller ?

Thanks,
- MosMan

[XanClic]

I have exactly the same problem as you do.

So, is it like the High speed usb pen drive (which I am using) does not support operation as Full-Speed device ?

I thought that, too. But fortunately I also own a full speed hub, thus I can test the full speed operation of high speed devices when they never were connected to a high speed port. And my results are clear: The high speed devices don't work on root ports, but behind a full speed hub. Thus, it's not the device's fault, because it obviously supports full speed operation.

[prajwal]

It's been very late reply to this thread. But it's been few months that I wrote a EHCI controller driver and a mass storage device driver (SCSI protocol).. yes now I am able to detect pen driver and use it.

Thanks for all your help.

Wish you all a very happy new year
- MosMan