maemo.org - Talk - [Announce] USB hostmode beta release

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

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

- - [Announce] USB hostmode beta release (https://talk.maemo.org/showthread.php?t=65232)

Re: [Announce] USB hostmode beta release

i ordered the female to female connectors way back when, and really never used OTG. I just got an E6 with the factory usb otg cable, im assuming this would work jsut as well with N900?

Edit: well, scratch that, i guess the factory usb otg cable (CA-157) isnt a standard micro usb. its lacking the standard taper dimension and doesnt fit the N900

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by jerryfreak (Post 1061482)

It's a micro-B receptacle on N900, while CA-157 has a micro-A plug fitting the micro-AB receptacle of the device it ships with. All pretty much in line with standards for USB. You'll find this info if only you look a bit - e.g. there: http://talk.maemo.org/showpost.php?p...&postcount=364

N900 isn't meant to do USB hostmode so it got a micro-B receptacle, not a micro-AB

/j

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by joerg_rw (Post 1061912)

N900 isn't meant to do USB hostmode so it got a micro-B receptacle, not a micro-AB

Joerg, this is not quite correct, it should be more like:
N900 wasn't meant to do USB hostmode so it got a micro-B receptacle, not a micro-AB ...

... thanks to Your, and of course all other participants, tremendous and honorable work!

Sorry for OT. ;)

Re: [Announce] USB hostmode beta release

This is amazing! Maybe it will be more amazing if I could charge my battery in host mode.
I followed the instructions that @joerg_rw posted, but the script says "STANDBY". I tried to start and kill it several times with no result.
My N900 is connected to a self powered USB HUB. I tried to test if the hub gives any power to the N900. For this purpose I connected the hub to N900 while the N900 was switched off. The result was: screen flash, vibrating and led flashing. This should mean that the HUB gives power, right?

Re: [Announce] USB hostmode beta release

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

Re: [Announce] USB hostmode beta release

I bought the N8 USB OTG Cable BUT it's not plugging into the N900 :((
whyyyyyyyyyy isn't all micro USB ports the same sizes ??

Re: [Announce] USB hostmode beta release

There are 6 types od USB ports:

USB A
USB B
USB mini A
USB mini B
USB micro A
USB micro B

So you need know which port has your USB cable.

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by Boixos Nois (Post 1068623)

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

Definitely KP 47.

---

As for USB plug problems, just remember, that CA-157 may be easily re-shaped to work on N900 perfectly fine. Even useless (now) ID pin is recognized properly, then.

Re: [Announce] USB hostmode beta release

great application.i really love this app.but i face a problem.i install power kernel and update it.than i install H-E-N.but when i connect a usb mouse,pen drive and others than my n900 show me " unable to connect,no file system available''.and some times show ''mount /dev/sda1 not found''.plz sir help me in details.as soon possible.

thanks

Re: [Announce] USB hostmode beta release

As last time, I'm not demanding anything, but could H-E-N team, consider some status-update info here?

Even if (which I doubt) there was no much activity in the project, it would be good to know about that. There are some joerg_rw patches (like new booston/off) things, that are still not included in -devel version, and up to date no one described what is holding "new version time" for so long.

Again, just to be sure that everyone understand it correctly - I'm not whining here "where will be next version available". It would be just great to know at least what is going on inside the project.

And i know that possibly there are IRC channels/mailing lists or whatever, but info on forum for us - regular Joey's the users/testers/feedbackers would be really appreciated.

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by MohammadAG (Post 866310)

Well, most of you don't know this, but, PR1.3 introduced ~~two~~ things:
~~Backports of new kernel patches to musb, which really helped with hostmode.~~
And.. a new bug, if you connect the wall charger to the device, 100% of the time it will stay on 500 (sometimes 550?) MHz, we do not know the behavior of an overclocked device when this bug is triggered on it, if it stays clocked @ 900 (for example), then we're going to see some dead devices pretty soon.
Anyways, hostmode's patches require 1.3's patches to musb, so until titan updates his kernel, it's a no go, feel free to contact his email address (see http://maemo.org/packages/view/kernel-power-flasher and click his name) and request an update.

Re: [Announce] USB hostmode beta release

Friends please help me....please

Re: [Announce] USB hostmode beta release

On my N900, after closing h-e-n, idle current draw is significantly higher than it was before using hostmode.
As per discussion here --> http://mg.pov.lt/maemo-irclog/%23mae...09-01T23:45:48
it was found that briefly connecting the device to a charger fixes the issue. Another fix that works is to execute /usr/sbin/booston while bme is running, then after about 5 seconds, you kill it and run /usr/sbin/boostoff.
EDIT: it doesn't matter whether bme is running or not. I found that out through updated booston script (see joerg_rw's post below), which stops bme automatically.

Re: [Announce] USB hostmode beta release

I've been wondering that if i could use this function with external touch screen? is there any way to charge phone when it is in hostmode? It would be nice extend to life of my n900 after n9 comes along. I would be installing n900 and touchscreen to car. is there any idea or am i crazy? :D

Re: [Announce] USB hostmode beta release

as for charging while in hostmode, answer is yes. see http://talk.maemo.org/showthread.php...203#post921203

and external touchscreen, i believe it would be recognized as an input device. only issue would be how to calibrate it, etc

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by joerg_rw (Post 1023402)

