maemo.org - Talk - Thread for problems getting USB hostmode working.

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - Thread for problems getting USB hostmode working. (https://talk.maemo.org/showthread.php?t=65570)

Re: Thread for problems getting USB hostmode working.

I am wondering why the H-E-N app sometimes mounts my USB flash drive read/write and sometimes read-only. Is there a trick as it seems to be rather random whether it will even show the device detected in kernel messages. Some devices like my MP3 player require manual creation of a directory in /media and manual mounting. Also it typically takes two or more clicks to the mount button to mount a flash drive.
I love H-E-N, just trying to figure out the tricks and quirks.

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by Pranjal (Post 1054087)

Is there a way to connect mouse and keyboard together to my N900 without the help of a usb hub? I mean...there are two headed usb cables available in the market as well...

Short answer: no.

Long answer: It would be exactly same as trying to connect 2 devices (USb mouse + USb keyboard) to one port of desktop computer, without using HUB. Try it, but don't blame us if Your ports refuse to work after due to blowed fuse ;) (ho ever, it should just don't work, anyway, except for really screwed up cables)

Cables you're mentioning are totally for different things - most of them time, it's kind of Y-cable for providing additional 500 mAh of power from spare port - for power-hundry HDD's, or BlueRay writers, or whatever.

Ho ever, *sometimes* You may get Your hands on cable that actually contains very small 2-ports hub bundled inside, so it looks exactly like variant of Y-cable, but work like hub. No problems with using it for HEN, but to be honest, I find small USB 2.0 4 ports hubs much more sane thing (they are really small anyway, and contain 4 ports, not just 2...). Also, with hubs bundled inside cable, You can usually forget about powering them up with external power supply. Unless You modify them further, to also contain another plug, just for powering up ;)

Re: Thread for problems getting USB hostmode working.

I see
[WIP]Battery hotswap on field under any load MOD
in your signature, alas no link so I answer here:
This can not work, beware! You MUST NOT connect in parallel a full and an empty battery, worst thing that may happen is one of the cells exploding.
Please be extremely careful when experimenting with batteries, and better check back each step with community.

cheers
jOERG

Re: Thread for problems getting USB hostmode working.

Hi joerg_rw!

Thanks for showing interest and for warning. Indeed, You're right about connecting batteries @ different SoC in parallel - just to be sure than no one will try that. Of course I know it, and that limitation is "base" of my project (and reason, why it's developing so slow - I want to be sure that I'm not gonna kill/fry my battery, or bring danger to other people trying my method).

What I'm trying to achieve, is hotswap possibility via special micro-circuit, that will control hotswapping in safe way. It involves cheating chip via BSI (that same battery is still present), then "switching" battery by circuit via electronic - *without* paralleling batteries in reality, yet with so small interval, that N900 won't notice. Of course, no human being can be so fast, thus electronic need to control that ;) I'm designing it in a way that everything can be put inside Mugen Cover, without external things outside N900 needed.

Obviously, inspiration for this project is your thread about hotswaping via killing bme (and I was going to include full info about inspiration, when announcing in Thread). I wanted to introduce more practical way, without need to disable power-hungry applications - transparent hotswap. Also, I'll be very happy to consult everything with community, I'm definitely not gonna publish any unchecked advices, that may put devices/health of other users in danger.

Also, complication of this project is reason, why I dubbed it "mugen-cover-power" - as parody of kernel-power and busybox-power + allusion to internal power source, allowing hotswap. That wasn't just ego thing ;)

Sorry for off-topic here, I just thought that it's worth to clarify.

Re: Thread for problems getting USB hostmode working.

Hello there, I have come across a problem here. No device (of 2 tested) will connect properly using h-e-n on my N900.

Have just installed h-e-n whilse upgrading to power kernel to v47 (faster app manager suggested, I had v42) and rebooted because h-e-n warned me about v42 being active. Rebooting solved the warning, read on though please..

I am using a new f- to f usb connector in the middle, and a keyboard (pretty old, usb1. tested on PC, works fine.) I am pretty sure the f- to f connector is fine too, because when connecting the N900 to a usb stick via this connector, I can see the USB drive's led blinking several times. So shortly, both keyboard and USB stick don't work.

As for the USB stick, I try to activate via high speed> vbus boost> enumerate> mount (drives should be mounted, right?) I had the cables connected before these operations. After a second or two, flash drive led blinks several times, and then stops blinking. I open up file manager on N900 (as shown in one youtube vid) but the drive will not appear. Have waited almoast one min, should I wait longer?

As for the keyboard, i have the cables connected beforehand and then: low speed> vbus boost> enumerate (no mount). This time, nothing happens. The keyboard led/light should also go on, as tested on my PC. What am I doing wrong?

(have SCCU, pk v47, h-e-n plus dependencies, portrait hildon, plus some other less interesting stuff regarding h-e-n issues)

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by blipnl (Post 1062431)

As for the USB stick, I try to activate via high speed> vbus boost> enumerate> mount (drives should be mounted, right?)

