USB OTG as host

I want to config the USB OTG of my BB C5 as host permanently. I have 2 USB sticks, let call it A, B.
I tested as follow:

  • A or B plugged in → boot → detected. Unplug A (or B), re-plug in → detect. If plug in the other (ex C) → not detect. Must reboot to be able to detect again.
  • Booted. Plug in A or B → not detect.

The symptom is the same with the case pin 4, 5 of USB OTG are short circuit.

I’m running Oneiric, kernel 3.2.19-x13 if that matter. I greatly appreciate your helps.

In addition, I don’t see this path in my system
/sys/devices/platform/musb_hdrc

I want to config the USB OTG of my BB C5 as host permanently. I have 2 USB
sticks, let call it A, B.
I tested as follow:
- A or B plugged in --> boot --> detected. Unplug A (or B), re-plug in -->
detect. If plug in the other (ex C) --> not detect. Must reboot to be able
to detect again.
- Booted. Plug in A or B --> not detect.

Simple answer, don't do that with the current kernel, it's a known old
musb bug.. Use a hub and ALLWAYS have atleast one device plugged in
the musb port to keep it active.. Then you can easily add/remove any
other devices at will..

The symptom is the same with the case pin 4, 5 of USB OTG are short
circuit.
I'm running Oneiric, kernel 3.2.19-x13 if that matter. I greatly
appreciate your helps.

You can try v3.4.x to see if this is now maybe fixed upstream..

wget http://rcn-ee.net/deb/oneiric-armel/v3.4.4-x1/install-me.sh
/bin/bash install-me.sh

Thanks Robert.

You can try v3.4.x to see if this is now maybe fixed upstream…
This fixed my problem.

One concern is, I need to apply a patch for an LCD panel, so I need the source for kernel 3.4.x. The last updated stable-kernel is 3.2. Where can I get the code for 3.4.x with patches for BB? Testing version is fine with me.

I managed to get the code at

git://github.com/RobertCNelson/linux-dev.git.

Thanks for the great work, Robert.

That repo is not recommended for end users..

Use the v3.4.x branch from:
https://github.com/RobertCNelson/stable-kernel/tree/v3.4.x

As soon as i fix the last panda issue, it's going to be replacing v3.2.x...

Regards,