here an intermediate version of booston, that replaces original file and has some small goodies - a direct uncleaned copy of what's on my hostmode devel device. You might want to edit /etc/mce/mce.ini to define a new pattern "PatternVboost" signalling device is in boostmode (attached my mce.ini for an example).
Of course you may want to keep permissions and owner of original booston, and maybe you need to change the hardcoded path to ic2set in this script (the line "i2cset=/usr/local/sbin/i2cset") to your result of `which i2cset`

This is no official update but just a teaser, as I'm feeling sad with all of you while this is collecting dust on my t900.

Bear with me, a better version is about to include charging and slowly matures here...

/j

Code:

#!/bin/sh

# jrbme "just replaces bme" in fact does more than just that

# It implements FOSS charging via bq24150 and manages hostmode

# For this it implements a daemon mode which is entered by default

# when jrbme is called by user root (i.e. on system init usually) 

# and which cares about keeping battery charged and about signalling

# battery charge status and other events via system dbus 

# When called by any user who's not root, jrbme doesn't enter daemon 

# mode. Instead it serves as a cmd interface between user and a daemonized

# instance of itself, talking to the daemon via signal and named pipes,

# and reporting back to user all result codes, messages to stdout/stderr.

#

# sed -i "s/LEDPatterns=/LEDPatterns=PatternVboost;/" /etc/mce/mce.ini

# vboost with reset on exit and (#'d) partial hostmode for PF-kernel

#(c) 20101030 J.Reisenweber



set -eu

true=true

false=""



${debug=/bin/false} && set -vx; # call like ~# debug="echo -n $0; date" script.sh



#const

PatternVboost=PatternVboost

dbus-send="/usr/bin/run-standalone.sh /usr/bin/dbus-send"

i2cset=/usr/local/sbin/i2cset



#var

: ${start_bme=true}

: ${notify=true}







trap cleanup INT QUIT TERM EXIT

cleanup(){

  trap - INT QUIT TERM EXIT



  # reset bq24150

  $i2cset -y -m 0x80 2 0x6b 0x04 0x80



  # stop LED indicator 

  $dbus-send --system --type=method_call \

    --dest=com.nokia.mce /com/nokia/mce/request \

    com.nokia.mce.request.req_led_pattern_deactivate \

    string:$PatternVboost



  $debug && (

    Reg1=`$i2cget -y 2 0x6b 0x00`

    echo $Reg1

  )

  

  if [ $start_bme ]

  then

    sleep 2

    log "Starting bme"

    /sbin/start --quiet bme

  fi

  exit

}



log(){

  echo "${0}: $@"

}



logn(){

  echo -n "${0}: $@"

}



# the script body. We read in whole text, and then execute a main at end of script,

# this ensures the whole script has correct syntax and there'll be no reads at 

# runtime

main(){

  log "Stopping bme"

  /sbin/stop --quiet bme

  sleep 3

  #echo host >mode

  

  # start vbus boost 5V

  $i2cset -y -m 0x07 2 0x6b 0x01 0x05;

  

  # set notification LED

  $dbus-send --system --type=method_call \

    --dest=com.nokia.mce /com/nokia/mce/request \

    com.nokia.mce.request.req_led_pattern_activate \

    string:$PatternVboost

  

  #sleep 1

  #echo F >/proc/driver/musb-hdrc



  while sleep 5; do

    Reg1=`$i2cget -y 2 0x6b 0x00`

    if [ 8 -ne $(( Reg1 & 0x0F )) ]; then

      errortext1="ERROR in VBUS supply: BQ24150-Reg1=$Reg1"

      case $(( Reg1 & 0x07)) in

        0) errortext2="No error, just stopped";;

        1) errortext2="VBUS OVERVOLTAGE - You just fried your N900";;

        2) errortext2="OVERLOAD - N900 can deliver max 200mA. VBUS got shut off";;

        3) errortext2="Battery too low. VBUS shut off";;

        4) errortext2="Battery OVP - WTF are you doing?";;

        5) errortext2="Thermal Shutdown (too hot)";;

        6) errortext2="Watchdog expired. Script sucks";;

        *) errortext2="WTF? This should not happen";;

      esac



      log "$errortext1"

      log "$errortext2"

      if [ $notify ]; then

        $dbus-send --type=method_call --dest=org.freedesktop.Notifications \

         /org/freedesktop/Notifications \

         org.freedesktop.Notifications.SystemNoteDialog \

         string:"`echo -en "Shutting down 5V supply for USB! Reason:\n$errortext2"`" uint32:0 string:"WARN"; #no idea about WARN

      fi

      cleanup

    fi

    

    # tickle watchdog timer

    $i2cset -y -m 0x80 2 0x6b 0x00 0x80;

  done

  cleanup

}

main "$@"; exit

Using this booston via terminal, I got following error:

Code:

/usr/sbin/booston: line 25: dbus-send=/usr/bin/run-standalone.sh /usr/bin/dbus-send: not found

I've checked that both '/usr/bin/run-standalone.sh' and '/usr/bin/dbus-send' are in correct place. I hope that this will help in improving this script ;)

Also, what may cause this, and, is a chance that this prevent booston for working at all = may prevent hostmode from working correctly? I don't want to assume too early - I got problems with connecting devices (that i know worked flawlessly) with new booston script, but i'm not sure if it's generic hostmode error (i.e. I need to try again few more times), or something with booston.

// Edit

Led pattern is correctly created, ho ever, it doesn't work when I use new booston (even when phone locked or screen off). I suspect it's related to dbus-send fail, ho ever, I still don't know if it prevent booston from working as whole.

