Has anyone had issues with the BB while using it as a Mass Storage
device with the gadget g_file_storage module. I have been looking into
an issue I am having.
The issue is simple, it takes a long time for Windows Vista 32 or
Windows 7 64/32 to recognize the device as a mass storage device (as
much as 5 mins). What I observed form a console on the BB were
messages of the form
[ 37.305114] g_file_storage gadget: high speed config #1
This type of message is repeated as many as 7 times before the device
shows up in the Windows system. I then inserted a Beagle USB 480
device between the BB and the Windows machine to watch the messaging.
I can make a copy of this available for anyone wanting to take a look.
However, what I see is the following:
1. The bus is reset over and over
2. You see the expected protocol exchange for Configuration Descriptor
and String Descriptor
3. The above is followed by a Get Max LUN (knows it is a mass storage
device)
4. Then 2 Inquiry exchanges
5. This is followed by a walk off the map. Exchanges then start for a
device endpoint pair which were not negotiated. In the example I am
looking at the exchange was negotiated for device 2, ep 0 & 1 then the
messages appear for device 1, ep 1.
I the sample I have (win7 64) the system never recognizes the device.
Any thoughts on what may be causing this issue or where to begin in
the driver to fix this?
TIA