I'm trying to program a UHCI, I managed for the moment to send the change of address command and it works
I try to send a request to read the main descriptor, the function is sent without problems but impossible to send a function IN the transfer descriptor is marked STALL as soon as I activate it

when I make an IN of 8 byte on the endpoint 0 I have 18800000h on the "TD control and status dword" and 00E00069h on the "TD token" and the controller immediately passes the "TD control and status dword" has the value 184007FFh

and I do not understand what's wrong, I fill the td pretty much in the same way the td for a SETUP (except the PID course) and it works

edit: the setup data i send just before is 80h,06h,01h,00h,00h,00h,14h,00h

I don't know if this is your problem but I'm going to say it just in case.....

there is a "Chicken-or-the-egg" problem with USB. you need to know the Max Packet Size of the DEVICE before you issue any packets to/from the device. the problem is that the Max Packet Size is a field in the Device Descriptor that you need to issue packets to get. hence the chicken/egg.

the Max Packet Size field is in the 7th byte of the Device Descriptor: send a request for the first 8bytes of the Device Descriptor and validate the Transfer Length received in the UHCI data structure to ensure 8 bytes were read before any potential error (an error wont necessarily occur). then use the Max Packet Size field to read in the full descriptor.

Stefan

i try to do a read of only 8 bytes of descriptor but it doesnt work
i test different usb device and all doesnt work and one devide doesnt accept my setup frame, so i have a doubt whit the format of the setup frame and i test to reverse the wLength in MSB first format but it doesnt work too

do you think the setup frame i use is good?

If you are trying to do something similar to:

Here is your error, because x86 cannot read/write 8 Bytes at time, the maximum is 4 Bytes.

read data from usb device is diffrent than reading I/O port, its more complex

ROTFLMAO

I use an expression of identifiers for my SETUP packet so I wouldn't recognize the 8 byte numeric string offhand.

I suggest creating identifiers for each option instead of using literal numbers. it serves to expose bugs that are very difficult to see when reduced to numbers.

edit: I just looked at my early device descriptor retrieval code and it's a combination of identifiers and literals... oops.

in my code i use this:

mov byte[usb_commande],10000000b ;bmRequestType
mov byte[usb_commande+1],6 ;bRequest (ici get descriptor)
mov byte[usb_commande+2],1 ;LSB wValue (type)
mov byte[usb_commande+3],0 ;MSB wValue (index)
mov word[usb_commande+4],0 ;wIndex
mov word[usb_commande+6],18 ;wLength

i have a doubt about the word of the structure's command, in assembly we use LSB first but it seem to be a MSB first in the setup structure

usb.wValue.DEVICE = 1
usb.bRequest.GET_DESCRIPTOR = 6 shl 8

you've got the wValue backwards

LOL. my code doesn't properly express what that field is... oops..

wValue is being used as a two byte field. one byte is the Descriptor Type and the other is the Descriptor Index.