Closed Thread
Thread Tools
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#831
Originally Posted by blue_led View Post
the only one i found is different length of pins inside receptacle ( tolerances or overheat & melted plastic of receptacle body during manufacturing process of adapter )
different connection is made first : ground , vbus and datalines and sometimes something go wrong
Usually GND and +5V should be noticeably longer than data line contacts, so always power and GND make first break last. At least that's the specs.
/j
 

The Following 3 Users Say Thank You to joerg_rw For This Useful Post:
Posts: 306 | Thanked: 566 times | Joined on Jan 2010 @ Romania
#832
if datalines pins on the ends of F-F adapter have different length this can matter when busreset .

On topic:
[joke] why , why .... i'm gonna cry [/joke]
rx51_defconfig
.....
1410 # CONFIG_USB_DEVICE_CLASS is not set

Last edited by blue_led; 2010-05-11 at 22:50.
 

The Following User Says Thank You to blue_led For This Useful Post:
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#833
Originally Posted by blue_led View Post
....
1410 # CONFIG_USB_DEVICE_CLASS is not set
Deprecated, not required AFAIU.

See http://cateee.net/lkddb/web-lkddb/USB_DEVICE_CLASS.html
 

The Following 2 Users Say Thank You to javispedro For This Useful Post:
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#834
Originally Posted by joerg_rw View Post
We really need to check why 'echo host >mode' seems to have no effect - evidence for the missing effect is the usage of the whitelist.
Probably there are parts missing in the source, for handling plain vanilla hostmode.
Isn't that just because of:
Originally Posted by blue_led
and rx51_defconfig
1436 # CONFIG_USB_MUSB_HOST is not set
1437 # CONFIG_USB_MUSB_PERIPHERAL is not set
1438 CONFIG_USB_MUSB_OTG=y
Or is your kernel configured with CONFIG_USB_MUSB_HOST?

