[maemo-developers] Unable to get device detected with usb host mode on N800

[From: Vasudevan Srinivasan]

Hi,

I'm facing an interesting condition. I got my setup working again without
need for any modification on the kernel. I am attaching the logs of both
working and non working condition.
I could not get enough time to check without musb DMA support in kernel,
will try that by Monday.

Everything works fine without errors only when the N800 charger is plugged
in. I get babble errors without that.  This sounds crazy, as we cannot
expect to have the n800 powered whenever we want the usb-host mode.

I'm not sure if this is common or only particular to my device. Is there any
option?


regards,
Vasudevan

On 5/24/07, Tony Lindgren <tony at atomide.com> wrote:
>
> Hi,
>
> * Vasudevan Srinivasan <vazudevan at gmail.com> [070524 08:47]:
> > Hi,
> >
> > The host side drivers were compiled in, CONFIG_USB_OTG_WHITELIST was set
> > off.
> > I could not get things up with the hub, so this time I cooked up a Y
> > connector
> > with external power source(a usb port from desktop without d+ and d-),
> > connected n800 and flash disk to other ends.
> >
> > I was able to get the flash disk working only for a while, after a
> shutdown
> > and start of n800
> > it stopped working with the following errors in dmesg.
> > Have i messed up with something? Any clues / pointers?
> >
> > <dmesg>
> > [  174.530487] musb_stage0_irq 528: CONNECT (a_host) devctl 5d
> > [  174.530578] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
> > [  174.530670] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
> > [  174.681610] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms
> > status 0x101
> > [  174.807830] usb 1-1: new high speed USB device using musb_hdrc and
> > address 2
> > [  175.807800] usb 1-1: khubd timed out on ep0in len=0/64
> > [  176.807800] usb 1-1: khubd timed out on ep0in len=0/64
> > [  177.807281] usb 1-1: khubd timed out on ep0in len=0/64
> > [  177.932800] usb 1-1: device descriptor read/64, error -110
> > [  182.815063] Unhandled trap: 0x18000010
> > [  183.041229] usb 1-1: khubd timed out on ep0in len=0/64
> > [  188.042236] usb 1-1: khubd timed out on ep0in len=0/64
> > [  193.042297] usb 1-1: khubd timed out on ep0in len=0/64
> > [  193.167144] usb 1-1: device descriptor read/64, error -110
> > [  193.401550] usb 1-1: new high speed USB device using musb_hdrc and
> > address 3
> > [  194.401519] usb 1-1: khubd timed out on ep0in len=0/64
> > [  195.401580] usb 1-1: khubd timed out on ep0in len=0/64
> > [  196.401550] usb 1-1: khubd timed out on ep0in len=0/64
> > [  196.526519] usb 1-1: device descriptor read/64, error -110
> > [  201.635925] usb 1-1: khubd timed out on ep0in len=0/64
> > [  206.634796] usb 1-1: khubd timed out on ep0in len=0/64
> > [  211.635955] usb 1-1: khubd timed out on ep0in len=0/64
> > [  211.760955] usb 1-1: device descriptor read/64, error -110
> > [  211.995300] usb 1-1: new high speed USB device using musb_hdrc and
> > address 4
> > [  217.970916] musb_h_tx_flush_fifo 126: Could not flush host TX fifo:
> csr:
> > 000a
> > [  217.971984] usb 1-1: khubd timed out on ep0out len=0/0
> > [  224.158416] musb_h_tx_flush_fifo 126: Could not flush host TX fifo:
> csr:
> > 000a
> > [  224.159545] usb 1-1: khubd timed out on ep0out len=0/0
> > [  224.370269] usb 1-1: device not accepting address 4, error -110
> > [  224.495300] usb 1-1: new high speed USB device using musb_hdrc and
> > address 5
> > [  230.470764] musb_h_tx_flush_fifo 126: Could not flush host TX fifo:
> csr:
> > 000a
> > [  230.471771] usb 1-1: khubd timed out on ep0out len=0/0
> > [  236.658264] musb_h_tx_flush_fifo 126: Could not flush host TX fifo:
> csr:
> > 000a
> > [  236.659729] usb 1-1: khubd timed out on ep0out len=0/0
> > [  236.870330] usb 1-1: device not accepting address 5, error -110
> > [  236.870452] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
> > [  236.870513] hub 1-0:1.0: port 1 enable change, status 00000501
> > [  355.409515] musb_stage0_irq 543: Stopping host session because of
> babble
> > [  367.182983] Unhandled trap: 0x18000010
> > </dmesg>
>
> Interesting, I've never seen this error. I'm suspecting there are some
> alignment issues going on which then cause USB babble errors.
>
> Could you please increase the musb driver debug level by doing:
>
> # echo 8 > /proc/sysrq-trigger
> # echo D3 > /proc/driver/musb_hdrc
>
> And then post the dmesg after plugging in your device.
>
> After that you may want to try to recompile the kernel and leave out
> musb DMA support by setting CONFIG_USB_INVENTRA_FIFO in .config. If that
> works let me know.
>
> Also please post info on the device you're connecting to the USB port,
> such as device model and maybe the relevant part of lsusb -v on your
> Linux PC.
>
> Regards,
>
> Tony
>



-- 
regards
Vasudevan Srinivasan


/* Linux: Because rebooting is for adding new hardware. */
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20070526/efbd9e95/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg n800 on battery.log
Type: application/octet-stream
Size: 15219 bytes
Desc: not available
Url : http://lists.maemo.org/pipermail/maemo-developers/attachments/20070526/efbd9e95/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg n800 on charger.log
Type: application/octet-stream
Size: 8756 bytes
Desc: not available
Url : http://lists.maemo.org/pipermail/maemo-developers/attachments/20070526/efbd9e95/attachment-0001.obj