Sub-edit:
It seems to me, that due to aforementioned error, new booston doesn't want to work at all on my device. I've tried multiple times to connect device, but even kernel-messages doesn't seem to show any activity on booston, no matter if called from GUI or terminal.

Resurrecting old booston fixed this, and every device, that failed with new booston, works fine now.

// Edit 2

Slightly different topic - I *may* have found something related to "generic hostmode error" (i.e. it doesn't work, and we don't know why), people are experiencing sometimes.

I've checked kernel messages in different situations, when I try to attach my (working flawlessly with HEN, normally) pendrive. Usually, when it does not want to work, it says:

Code:

Forced hostmode error: a full/low-speed device attached but high-speed mode selected

Of course pendrive in question is high-speed device for 100%. Ho ever, I noticed that, when such error appear, and I disconnect my device/adapter/cable at all (same result in every combination), then start from the beginning, kernel messages also state mentioned forced hostmode error - even when no device is attached at all!

Even restarting HEN totally doesn't make difference. If it get "stuck" like that, I've to try again and again, and, it *should* "unstuck" on n attempt. There was no situations, on which I was not able to connect my device at all (but, keep in mind, that I'm somehow stubborn one), it got to work, sooner or later. Still, I got no idea what may cause this type of error.

Of course, trying to use full-speed or low-speed also doesn't solve the problem. It just have to "unstuck". I feel that device may assume something wrong is connected, even before actual device is connected, but I may be wrong.

// Edit 3
sorry for providing so much info/text in one post, but I think it's worth mentioning without delay. Is there any "forced wait" before enabling/disabling booston, and enabling it again?

I'm asking, because, another "scenario" when hostmode reject to work properly, is when I try few devices "in a row". Initially it works, but after few device switches, it stop working, giving constant:

Code:

device descriptor read/64, error -71

I'm thinking it may be related to booston, because, normally, when you call booston, a:

Code:

twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80: link 1

...appear in kernel messages. Ho ever, when such error situation occur, there is no info about twl4030_usb anywhere in log. I've also tried to just enable booston, without actually connecting and enumerating device - it just doesn't appear to do anything. If i left device alone for few minutes, it work again as it should, and booston result in twl4030_usb info popping up.

I think it may be also responsible for high ammount of user-case fails with hostmode - if people constantly try to connect device, booston doesn't get "unstuck".

Re: [Announce] USB hostmode beta release

please get a fixed version of augmented booston from http://maemo.cloud-7.de/maemo5/usr/sbin/booston

sorry for the glitches that sneaked in

[edit]
(yet untested) commands for your convenience:

Code:

root

cd /usr/sbin

mv booston "booston-backup-`date`"

wget http://maemo.cloud-7.de/maemo5/usr/sbin/booston 

chmod a+x booston



echo "new booston should be ready to use now"

Re: [Announce] USB hostmode beta release

Huge thanks joerg_rw, but could You tell me - it was related to my device, or every "generic" user should get this problem? I.E, it was not reported, cause no one dared to test it before, or it's just fault of my configuration?

// Edit

with updated booston, hostmode works like a charm. Ho ever, for some reasons LED indicator doesn't show that device is in vboost mode - no matter if it's locked, unlocked but screen off etc.

I got correct (otherwise working, tested with LED Patterns editor) PatternVboost. It seems that it's just not used.

Anyway, here is my pattern, in case someone may find any error I wasn't able to spot:

Code:

PatternVboost=35;4;0;Rb;9d8040004817e0044807431e7e007e0042000000;9d804000e080421e431e0000

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by Estel (Post 1086924)

with updated booston, hostmode works like a charm.

OK since you have it working and tested what is the short path to the fix? I tried the new booston and that didn't fix it, H-E-N no connect problem started with new KP48. Thanks

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by Estel (Post 1086924)

It's been my fault to edit original script to fix some minor bugs (add run-standalone.sh etc) and then not testing it. Was too sure about my shell scripting fu, envs mustn't contain "-"
So no, nobody noticed that before you did :-(
/j

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by biketool (Post 1087244)

OK since you have it working and tested what is the short path to the fix? I tried the new booston and that didn't fix it, H-E-N no connect problem started with new KP48. Thanks

[2011-09-13 10:17:48] <psycho_oreos> power48 from extras-kernel? I have it working on my other N900 (with cssu maemo15 installed)
[2011-09-13 10:19:02] <psycho_oreos> yes, I have sandisk 32GB flash drive attached to my other N900 and it is working.. the flash drive is mounted and I could see the contents

/j

Re: [Announce] USB hostmode beta release

Joerg,
First thanks for the work both here and on openmoko.
So new booston linked upthread is all that is required to get H-E-N working on KP48?

Re: [Announce] USB hostmode beta release

haha I actually made an epic typo.. I meant extras-devel _not_extras-kernel. There's no such repository as extras-kernel and I'm sure t.m.o. regulars will pick that up in no time :)

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by biketool (Post 1087332)

Joerg,
First thanks for the work both here and on openmoko.
So new booston linked upthread is all that is required to get H-E-N working on KP48?

augmented booston is completely unrelated to PK48
/j

Re: [Announce] USB hostmode beta release

So this is what I am getting now, I downgraded to Nokia kernel reboot and installed KP48 reboot, reinstalled HEN. I have two host cables and the flash drive works on my laptop. Previously H-E-N worked great, I use it quite a bit when cycling to upload pics form my camera SD card.
I am sure it is something simple but I don't know much about USB below the surface.

Code:

[  125.193084] usb usb1: usb resume

[  125.213806] hub 1-0:1.0: hub_resume

[  125.213867] hub 1-0:1.0: port 1: status 0101 change 0001

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

[  125.323272] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[  125.448242] usb 1-1: new high speed USB device using musb_hdrc and address 2

[  125.573242] usb 1-1: device descriptor read/64, error -71

[  125.807647] usb 1-1: device descriptor read/64, error -71

[  126.042114] usb 1-1: new high speed USB device using musb_hdrc and address 3

[  126.167541] usb 1-1: device descriptor read/64, error -71

[  126.401489] usb 1-1: device descriptor read/64, error -71

[  126.635803] usb 1-1: new high speed USB device using musb_hdrc and address 4

[  127.057739] usb 1-1: device not accepting address 4, error -71

[  127.182617] usb 1-1: new high speed USB device using musb_hdrc and address 5

[  127.604553] usb 1-1: device not accepting address 5, error -71

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

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

[  127.604827] hub 1-0:1.0: port 1 enable change, status 00000501

[  130.224121] hub 1-0:1.0: hub_suspend

[  130.224212] usb usb1: bus auto-suspend

[  130.224243] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[  130.224304] usb usb1: bus suspend fail, err -16

[  130.224334] hub 1-0:1.0: hub_resume

[  130.225006] hub 1-0:1.0: port 1: status 0501 change 0000

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

[  130.225189] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[  130.346801] usb 1-1: new high speed USB device using musb_hdrc and address 6

[  130.471740] usb 1-1: device descriptor read/64, error -71

[  130.706115] usb 1-1: device descriptor read/64, error -71

[  130.940551] usb 1-1: new high speed USB device using musb_hdrc and address 7

[  131.065521] usb 1-1: device descriptor read/64, error -71

[  131.299896] usb 1-1: device descriptor read/64, error -71

[  131.534240] usb 1-1: new high speed USB device using musb_hdrc and address 8

[  131.956085] usb 1-1: device not accepting address 8, error -71

[  132.081329] usb 1-1: new high speed USB device using musb_hdrc and address 9

[  132.502960] usb 1-1: device not accepting address 9, error -71

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

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

[  132.503204] hub 1-0:1.0: port 1 enable change, status 00000501

[  135.222015] hub 1-0:1.0: hub_suspend

[  135.222045] usb usb1: bus auto-suspend

[  135.222076] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[  135.222106] usb usb1: bus suspend fail, err -16

[  135.222106] hub 1-0:1.0: hub_resume

[  135.222167] hub 1-0:1.0: port 1: status 0501 change 0000

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

[  135.222259] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[  135.346740] usb 1-1: new high speed USB device using musb_hdrc and address 10

[  135.471740] usb 1-1: device descriptor read/64, error -71

[  135.706146] usb 1-1: device descriptor read/64, error -71

[  135.940429] usb 1-1: new high speed USB device using musb_hdrc and address 11

[  136.065429] usb 1-1: device descriptor read/64, error -71

[  136.300048] usb 1-1: device descriptor read/64, error -71

[  136.534301] usb 1-1: new high speed USB device using musb_hdrc and address 12

[  136.955963] usb 1-1: device not accepting address 12, error -71

[  137.081054] usb 1-1: new high speed USB device using musb_hdrc and address 13

[  137.502990] usb 1-1: device not accepting address 13, error -71

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

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

[  137.503265] hub 1-0:1.0: port 1 enable change, status 00000501

[  140.221618] hub 1-0:1.0: hub_suspend

[  140.221679] usb usb1: bus auto-suspend

[  140.221679] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[  140.221710] usb usb1: bus suspend fail, err -16

[  140.221740] hub 1-0:1.0: hub_resume

[  140.221771] hub 1-0:1.0: port 1: status 0501 change 0000

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

[  140.221862] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[  140.346740] usb 1-1: new high speed USB device using musb_hdrc and address 14

[  140.471710] usb 1-1: device descriptor read/64, error -71

[  140.706024] usb 1-1: device descriptor read/64, error -71

Re: [Announce] USB hostmode beta release

H-E-N works for me on KP48 with or without new booston (latest one). What You've experiencing seems to me as thing that I called unoficially "generic hostmode error", few posts ago.

Also, this may be "false alarm", but I don't see any indication of vboost on in Your log (tw4030_usb thing).

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by Estel (Post 1086924)

Code:

PatternVboost=35;4;0;Rb;9d8040004817e0044807431e7e007e0042000000;9d804000e080421e431e0000

make sure you have added ;PatternVboost at the end of LEDPatterns=............. line
and stop and restart mce

Re: [Announce] USB hostmode beta release

You're perfectly right blue_led, and it was my user fault (i've discovered it just few minutes ago, thanks to little talk with Pali on irc, about charging while hostmode is on ;) ) I've just forget to add ;PatternVboost to LEDPatterns=