I'm pretty sure I always had to mount the device manually.

Re: Thread for problems getting USB hostmode working.

Update: I now successfully connected a flash drive, only my keyboard prob prevails. Done the same steps, but connected hw cable to n900 after vbus boost, and thus before enumerate (rather then connecting all before any operation). Now I can use the flashdrive on my N900 :)

But the keyboard is still the same, no led activity or any other. Have tried connecting hw cable between step vbus and step enumerate, but no success. At least I now know HW mode sorta works on my N900, so this is probably my fault rather than hw/software? Fingers crossed.

Ty in advance

Re: Thread for problems getting USB hostmode working.

Most of the times, it helps to slow down a little during enabling hostmode. So, wait 2-3 seconds after choosing speed, then, after vbus on, wait 1-2 seconds before connecting cable (physically), then, wait 2-3 seconds, before enumerating...

Anyway, best thing You can do to help us help You is provide here "kernel messages" (dmesg) log, copied *after* unsuccessful attempt to connect keyboard.

Also, just in case, try with different speed. But, log from dmesg is most crucial here.

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by Estel (Post 1062449)

best thing You can do to help us help You is provide here "kernel messages" (dmesg) log, copied *after* unsuccessful attempt to connect keyboard.

Done that as clean as possible first thing after reboot, I notice error -19 and -110. I cannot comprehand this properly ;)
Log:

Code:

[59663.557067] SCSI subsystem initialized 

[59663.727966] Driver 'sd' needs updating - please use bus_type methods 

[59665.754089] wl12xx spi4.0: firmware: requesting wl1251-fw.bin 

[59667.152343] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 

[59667.167877] wl1251: firmware booted (Rev 4.0.4.3.7) 

[59668.816558] wl1251: down 

[59669.777313] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 

[59669.792968] wl1251: firmware booted (Rev 4.0.4.3.7) 

[59670.754089] wlan0: authenticate with AP 00:14:bf:48:9a:2c 

[59670.756835] wlan0: authenticated 

[59670.756866] wlan0: associate with AP 00:14:bf:48:9a:2c 

[59670.759704] wlan0: RX AssocResp from 00:14:bf:48:9a:2c (capab=0x411 status=0 aid=1) 

[59670.759735] wlan0: associated 

[59814.682922] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2 

[59850.437652] Forced hostmode error: no device attached 

[59850.437774] usb usb1: usb resume 

[59850.456848] hub 1-0:1.0: hub_resume 

[59850.456909] hub 1-0:1.0: port 1: status 0301 change 0001 

[59850.566314] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 

[59850.566375] hub 1-0:1.0: port 1, status 0301, change 0000, 1.5 Mb/s 

[59850.691955] usb 1-1: new low speed USB device using musb_hdrc and address 2 

[59855.691406] usb 1-1: khubd timed out on ep0in len=0/64 

[59860.691406] usb 1-1: khubd timed out on ep0in len=0/64 

[59865.691406] usb 1-1: khubd timed out on ep0in len=0/64 

[59865.816375] usb 1-1: device descriptor read/64, error -110 

[59870.925628] usb 1-1: khubd timed out on ep0in len=0/64 

[59875.925659] usb 1-1: khubd timed out on ep0in len=0/64 

[59880.925659] usb 1-1: khubd timed out on ep0in len=0/64 

[59881.050781] usb 1-1: device descriptor read/64, error -110 

[59881.285125] usb 1-1: new low speed USB device using musb_hdrc and address 3 

[59886.285156] usb 1-1: khubd timed out on ep0in len=0/64 

[59891.285156] usb 1-1: khubd timed out on ep0in len=0/64 

[59891.410156] usb 1-1: device descriptor read/64, error -19 

[59891.644378] usb 1-1: device descriptor read/64, error -19 

[59891.878784] usb 1-1: new low speed USB device using musb_hdrc and address 4 

[59892.300750] usb 1-1: device not accepting address 4, error -19 

[59892.425811] usb 1-1: new low speed USB device using musb_hdrc and address 5 

[59892.847625] usb 1-1: device not accepting address 5, error -19 

[59892.847686] hub 1-0:1.0: unable to enumerate USB device on port 1 

[59892.847717] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 

[59892.847747] hub 1-0:1.0: port 1 enable change, status 00000301 

[59894.847625] hub 1-0:1.0: hub_suspend 

[59894.847656] usb usb1: bus auto-suspend 

[59900.382049] twl4030_keypad twl4030_keypad: Spurious key event 4-2 

[59900.559051] twl4030_keypad twl4030_keypad: Spurious key event 4-2 

~ $

Device: HP keyboard 5V 200MA model no. KUS0133.
Method: (a few seconds between these steps) low speed> vbus boost> cables connect> Enumerate.

Re: Thread for problems getting USB hostmode working.

Hello,
A version with Enhanced Linux kernel for power users v2.6.28-maemo42, you will go USB?
Or should kernel to version 47!?