Hi,
W dniu 13.05.2019 o 20:09, John Stultz pisze:
On Mon, May 13, 2019 at 7:08 AM Andrzej Pietrasiewicz
<andrzej.p@xxxxxxxxxxxxx> wrote:
<snip>
Do you get "functionfs read size 512 > requested size 24, splitting
request into multiple reads" message when problems happen?
Unfortunately no.
Actually that's a fortunate outcome :)
Is there anything in the kernel log?
Nope. Just the transfers stall/hang and further attempts at adb
connections fail until the USB cable is unplugged and replugged.
<snip>
Is there a way to try your adb without building and running the
whole Android?
Maybe? I have heard of folks doing it in the past, though I don't
really know a quick path to get there.
Is there anything else I can try for you?
Have you tried compiling FunctionFS with debugging enabled?
You do so bu uncommenting:
/* #define DEBUG */
/* #define VERBOSE_DEBUG */
at the beginning of drivers/usb/gadget/function/f_fs.c
Is there anything suspicious in the kernel log when you run it then?
Remote debugging through this mailing list will incur enormous
round trip time ;) The most valuable help would be helping in
reproducing the problem you encounter.
One question that comes to my mind is this: Does the USB transmission
stall (e.g. endpoint stall) or not? In other words, is adb connection
broken because USB stops transmitting anything, or because the
data is transmitted but its integrity is broken during transmission
and that causes adb/adbd confusion which results in stopping their
operation? Does anything keep happening on FunctionFS when adb
connection is broken?
Andrzej