After fixing that, LEDPattern works great, so thanks for that feature joerg_rw, and sorry for false alarm about this.

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by Estel (Post 1087555)

Also, this may be "false alarm", but I don't see any indication of vboost on in Your log (tw4030_usb thing).

I do get power to the USB gadgets, lights come on and flash in patterns similar to when H-E-N worked, I suspect that it falls apart at the end of enumerate but like I said I don't know much about lower levels of the USB protocols.

Re: [Announce] USB hostmode beta release

I like to recommend a tool: http://maemo.org/packages/view/mceledpattern/ :-D

Code:

IroN900:~# mceledpattern --help

Usage:

  mceledpattern add[_vibra] <pattern_name> <pattern>

  mceledpattern remove[_vibra] <pattern_name>



  To replace existing pattern use add, to restore replaced

  pattern back to previous value use remove

IroN900:~#

Re: [Announce] USB hostmode beta release

I also posted results of using a full speed keyboard with hub chip and USB port. My flash drive worked plugged into the keyboard plugged into the N900 host cable but not plugged in direct.
http://talk.maemo.org/showthread.php?t=65570&page=32

I hope there is something useful in hostmode.txt

Code:

 98.761718] hub 1-0:1.0: hub_resume

[   98.761779] hub 1-0:1.0: port 1: status 0101 change 0001

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

