Hi Sam,
Thanks for your advice. However, I was looking for a mechanism to transfer custom data at the USBDevice level itself. By incorporating the USBHID class, I am going out of scope of USBMSD.
I am trying to make a custom USBMSD implementation that will have a capability to exchange some user defined strings. So, it would be nice to encapsulate that within the USBMSD or its parent classes, right ? I mean that makes the design clean.
No doubt, using the USBHID class seems like a workable solution, but my first priority would be to get everything done within the domain of USBMSD. What do you say ?
Thanks as always,
Seemanta
Greetings MBED hackers,
I am sorry, I could not come up with a title that could convey exactly what I want. But roughly what I am trying to do:
I am using the USBMSD interface to use my MBED as a USBDevice and provide access to an SD card as a USB mass storage device. (the code I have used is here: http://mbed.org/handbook/USBMSD).
But now I want to exchange some custom out-of-band information with the host side through the USB interface. But I am not sure where that code should go in the MBED side for that. Of course, this will require some changes on the driver on the host side. But I would like to first figure it out on the MBED side and from then go on to the host driver side. I don't have much knowledge of the USB protocol so any ideas/pointers would be welcome.
Seemanta