I used the SampleUSBMIDIDriver sample code to produce a driver and
everything worked fine (first time !)
There has been an upgrade in the device's hardware/firmware, and now
the USBDevice::OpenAndConfigure fails because the call to
SetConfiguration returns "device not responding".
This happens when the device is connected to the Mac's USB port, then
switched on. If the device is battery-powered, switched on, then
plugged in, everything works because the device is fully initialised.
My question: Is there anything I can do to work around the problem or
do I tell the manufacturer that it's really their fault and that the
device *must* respond to SetConfiguration calls immediately after
USBDeviceOpen, even when it's just been switched on ?
(I tried adding a call to usleep between USBDeviceOpen and
SetConfiguration but this didn't seem to help)