[   98.871185] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[   98.996124] usb 1-1: new full speed USB device using musb_hdrc and address 2

[   99.144500] usb 1-1: ep0 maxpacket = 8

[   99.145050] usb 1-1: default language 0x0409

[   99.145843] usb 1-1: uevent

[   99.145965] usb 1-1: usb_probe_device

[   99.145965] usb 1-1: configuration #1 chosen from 1 choice

[   99.148590] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[   99.148773] usb 1-1:1.0: uevent

[   99.148895] hub 1-1:1.0: usb_probe_interface

[   99.149566] hub 1-1:1.0: usb_probe_interface - got id

[   99.149597] hub 1-1:1.0: USB hub found

[   99.151123] hub 1-1:1.0: 2 ports detected

[   99.151153] hub 1-1:1.0: compound device; port removable status: FR

[   99.151184] hub 1-1:1.0: individual port power switching

[   99.151184] hub 1-1:1.0: individual port over-current protection

[   99.151214] hub 1-1:1.0: power on to power good time: 44ms

[   99.151336] hub 1-1:1.0: hub controller current requirement: 100mA

[   99.151336] hub 1-1:1.0: 100mA bus power budget for each child

[   99.151428] hub 1-1:1.0: enabling power on all ports

[   99.152191] drivers/usb/core/inode.c: creating file '002'

[   99.152587] usb 1-1: New USB device found, idVendor=046e, idProduct=5400

[   99.152618] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[   99.152648] usb 1-1: Product: Multimedia USB Keyboard

[   99.152648] usb 1-1: Manufacturer: BTC

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

[   99.152709] hub 1-0:1.0: port 1 enable change, status 00000103

[   99.246246] hub 1-1:1.0: port 1: status 0101 change 0001

[   99.347656] hub 1-1:1.0: state 7 ports 2 chg 0002 evt 0000

[   99.347808] hub 1-1:1.0: port 1, status 0101, change 0000, 12 Mb/s

[   99.433746] usb 1-1.1: new full speed USB device using musb_hdrc and address 3

[   99.542938] usb 1-1.1: ep0 maxpacket = 8

[   99.543365] usb 1-1.1: skipped 1 descriptor after interface

[   99.543487] usb 1-1.1: default language 0x0409

[   99.544219] usb 1-1.1: uevent

[   99.544311] usb 1-1.1: usb_probe_device

[   99.544342] usb 1-1.1: configuration #1 chosen from 1 choice

[   99.546875] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)

[   99.547058] usb 1-1.1:1.0: uevent

[   99.548706] drivers/usb/core/inode.c: creating file '003'

[   99.550231] usb 1-1.1: New USB device found, idVendor=046e, idProduct=530a

[   99.550262] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[   99.550292] usb 1-1.1: Product: Multimedia USB Keyboard

[   99.550292] usb 1-1.1: Manufacturer: BTC

[   99.550292] hub 1-1:1.0: 400mA power budget left

[   99.550323] hub 1-1:1.0: state 7 ports 2 chg 0000 evt 0002

[   99.900909] usbhid 1-1.1:1.0: usb_probe_interface

[   99.900939] usbhid 1-1.1:1.0: usb_probe_interface - got id

[   99.911499] input: BTC Multimedia USB Keyboard as /class/input/input4

[   99.996185] generic-usb 0003:046E:530A.0001: input: USB HID v1.10 Keyboard [BTC Multimedia USB Keyboard] on usb-musb_hdrc-1.1/input0

[  100.000640] usbcore: registered new interface driver usbhid

[  100.000701] usbhid: v2.6:USB HID core driver

[  153.035614] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1

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

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

[  187.649810] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s

[  187.649841] usb 1-1: USB disconnect, address 2

[  187.649871] usb 1-1.1: USB disconnect, address 3

[  187.649902] usb 1-1.1: unregistering device

[  187.649932] usb 1-1.1: usb_disable_device nuking all URBs

[  187.650024] musb_hdrc musb_hdrc: shutdown urb c4bd4a00 ep1in-intr

[  187.650054] usb 1-1.1: unregistering interface 1-1.1:1.0

[  187.746612] usb 1-1.1:1.0: uevent

[  187.747161] usb 1-1.1: uevent

[  187.747253] usb 1-1: unregistering device

[  187.747253] usb 1-1: usb_disable_device nuking all URBs

[  187.747314] musb_hdrc musb_hdrc: shutdown urb c4bd4880 ep1in-intr

[  187.747314] usb 1-1: unregistering interface 1-1:1.0

[  187.747558] usb 1-1:1.0: uevent

[  187.747924] usb 1-1: uevent

[  187.902404] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101

[  188.028564] usb 1-1: new full speed USB device using musb_hdrc and address 4

[  188.175750] usb 1-1: ep0 maxpacket = 8

