search

uchan-nos / mikanos-build

Build and run scripts for MikanOS
Apache License 2.0
302 stars 79 forks source link

How to used intel USB 3.0 xhci ? #30

Open duicleme opened 2 years ago

duicleme commented 2 years ago

I has a NUC that the mini pc. It has intel usb 3.0 . I am try to build mikan os. but not used usb . help me please.

day6 , 7 and after .

duicleme commented 2 years ago

I am see the usbviewer.. ... .. Day06c , How to Edit I am ?

[Port2] : USB Composite Device

Is Port User Connectable: yes Is Port Debug Capable: no Companion Port Number: 2 Companion Hub Symbolic Link Name: USB#VID_2109&PID_0813#5&232e2f59&0&13#{f18a0e88-c30c-11d0-8815-00a0c906bed8} Protocols Supported: USB 1.1: yes USB 2.0: yes USB 3.0: no

Device Power State: PowerDeviceD0

   ---===>Device Information<===---

English product name: "USB Gaming Mouse"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Full (is not SuperSpeed or higher capable) Device Address: 0x05 Open Pipes: 4

      ===>Device Descriptor<===

bLength: 0x12 bDescriptorType: 0x01 bcdUSB: 0x0200 bDeviceClass: 0x00 -> This is an Interface Class Defined Device bDeviceSubClass: 0x00 bDeviceProtocol: 0x00 bMaxPacketSize0: 0x08 = (8) Bytes idVendor: 0x1017 = SPEEDY INDUSTRIAL SUPPLIES PTE. LTD. idProduct: 0x8003 bcdDevice: 0x0133 iManufacturer: 0x01 English (United States) "E-Signal" iProduct: 0x02 English (United States) "USB Gaming Mouse" iSerialNumber: 0x00 bNumConfigurations: 0x01

      ---===>Open Pipes<===---

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0008 = 0x08 bytes bInterval: 0x01

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x82 -> Direction: IN - EndpointID: 2 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0010 = 0x10 bytes bInterval: 0x02

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0020 = 0x20 bytes bInterval: 0x04

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x04 -> Direction: OUT - EndpointID: 4 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0020 = 0x20 bytes bInterval: 0x04

   ---===>Full Configuration Descriptor<===---

      ===>Configuration Descriptor<===

bLength: 0x09 bDescriptorType: 0x02 wTotalLength: 0x005B -> Validated bNumInterfaces: 0x03 bConfigurationValue: 0x01 iConfiguration: 0x00 bmAttributes: 0xA0 -> Bus Powered -> Remote Wakeup MaxPower: 0x32 = 100 mA

      ===>Interface Descriptor<===

bLength: 0x09 bDescriptorType: 0x04 bInterfaceNumber: 0x00 bAlternateSetting: 0x00 bNumEndpoints: 0x01 bInterfaceClass: 0x03 -> HID Interface Class bInterfaceSubClass: 0x01 bInterfaceProtocol: 0x02 iInterface: 0x00

      ===>HID Descriptor<===

bLength: 0x09 bDescriptorType: 0x21 bcdHID: 0x0110 bCountryCode: 0x00 bNumDescriptors: 0x01 bDescriptorType: 0x22 (Report Descriptor) wDescriptorLength: 0x0047

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0008 = 0x08 bytes bInterval: 0x01

      ===>Interface Descriptor<===

bLength: 0x09 bDescriptorType: 0x04 bInterfaceNumber: 0x01 bAlternateSetting: 0x00 bNumEndpoints: 0x01 bInterfaceClass: 0x03 -> HID Interface Class bInterfaceSubClass: 0x00 bInterfaceProtocol: 0x00 iInterface: 0x00

      ===>HID Descriptor<===

bLength: 0x09 bDescriptorType: 0x21 bcdHID: 0x0110 bCountryCode: 0x00 bNumDescriptors: 0x01 bDescriptorType: 0x22 (Report Descriptor) wDescriptorLength: 0x0075

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x82 -> Direction: IN - EndpointID: 2 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0010 = 0x10 bytes bInterval: 0x02

      ===>Interface Descriptor<===

bLength: 0x09 bDescriptorType: 0x04 bInterfaceNumber: 0x02 bAlternateSetting: 0x00 bNumEndpoints: 0x02 bInterfaceClass: 0x03 -> HID Interface Class bInterfaceSubClass: 0x00 bInterfaceProtocol: 0x00 iInterface: 0x00

      ===>HID Descriptor<===

