Hello! I am new to this group and hope you can help me out.
I am on an embedded board with an ARM cortex a5 and using gadgetfs.
An Application that is derived from the usb.c example is running on it while
the board is connected to a PC with the USB 2.0 Command Verifier.
I am quite new to development with usb. When I run all the Chapter 9 tests,
the
"Device Descriptor Test - Configured State" and the
"Device Descriptor Test - Addressed State" are passed while the
"Interface Association Descriptor Test" and all the following tests fail.
I found out that in "Interface Association Descriptor Test" the open() of the
endpoint fails as well as the read() of the filedescriptor after handling the
"USB_REQ_SET_CONFIGURATION" in this line:
/* ... ack (a write would stall) */
status = read (fd, &status, 0);
if (status)
perror ("\t\tack SET_CONFIGURATION");
return;
The print out of the error message is "Identifier removed".
I noticed that when I leave out all the "Adressed state" Tests, my Tests would
all pass.
As I mentioned, I'm new to USB developing and maybe there's no way to achieve
Chapter 9 conformity with GadgetFS or there's a known bug?
Thanks for any additional info!
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