[  188.176635] usb 1-1: default language 0x0409

[  188.177734] usb 1-1: uevent

[  188.177825] usb 1-1: usb_probe_device

[  188.177856] usb 1-1: configuration #1 chosen from 1 choice

[  188.180297] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[  188.180480] usb 1-1:1.0: uevent

[  188.180603] hub 1-1:1.0: usb_probe_interface

[  188.180603] hub 1-1:1.0: usb_probe_interface - got id

[  188.180633] hub 1-1:1.0: USB hub found

[  188.181793] hub 1-1:1.0: 2 ports detected

[  188.181823] hub 1-1:1.0: compound device; port removable status: FR

[  188.181823] hub 1-1:1.0: individual port power switching

[  188.181854] hub 1-1:1.0: individual port over-current protection

[  188.181854] hub 1-1:1.0: power on to power good time: 44ms

[  188.182464] hub 1-1:1.0: hub controller current requirement: 100mA

[  188.182495] hub 1-1:1.0: 100mA bus power budget for each child

[  188.182617] hub 1-1:1.0: enabling power on all ports

[  188.183349] drivers/usb/core/inode.c: creating file '004'

[  188.183776] usb 1-1: New USB device found, idVendor=046e, idProduct=5400

[  188.183807] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[  188.183807] usb 1-1: Product: Multimedia USB Keyboard

[  188.183837] usb 1-1: Manufacturer: BTC

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

[  188.183898] hub 1-0:1.0: port 1 enable change, status 00000103

[  188.277618] hub 1-1:1.0: port 1: status 0101 change 0001

[  188.378997] hub 1-1:1.0: state 7 ports 2 chg 0002 evt 0000

[  188.379150] hub 1-1:1.0: port 1, status 0101, change 0000, 12 Mb/s

[  188.465179] usb 1-1.1: new full speed USB device using musb_hdrc and address 5

[  188.574371] usb 1-1.1: ep0 maxpacket = 8

[  188.575103] usb 1-1.1: skipped 1 descriptor after interface

[  188.575317] usb 1-1.1: default language 0x0409

[  188.576995] usb 1-1.1: uevent

[  188.577209] usb 1-1.1: usb_probe_device

[  188.577239] usb 1-1.1: configuration #1 chosen from 1 choice

[  188.581848] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)

[  188.582336] usb 1-1.1:1.0: uevent

[  188.582611] usbhid 1-1.1:1.0: usb_probe_interface

[  188.582672] usbhid 1-1.1:1.0: usb_probe_interface - got id

[  188.600067] input: BTC Multimedia USB Keyboard as /class/input/input5

[  188.691528] generic-usb 0003:046E:530A.0002: input: USB HID v1.10 Keyboard [BTC Multimedia USB Keyboard] on usb-musb_hdrc-1.1/input0

[  188.692810] drivers/usb/core/inode.c: creating file '005'

[  188.693511] usb 1-1.1: New USB device found, idVendor=046e, idProduct=530a

[  188.693572] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[  188.693603] usb 1-1.1: Product: Multimedia USB Keyboard

[  188.693634] usb 1-1.1: Manufacturer: BTC

[  188.693664] hub 1-1:1.0: 400mA power budget left

[  188.693695] hub 1-1:1.0: state 7 ports 2 chg 0000 evt 0002

[  298.542480] hub 1-1:1.0: state 7 ports 2 chg 0000 evt 0004

[  298.542968] hub 1-1:1.0: port 2, status 0101, change 0001, 12 Mb/s

[  298.699615] hub 1-1:1.0: debounce: port 2: total 100ms stable 100ms status 0x101

[  298.785400] usb 1-1.2: new full speed USB device using musb_hdrc and address 6

[  298.895812] usb 1-1.2: not running at top speed; connect to a high speed hub

[  298.897430] usb 1-1.2: default language 0x0409

[  298.899810] usb 1-1.2: uevent

[  298.900024] usb 1-1.2: usb_probe_device

[  298.900054] usb 1-1.2: configuration #1 chosen from 1 choice

