Hi,
I have a bug that i am trying to fish out and pin point the root cause.
I have a WLAN device connected over USB-OTG that talks to the zedboard. I have a device driver installed on the Zedboard that loads the DUT as a WLAN device and if you type "ifconfig -a" you will see this device listed as "wlan0". If i run my program, which is hardcoded to use resource wlan0, x-number of times, after y-iterations (power cycling on -off- on), my wlan device gets locked in the kernel and wlan0 is stuck, thus not allowing me to reinitialize the device again.
Now, I am trying to determine whether this is a resource issue with my program, a specific kernel config option i compiled in, a jumper setting for USB on my Zed (which is currently JP3 open, JP2 closed), or a hardware limitation of the Zedboard.
From my understanding, USB-OTG needs the jumper settings at JP3 open and JP2 closed in order for the zedboard to act as the "host" and use the connected interface as a "device".
Has anyone ever witnessed this before? Anyone on the Zedboard design team have any hints or direction to choose first in order to troubleshoot this properly?
My kernel is Linux/arm 3.3.0-digilent-12.07-zed-beta.
Any help would be great!
Thanks.