bLength: 0x09 bDescriptorType: 0x21 bcdHID: 0x0110 bCountryCode: 0x00 bNumDescriptors: 0x01 bDescriptorType: 0x22 (Report Descriptor) wDescriptorLength: 0x0020

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x83 -> Direction: IN - EndpointID: 3 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0020 = 0x20 bytes bInterval: 0x04

      ===>Endpoint Descriptor<===

bLength: 0x07 bDescriptorType: 0x05 bEndpointAddress: 0x04 -> Direction: OUT - EndpointID: 4 bmAttributes: 0x03 -> Interrupt Transfer Type wMaxPacketSize: 0x0020 = 0x20 bytes bInterval: 0x04

uchan-nos commented 2 years ago

@duicleme

I am try to build mikan os. but not used usb .

Did you have any errors while building MikanOS? Building MikanOS itself doesn't depend on architecture of a target machine.

duicleme commented 2 years ago

@uchan-nos

My system intel NUC .

It's Debug Report . a Error Picture Capture

https://cafe.naver.com/raspberrypis/3376

uchan-nos commented 2 years ago

I couldn't find any picture. Is URL incorrect?

duicleme commented 2 years ago

Sorry for the late mail.

It's because I have a cold.

kota uchida also be careful of summer cold.

Capture the error screen and send it.

I hope you find a good answer by all means .

2022년 8월 11일 (목) 오전 9:13, Kota UCHIDA @.***>님이 작성:

I couldn't find any picture. Is URL incorrect?

— Reply to this email directly, view it on GitHub https://github.com/uchan-nos/mikanos-build/issues/30#issuecomment-1211427531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGPV4KR7SSZLAVHHAFLWSOLVYRASNANCNFSM55UFOWVQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Home Lab 2015, Suwon in Korea (Version POX.3.4)

uchan-nos commented 2 years ago

Please attach the capture image to this issue, not emailing it to me.

duicleme commented 2 years ago

so sorry

attach

https://raspberrypis.tistory.com/7

duicleme commented 2 years ago

.. I am think someone that a pci not found.... the first step faileld so not work on it . I am think.

uchan-nos commented 2 years ago

The last error is "Babble Detected Error" occured on the slot 2. The device connected at the slot may be a hub since its class code is 9.

I don't have any idea why this error occurs. This error is defined in "4.10.2.4 Babble Detected Error", xHCI requirement specification.

duicleme commented 2 years ago

If you look at the USBViewer, it seems to be recognized as USB 2.0. If so, is it not a bubble because it has to be at full speed?

I don't know what to do and how to solve it.

duicleme commented 2 years ago

I checked day06b again. " pci " The number of num_device was 0. Could it be 0?

I wondered if the addresses of config_address and config_data were wrong. ( " 0x0cf8 0x0cfc " wrong ?!?!?!?! ) Wouldn't it be different for each computer? My computer is an intel NUC.

duicleme commented 2 years ago

pci address not found... ^^;;;;;

https://docs.oracle.com/cd/E19683-01/806-5222/6je8fjvhe/index.html

duicleme commented 2 years ago

i am finding a pci device . number 21 .. but ...other error ...

day06b ok...

e~~ next day06c

error picture...here

https://raspberrypis.tistory.com/10

duicleme commented 2 years ago

max 16 port ... but anything port not connected.

picture.

https://raspberrypis.tistory.com/11

uchan-nos commented 2 years ago

If you look at the USBViewer, it seems to be recognized as USB 2.0. If so, is it not a bubble because it has to be at full speed?

Yes, it is a babble detected error. xHCI handles USB 1.1, 2.0, 3.x devices in a unified way.

You can use Wireshark to capture USB packets that may help you debug further. https://wiki.wireshark.org/CaptureSetup/USB

duicleme commented 2 years ago

If you look at the USBViewer, it seems to be recognized as USB 2.0. If so, is it not a bubble because it has to be at full speed?

Yes, it is a babble detected error. xHCI handles USB 1.1, 2.0, 3.x devices in a unified way.

You can use Wireshark to capture USB packets that may help you debug further. https://wiki.wireshark.org/CaptureSetup/USB

Sorry, My system mouse is USB 2.0. I checked with usbview.

I'm wondering if you can cover the mouse and keyboard of USB 2.0. I want to make progress, but my abilities are not enough.

Once we have the driver code, I think we can move on. Ask for help.

Capture But unknown .