[  298.903381] usb 1-1.2: adding 1-1.2:1.0 (config #1, interface 0)

[  298.903717] usb 1-1.2:1.0: uevent

[  298.903961] libusual 1-1.2:1.0: usb_probe_interface

[  298.904052] libusual 1-1.2:1.0: usb_probe_interface - got id

[  298.907073] drivers/usb/core/inode.c: creating file '006'

[  298.907745] usb 1-1.2: New USB device found, idVendor=058f, idProduct=6387

[  298.907806] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[  298.907836] usb 1-1.2: Product: Mass Storage Device

[  298.907867] usb 1-1.2: Manufacturer: JetFlash

[  298.907897] usb 1-1.2: SerialNumber: 2F6KJUZA

[  298.907928] hub 1-1:1.0: 300mA power budget left

[  298.907958] hub 1-1:1.0: state 7 ports 2 chg 0000 evt 0004

[  298.975921] Initializing USB Mass Storage driver...

[  298.976196] usb-storage 1-1.2:1.0: usb_probe_interface

[  298.976257] usb-storage 1-1.2:1.0: usb_probe_interface - got id

[  298.977874] scsi0 : SCSI emulation for USB Mass Storage devices

[  298.982910] usbcore: registered new interface driver usb-storage

[  298.982940] USB Mass Storage support registered.

[  298.985382] usb-storage: device found at 6

[  298.985382] usb-storage: waiting for device to settle before scanning

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

[  302.304992] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s

[  302.304992] usb 1-1: USB disconnect, address 4

[  302.305023] usb 1-1.1: USB disconnect, address 5

[  302.305023] usb 1-1.1: unregistering device

[  302.305053] usb 1-1.1: usb_disable_device nuking all URBs

[  302.305084] musb_hdrc musb_hdrc: shutdown urb c30ba780 ep1in-intr

[  302.305114] usb 1-1.1: unregistering interface 1-1.1:1.0

[  302.395263] usb 1-1.1:1.0: uevent

[  302.395935] usb 1-1.1: uevent

[  302.396026] usb 1-1.2: USB disconnect, address 6

[  302.396057] usb 1-1.2: unregistering device

[  302.396057] usb 1-1.2: usb_disable_device nuking all URBs

[  302.396087] usb 1-1.2: unregistering interface 1-1.2:1.0

[  302.417694] usb 1-1.2:1.0: uevent

[  302.419067] usb 1-1.2: uevent

[  302.419189] usb 1-1: unregistering device

[  302.419189] usb 1-1: usb_disable_device nuking all URBs

[  302.419250] musb_hdrc musb_hdrc: shutdown urb c30ba580 ep1in-intr

[  302.419250] usb 1-1: unregistering interface 1-1:1.0

[  302.419555] usb 1-1:1.0: uevent

[  302.420013] usb 1-1: uevent

[  302.574645] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101

[  302.699310] usb 1-1: new full speed USB device using musb_hdrc and address 7

[  302.847686] usb 1-1: ep0 maxpacket = 8

[  302.848571] usb 1-1: default language 0x0409

[  302.849273] usb 1-1: uevent

[  302.849395] usb 1-1: usb_probe_device

[  302.849395] usb 1-1: configuration #1 chosen from 1 choice

[  302.851226] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[  302.851379] usb 1-1:1.0: uevent

[  302.851470] hub 1-1:1.0: usb_probe_interface

[  302.851501] hub 1-1:1.0: usb_probe_interface - got id

[  302.851501] hub 1-1:1.0: USB hub found

[  302.852539] hub 1-1:1.0: 2 ports detected

[  302.852569] hub 1-1:1.0: compound device; port removable status: FR

[  302.852569] hub 1-1:1.0: individual port power switching

[  302.852600] hub 1-1:1.0: individual port over-current protection

[  302.852600] hub 1-1:1.0: power on to power good time: 44ms

[  302.852966] hub 1-1:1.0: hub controller current requirement: 100mA

[  302.852996] hub 1-1:1.0: 100mA bus power budget for each child

[  302.853088] hub 1-1:1.0: enabling power on all ports

[  302.853759] drivers/usb/core/inode.c: creating file '007'

[  302.854064] usb 1-1: New USB device found, idVendor=046e, idProduct=5400

[  302.854095] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[  302.854125] usb 1-1: Product: Multimedia USB Keyboard

[  302.854125] usb 1-1: Manufacturer: BTC

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

[  302.854187] hub 1-0:1.0: port 1 enable change, status 00000103

[  302.949554] hub 1-1:1.0: port 1: status 0101 change 0001

[  302.949676] hub 1-1:1.0: port 2: status 0101 change 0001

[  303.050811] hub 1-1:1.0: state 7 ports 2 chg 0006 evt 0000

[  303.050964] hub 1-1:1.0: port 1, status 0101, change 0000, 12 Mb/s

Re: [Announce] USB hostmode beta release

[2011-09-14 12:43:24] <Sicelo> to disturb a little: i am using h-e-n with the latest booston script. connecting an externally powered hub (not for charging) i always get VBUS OVERVOLTAGE - You just fried your N900. at least the port is still fine :) any ideas?
[2011-09-14 12:48:56] <Sicelo> i am connecting the hub to N900 soon after i turn VBoost On
[2011-09-14 12:52:40] <DocScrutinizer> Sicelo: this indicates your externally powered hub feeds back a somewhat too high voltage to the N900 USB port
[2011-09-14 12:53:57] <DocScrutinizer> Sicelo: I had to look up in bq24150 datasheet what exactly VBUS overvoltage means, I guess it gets triggered on >6V or sth
[2011-09-14 13:04:06] <DocScrutinizer> VBUS ABS MAX -0.3 .. 20 V
[2011-09-14 13:04:39] <DocScrutinizer> (3) The bq24150/1 family can withstand up to 10.6 V continuously and 20 V for a maximum of 432 hours.
[2011-09-14 13:05:18] <DocScrutinizer> ABS MAX for other chips' pins connected to VBUS is way lower though
[2011-09-14 13:06:39] <DocScrutinizer> recomended operating conditins: VBUS Supply voltage, VBUS min:4 max:6 Volt
[2011-09-14 13:07:26] <DocScrutinizer> (1) The inherent switching noise voltage spikes should not exceed the absolute maximum rating on either the BOOST or SW pins. A tight layout minimizes switching noise.
[2011-09-14 13:11:18] <DocScrutinizer> VBUS(OVP) Overvoltage protection threshold for boost (VBUS pin) Threshold over VBUS to turn off converter during boost min:5.8 nominal:6 max:6.2 V

The "you just fried your N900" part is a bit of tongue-in-cheek, but honestly you shouldn't gamble with it. Anyway I don't give any warranty on N900 actually being fried when this error notification pops up ;-D

Re: [Announce] USB hostmode beta release

Code:

[  126.167541] usb 1-1: device descriptor read/64, error -71

