devu-uhci starts but doesn't communicate

QNX Newsgroups (Archives) qnx.ddk
1

Hi,

There is an output from pci command before the devu-uhci manager start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek

2

What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote in message
news:cv2243$q76$1@inn.qnx.com…

Hi,

There is an output from pci command before the devu-uhci manager start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek

3

I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <henry@qnx.com> napisa³ w wiadomo¶ci
news:cv2au3$34q$1@inn.qnx.com…

What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek
\

4

Is it possible for you to try 6.30 on this board ?

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote in message
news:cv2bmu$3vg$1@inn.qnx.com…

I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2au3$34q$> 1@inn.qnx.com> …
What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek


\

5

We’ve had some troubles like that too. But we have
an “engineering version” of the UHCI driver from May 2003
for QNX 6.21. Is there a later version that will work
on 6.21? (We can’t go to 6.3, because Mindready isn’t
supporting it.)

John Nagle

6

I can’t promise anything about migration to the
QNX 6.3 at the moment Henry.

Is there any other way to resolve that problem?

Regards,
Jacek


U¿ytkownik “Henry VanDyke” <henry@qnx.com> napisa³ w wiadomo¶ci
news:cv2dut$5cl$1@inn.qnx.com…

Is it possible for you to try 6.30 on this board ?

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2bmu$3vg$> 1@inn.qnx.com> …
I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2au3$34q$> 1@inn.qnx.com> …
What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager
start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek




\

7

Hi John,

Does mean that you have modified the devu-uhci
source itself to build “engineering version”?

No luck with the devu-uhci from Patch B
(87716 May 17 2003).

Jacek

Uzytkownik “John Nagle” <nagle@downside.com> napisal w wiadomosci
news:cv2g86$74v$1@inn.qnx.com…

We’ve had some troubles like that too. But we have
an “engineering version” of the UHCI driver from May 2003
for QNX 6.21. Is there a later version that will work
on 6.21? (We can’t go to 6.3, because Mindready isn’t
supporting it.)

John Nagle

8

Jacek Rudnicki wrote:

Hi John,

Does mean that you have modified the devu-uhci
source itself to build “engineering version”?

No, we were “early adopters” and QSSL sent us
a development version after we reported some
bugs. But the final version went into QNX 6.3,
and we were told to upgrade.

“devu-ohci” seems to work better.

John Nagle
Team Overbot

9

Hi Henry,

QNX 6.3 is running very well on my target,
but I still have some problems with USB
interface.

When I try to run io-usb manager:
#io-usb -duhci -vvvvvvvv
then system prints:
Interrupt AttachEvent failed

Here is a part of pci command after driver start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB/MB PIIX4/4E/4M USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
CPU Interrupt = 1fh
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Very interesting is that USB driver doesn’t set:
“I/O space access” field to enabled (Command Reg is = 4h)

Why the “PCI IO Address = ffffffff18000000h” has that
strange value?

Under QNX 6.2.1 the devu-uhci didn’t have such problems:

Command Reg = 5h
I/O space access enabled

PCI IO Address = 3ffff00h length 32 enabled

Do you know what can be wrong?

Regards,
Jacek

U¿ytkownik “Henry VanDyke” <henry@qnx.com> napisa³ w wiadomo¶ci
news:cv2dut$5cl$1@inn.qnx.com…

Is it possible for you to try 6.30 on this board ?

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2bmu$3vg$> 1@inn.qnx.com> …
I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2au3$34q$> 1@inn.qnx.com> …
What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager
start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek




\

10

What board is this ?
can you provide a full pci -vvvv output.
The output matches the 6.2.1 one before running the devu-uhci.
looks like the resources havn’t been set up by pci server.

Henry

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote in message
news:d485p1$oaf$1@inn.qnx.com…

Hi Henry,

QNX 6.3 is running very well on my target,
but I still have some problems with USB
interface.

When I try to run io-usb manager:
#io-usb -duhci -vvvvvvvv
then system prints:
Interrupt AttachEvent failed

Here is a part of pci command after driver start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB/MB PIIX4/4E/4M USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
CPU Interrupt = 1fh
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Very interesting is that USB driver doesn’t set:
“I/O space access” field to enabled (Command Reg is = 4h)

Why the “PCI IO Address = ffffffff18000000h” has that
strange value?

Under QNX 6.2.1 the devu-uhci didn’t have such problems:

Command Reg = 5h
I/O space access enabled

PCI IO Address = 3ffff00h length 32 enabled


Do you know what can be wrong?

Regards,
Jacek

U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2dut$5cl$> 1@inn.qnx.com> …
Is it possible for you to try 6.30 on this board ?

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2bmu$3vg$> 1@inn.qnx.com> …
I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2au3$34q$> 1@inn.qnx.com> …
What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager
start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek






\

11

You were right Henry.
After some pci server modification
the devu-uhci is running very well.

How can I check USB interface
without Photon GUI available?

Jacek


U¿ytkownik “Henry VanDyke” <henry@qnx.com> napisa³ w wiadomo¶ci
news:d4aulv$qsk$1@inn.qnx.com…

What board is this ?
can you provide a full pci -vvvv output.
The output matches the 6.2.1 one before running the devu-uhci.
looks like the resources havn’t been set up by pci server.

Henry

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:d485p1$oaf$> 1@inn.qnx.com> …
Hi Henry,

QNX 6.3 is running very well on my target,
but I still have some problems with USB
interface.

When I try to run io-usb manager:
#io-usb -duhci -vvvvvvvv
then system prints:
Interrupt AttachEvent failed

Here is a part of pci command after driver start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB/MB PIIX4/4E/4M USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
CPU Interrupt = 1fh
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Very interesting is that USB driver doesn’t set:
“I/O space access” field to enabled (Command Reg is = 4h)

Why the “PCI IO Address = ffffffff18000000h” has that
strange value?

Under QNX 6.2.1 the devu-uhci didn’t have such problems:

Command Reg = 5h
I/O space access enabled

PCI IO Address = 3ffff00h length 32 enabled


Do you know what can be wrong?

Regards,
Jacek

U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2dut$5cl$> 1@inn.qnx.com> …
Is it possible for you to try 6.30 on this board ?

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2bmu$3vg$> 1@inn.qnx.com> …
I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2au3$34q$> 1@inn.qnx.com> …
What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager
start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek








\

12

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote in message
news:d4kv9e$97n$1@inn.qnx.com…

You were right Henry.
After some pci server modification
the devu-uhci is running very well.

thats good.

How can I check USB interface
without Photon GUI available?

What do you want to check ?
The usb utility shows you what devices are connected.

Henry

Jacek


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:d4aulv$qsk$> 1@inn.qnx.com> …
What board is this ?
can you provide a full pci -vvvv output.
The output matches the 6.2.1 one before running the devu-uhci.
looks like the resources havn’t been set up by pci server.

Henry

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:d485p1$oaf$> 1@inn.qnx.com> …
Hi Henry,

QNX 6.3 is running very well on my target,
but I still have some problems with USB
interface.

When I try to run io-usb manager:
#io-usb -duhci -vvvvvvvv
then system prints:
Interrupt AttachEvent failed

Here is a part of pci command after driver start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB/MB PIIX4/4E/4M USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
CPU Interrupt = 1fh
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Very interesting is that USB driver doesn’t set:
“I/O space access” field to enabled (Command Reg is = 4h)

Why the “PCI IO Address = ffffffff18000000h” has that
strange value?

Under QNX 6.2.1 the devu-uhci didn’t have such problems:

Command Reg = 5h
I/O space access enabled

PCI IO Address = 3ffff00h length 32 enabled


Do you know what can be wrong?

Regards,
Jacek

U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2dut$5cl$> 1@inn.qnx.com> …
Is it possible for you to try 6.30 on this board ?

Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2bmu$3vg$> 1@inn.qnx.com> …
I’m running QNX 6.2.1B.
There is only one USB controller with two ports.

I forgot to mention my target is ppcbe.


U¿ytkownik “Henry VanDyke” <> henry@qnx.com> > napisa³ w wiadomo¶ci
news:cv2au3$34q$> 1@inn.qnx.com> …
What verion of the OS are you running?
Is there more then 1 USB controller ?


Jacek Rudnicki <> jacek.rudnicki@quantum.com.pl> > wrote in message
news:cv2243$q76$> 1@inn.qnx.com> …
Hi,

There is an output from pci command before the devu-uhci manager
start:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 4h
I/O space access disabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = ffffffff18000000h length 32 disabled
CPU IO Address = 0h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 31
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

Driver starts fine and in result /dev/usb device is created.
Everything looks ok except one thing, the usb command
prints only:

“USB (UHCI) v1.10, v1.01 DDK
Control, Interrupt, Bulk, Isoch, Low speed, High speed”

no any info about connected devices.

Very interesting is that in verbose mode (devu-uhci -vvvvv)
nothing is written into the system log.

When devu-uhci is running the ‘pci’ reports:

Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB PIIX4 USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 6
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 80h
Cache Line Size= 0h
PCI IO Address = 3ffff00h length 32 enabled
CPU IO Address = ebffff00h
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = INT D
Interrupt line = 33
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00

What is wrong?
How can I bring my USB controller back to life?

Regards,
Jacek










\