Hi Greg and all, I am currently at the last stage of USB Host driver (currently using HID KBD for test) development. If any of you have developed this kind of Host driver/ ported - please let me know, your suggestions/ comments/ observations. It would help me a lot.
Currently I am done with the basic driver of USB Host. As soon as the device is connected, connect event triggers and enumerates the device. This completes getting all the details from device (mainly this is done in usbhost_enumerate.c). I can see all the data going from device and finally host also sets the configuration of the device. Which seems to be last stage of the enumeration. Also if I list the folder under /dev, I see kbda and assume enumeration is successful. nsh> ls /dev /dev: console *kbda* null ttyS2 ttyS8 After this, I don't see any thing from upper layer - so no activity happens on the bus. At this point (after enumeration is done), what is the next step? Who should start request to read the device (as the device is HID KBD, which is already identified during enumeration). Also I tried the Hidkbd example and I see the same behavior, as above. Any of your comments/ suggestions/ observations on what is the next step after enumeration - it would be really helps me a lot. Thanks in advance and With best regards, Phani. >