[  126.401489] usb 1-1: device descriptor read/64, error -71

[  126.635803] usb 1-1: new high speed USB device using musb_hdrc and address 4

[  127.057739] usb 1-1: device not accepting address 4, error -71

[  127.182617] usb 1-1: new high speed USB device using musb_hdrc and address 5

[  127.604553] usb 1-1: device not accepting address 5, error -71

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

so the above issue is addressed here
http://ubuntuforums.org/showthread.php?t=797789&page=2
and
http://www.guyrutenberg.com/2008/06/...ad64-error-71/
and
http://www.linux-usb.org/FAQ.html#ts10

for the above problem:
usb 1-1: device descriptor read/64, error -71
they say to...
sudo su
so it all runs as root and then...
echo Y > /sys/module/usbcore/parameters/old_scheme_first

I do know that HEN is a hack of regular USB due to Nokia closed hardware/driver maybe a nonfunctional microUSB port pin too. I have no idea if this will work or just totally break HEN so I await the advice of someone who really knows.

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by biketool (Post 1088100)

[...]
for the above problem:
usb 1-1: device descriptor read/64, error -71
they say to...
sudo su
so it all runs as root and then...
echo Y > /sys/module/usbcore/parameters/old_scheme_first

I do know that HEN is a hack of regular USB due to Nokia closed hardware/driver maybe a nonfunctional microUSB port pin too. I have no idea if this will work or just totally break HEN so I await the advice of someone who really knows.

Code:

IroN900:~# ll /sys/module/usbcore/parameters/old_scheme_first

-rw-r--r-- 1 root root 4096 2011-09-14 15:27 /sys/module/usbcore/parameters/old_scheme_first

IroN900:~# cat /sys/module/usbcore/parameters/old_scheme_first

N

No idea if it works and fixes the error, but for sure it won't make your device explode :-)
Please test and report if it changes things to the better for you

Many thanks biketool for this very useful comment

cheers
jOERG

ps: I'd use "root" rather than "sudo su"

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by joerg_rw (Post 1088185)

Code:

IroN900:~# ll /sys/module/usbcore/parameters/old_scheme_first

-rw-r--r-- 1 root root 4096 2011-09-14 15:27 /sys/module/usbcore/parameters/old_scheme_first

No idea if it works and fixes the error, but for sure it won't make your device explode :-)
Please test and report if it changes things to the better for you

No change after running
echo Y > /sys/module/usbcore/parameters/old_scheme_first
as root, same error codes.

I am no USB guru and that was as far as I got with Google. It could be I have an unusual USB drive, although it was not a problem a few weeks ago making me suspect the kernel upgrade might be involved. Do new drivers get compiled for eack power user kernel, it has been 15 years since I had to worry about things like this and I am VERY rusty. If I can find my wifes lost MP3 player I will try that too.
Thanks for testing Joerg, I wasn't sure what that was supposed to do and don't like running commands that I don't fully understand and cant undo in my everyday phone.

Re: [Announce] USB hostmode beta release

Q: Why doesn't USB work at all? I get "device not accepting address".
A: This can be one of several problems:
High speed devices sometimes have problems with cables used to connect them. They're more sensitive to signal quality issues than older usb 1.1 full or low speed devices. If the device works OK at full speed on the same system, after you "rmmod ehci-hcd" [[comment: "on using low speed or full speed setting"]], this is likely the problem you're seeing. There are a lot of things you can do to change signal quality.
Use a different cable. Some are even marketed specifically for use with high speed devices. Most USB 1.1 cables work just fine at high speed, but the one you're using might be an exception (maybe it's been damaged).
Switch to a different USB connector on your computer. Back panel connectors are often right on the motherboard, with much care taken to preserve signal quality. A front panel connector probably doesn't use cabling designed with USB in mind; and its cable could be damaged by bending, baking or something else even when it's not routed through the power supply.
Use an external high speed hub. Those hubs have signal conditioning circuitry that may cover up certain flaws.
Make sure your device is using its own external power supply, or that its battery is fully charged.
You might be able to get the same device to work at high speed on a different machine.

from http://www.linux-usb.org/FAQ.html#ts6

/j

Re: [Announce] USB hostmode beta release

I have two host mode cables, both show the same error, both worked well with HEN 3-4 weeks ago. Formatting the flash drive doesn't fix the problem, no does old_scheme_first. My cheap Davidcom wired NIC which Pali added drivers for in PK48 is acting no differently now, no driver loads. Is it having a hub circuit or a full speed hub chip in the middle? Is it the cables both going bad? I have ordered another cable just in case.

Joerg and others, off topic a bit. Did anyone ever get USB host working on your Openmoko phones? I have one laying around but it was terrible as a phone missing calls all the time so I didn't really work too hard with it.

Re: [Announce] USB hostmode beta release

Quote:

Originally Posted by biketool (Post 1088437)

Joerg and others, off topic a bit. Did anyone ever get USB host working on your Openmoko phones? I have one laying around but it was terrible as a phone missing calls all the time so I didn't really work too hard with it.

Sure, USB hostmode was working just fine on OM FR. That's where my Y-cable addiction and concerns about charging hostmode comes from, I introduced it there.

/j

Re: [Announce] USB hostmode beta release

I sometimes still use my neo1973 as a secondary GPS for a cycling partner. Did you document the host mode setup?

Re: [Announce] USB hostmode beta release

The problem I always had is that I never mounted devices.

Where are the scripts to check and see if I can improve or at least run on my N900?

If I manually mount I have no problems.