(EDIT: Or am I completely wrong and we don't want CONFIG_USB_MUSB_HOST?)
 
Posts: 992 | Thanked: 995 times | Joined on Dec 2009 @ California
#835
@Joerg

Again, good news - I repeated test suggested by you but replaced 'stop bme' to 'killall -SIGSTOP bme_RX-51'.

Originally Posted by joerg_rw View Post
[*]And finally, maybe you can replace the TWL4030 VBUS boostmode call by a call to bq24150 (or a system() call [man 3 system] to invoke my above posted cmdline like
Code:
 /bin/sh -c '/sbin/stop bme && sleep 3 && /usr/local/i2cset -y -m 0x07 2 0x6b 0x01 0x05 && while sleep 28; do /usr/local/i2cset -y -m 0x80 2 0x6b 0x00 0x80; done &'
)
Now it works, even on stock (unmodified) kernel.

However, I doesn't work well with my USB memory stick because read returns error -32 (EPIPE). But it still exchanges some info because device "not accepting address 8" (or ever). A modified kernel is needed to find out details why it reads descriptors with EPIPE.

And it also works only around 30-50secs because DSME reboots N900 due to BME failure.

So, conclusion - BME disables somehow host mechanism then it exits. Probably - to prepare a hardware charging.

EDIT: exact sequence on unmodified kernel:

1. plug to PC, answer "PC suite"
2. echo host >/sys/devices/platform/musb_hdrc/mode
3. echo H >/proc/driver/musb_hdrc
4. /bin/sh -c 'killall -SIGSTOP bme_RX-51 && sleep 3 && /usr/local/i2cset -y -m 0x07 2 0x6b 0x01 0x05 && while sleep 28; do /usr/local/i2cset -y -m 0x80 2 0x6b 0x00 0x80; done &
5. disconnect USB from PC and connect to USB memory stick or extrnal hard disk or HUB.
6. lsusb -- or just wait
7. Look into /var/log/syslog for messages.

(Sometime I add yet another additional steps 2 and 3 after 4).

Last edited by egoshin; 2010-05-12 at 06:25.
 

The Following 10 Users Say Thank You to egoshin For This Useful Post:
Posts: 946 | Thanked: 1,650 times | Joined on Oct 2009 @ Germany
#836
I have build a special version of the power-user kernel with USB debugging and verbose enumeration enabled, and the USB blacklist disabled (w/o whitelist it ended up in a reboot loop).
Modules for all common USB device classes are already included (for USB/IP).
I hope it can help you to get USB hostmode working on the N900.

download and install in this order
http://maemory.com/N900/kernel/testi...mo28_armel.deb
http://maemory.com/N900/kernel/testi...mo28_armel.deb
http://maemory.com/N900/kernel/testi...mo28_armel.deb
the kernel configuration is http://maemory.com/N900/kernel/testi...ower_defconfig

good luck!
 

The Following 3 Users Say Thank You to titan For This Useful Post:
Posts: 155 | Thanked: 61 times | Joined on Nov 2009
#837
Unfortunately... it didnt work - I'll have to think again :O)

~/.bin $ uname -a
Linux Nokia-N900 2.6.28.10powerusb28 #2 PREEMPT Wed May 12 08:03:07 CEST 2010 armv7l unknown

So definately the right kernel. Huge thanks for building it - I'll shout when I work out what module or includes are really needed.

Originally Posted by titan View Post
I have build a special version of the power-user kernel with USB debugging and verbose enumeration enabled, and the USB blacklist disabled (w/o whitelist it ended up in a reboot loop).
Modules for all common USB device classes are already included (for USB/IP).
I hope it can help you to get USB hostmode working on the N900.

download and install in this order
http://maemory.com/N900/kernel/testi...mo28_armel.deb
http://maemory.com/N900/kernel/testi...mo28_armel.deb
http://maemory.com/N900/kernel/testi...mo28_armel.deb
the kernel configuration is http://maemory.com/N900/kernel/testi...ower_defconfig

good luck!

EDIT: Am I a dope or what?

CONFIG_IP_MULTIPLE_TABLES and CONFIG_IP_ROUTE_MULTIPATH << has to be the ones....

Last edited by phedders; 2010-05-12 at 07:18.
 
Posts: 946 | Thanked: 1,650 times | Joined on Oct 2009 @ Germany
#838
note that phedders' comment is about a network function I added as well.
it's not about the USB host mode.

for discussion about the kernel please go to http://talk.maemo.org/showthread.php?t=43420

Originally Posted by phedders View Post
Unfortunately... it didnt work - I'll have to think again :O)
 
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#839
Originally Posted by egoshin View Post
So, conclusion - BME disables somehow host mechanism then it exits. Probably - to prepare a hardware charging.
I think this is the most interesting discovery so far. Now the question is: how? (and of course, what).
Should a strace of bme terminating help?

Last edited by javispedro; 2010-05-12 at 13:58.
 

The Following User Says Thank You to javispedro For This Useful Post:
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#840
Originally Posted by titan View Post
I have build a special version of the power-user kernel with USB debugging and verbose enumeration enabled, and the USB blacklist disabled (w/o whitelist it ended up in a reboot loop).
Modules for all common USB device classes are already included (for USB/IP).
I hope it can help you to get USB hostmode working on the N900.

download and install in this order
http://maemory.com/N900/kernel/testi...mo28_armel.deb
http://maemory.com/N900/kernel/testi...mo28_armel.deb
http://maemory.com/N900/kernel/testi...mo28_armel.deb
the kernel configuration is http://maemory.com/N900/kernel/testi...ower_defconfig

good luck!
Thanks a lot, Titan!
/j
 

The Following User Says Thank You to joerg_rw For This Useful Post:
Closed Thread

Tags
awesomeness in the works, boulevard of broken deals, host, i am the dealbreaker, inspector gadget lies, mobidapter is a scam, nokia fanbois, otg, over 9000, usb, usbcontrol

Thread Tools

 
Forum Jump


All times are GMT. The time now is 23:19.