Active Topics
-
Maemo repository (5)
to Community by dredlok706 - 1 day, 4 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 1 day, 6 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days ago -
List of well performing apps on Leste (33)
to Maemo 7 / Leste by teroyk - 2 days, 8 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 3 days, 12 hrs ago -
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 6 days, 15 hrs ago - more...
 |
|
2011-05-15
, 04:52
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#232
|
Originally Posted by cheve
1. boostoff and booston are provided with HEN. If You have latest HEN installed, you just have that 2 commands "aboard". The'yre executed just by:
All,
I have a few questions about charging while USB host is enabled. I have read the post http://talk.maemo.org/showpost.php?p...&postcount=647. I have a few things that I do not understanding..
1. jOERG mentioned about booston and boostoff script, are they provided?
2. jOERG's post point to the http://enivax.net/jk/n900/charge.sh.txt. My guess is that I need to download the charge.sh.txt to N900, then rename it as charge.sh and then run it. The question is where should this script reside in the N900.
3. What is the exact command at the x-term to run the charge.sh?
should it be "charge"
or
"charge &"
4. If the device that I want to use requires power itself(ie. usb harddrive); how does one setup charging under this scenario?
thanks
booston
boostoff
in console (not 2 at once, use only one that You want in the moment) - don't need to put anything before or after that command, but be sure that You're root. Overall, executing this commands act exact same way as enabling, for example, leafpad - You don't need to provide path to the file, just call it out from the console.
2. Good guessing - you need to download it, and put whenever You want in Your phone, except MyDocs, that by default is nk-exec. BUT, to execute THAT script, You need to provide full path to it, so putting it into root ("/") directory can be good idea. Personally, i would recommend to rename it to something like "charger", without .sh or .txt. - faster executing.
If You put it into root, You type in terminal:
/charger
(or whatever name You renamed it to). Notice the "/" - that because you must provide full path to the file. So, if you place it under "/home", to execute charger you need:
/home/charger
also, If you download it on Your desktop computer with windows/mac/whatever system that doesn't keep file permissions, You need to:
chmod 775 /charger
to make it executable - other way You get "permission denied" reply, what was the case for me.
Remember, that in my examples charge.sh.txt was renamed to "charger" (without any extensions).
Also, about executing whole thing - this is very straightforward, if You know that joerg_rw was executing many other commands to just "show" that battery is charging. you don't need to do that. to achieve charging during hostmode, You need literally 2-3 commands (depending on situation), and to have charging script downloaded and put somewhere on Your phone with executable rights.
Then, You just:
1. start hostmode as normal, select speed, vbus, enumerate, mount if You connected storage media...
2. without disabling HEN, open xterm and use:
boostoff
3. Next, do (in case that Your charging script is renamed to "charger" and put into root directory):
/charger
script will start its job... From my experience, if second output is like:
Status: 0x10 Mode: CHARGING Full: 0 WallCharger: 0 Battery Voltage: 4150 NAC: 1987 Battery level: 97 %
.. then you're all done. You can minimize xterm (DON'T close it - charging will stop after 10 seconds, if you close Xterm, because that terminates script going inside it). If You want to do something inside xterm, just click "xterminal" on upper part of the screen, then choose "new" (Yea, i know its basic thing, but i was searching for few hours how can i do something in terminal while charging during hostmode... 0_o... shadowjk kindly and mercifully brightened me up...).
But, if Your second line in output after executing "/charger" is like:
Status: 0x20 Mode: STANDBY Full: 0 WallCharger: 0 Battery Voltage: 3967 NAC: 1999 Battery level: 97 %
...then you need to press ctrl+c (that will stop script and allow You to type in same terminal window again) and execute:
/charger
...again. This time You're done for sure.
---
Side note: I don't know why in joerg_rw example we must use "/charger" twice. For me, 99% times it work just after first try - i double checked, if charging really goes on. But, literally one time, i get STANDBY - so, i just followed joerg_rw advice, ctrl-c'ing. I don't know why this work like that - i think joerg_rw know, so we can ask him
Last but not least, Your question about externally-powered things, like hard disc. I suppose that you know about "y-cable" thing to charge while hostmode, OR - method that i prefer - USB 2.0 active HUB (this way You DON'T need "y-cable"). Then, if your HDD or CD/DVd is powered externally by own power supply - that doesn't matter for charging while hostmode at all. HDD use own power, and Your N900 use Y-cable power or active HUB power.
IF HDD need to draw much power from USB line, Y-cable or powered HUB should provide it - again, you don't care about that. Sometimes, HDD's got own Y-cable, that you literally plug into 2 ports, to draw 1A instead of 500 mA (500mA is current limit for 1 port) - in that case, active HUB is a must (or You just use additional 5V charger with USB port - this way, You need to use additional wall plug, and you plug powering part of HDD's y-cable to that charger).
Another side note - sometimes, externally powered things like HDD's and USB printers also provide 5V at their USB PLUG (not port... don't ask about design). This way You can charge during hostmode by just connecting that peripheral to Your N900, without Y-cable or active HUB
It's funny to see how Your N900 print using printer, and the same time it is CHARGED by that printer... But, i encountered literally ONE printer like that. Normally, externally powered printers doesn't need current on USB plug, neither doesn't provide it.If You got any additional question, just feel free to ask. And, don't be scarred by length of that post - i tried to cover every aspect of charging during USB. In most cases it is as easy as executing 2 commands in xTerm...
| The Following 3 Users Say Thank You to Estel For This Useful Post: | ||
 |
|
2011-05-15
, 14:02
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#233
|
Estel,
many thanks for this excellent explanation. :-D
cheers
jOERG
many thanks for this excellent explanation. :-D
cheers
jOERG
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
| The Following User Says Thank You to joerg_rw For This Useful Post: | ||
|
|
2011-05-17
, 01:03
|
|
Posts: 362 |
Thanked: 143 times |
Joined on Mar 2008
|
#234
|
Hi,
I tried hostmode again today and for some reasons my N900 no longer 'see' my drives. I was able to attached them and worked with them before with N900. I checked the hostmode file, it seems that h.e.n. sees the drive, but N900 could not mount it.
I have power kernel 47. Would appreciate some help.
thank you for your time,
cheers,
Attached is the hostmode file.
I tried hostmode again today and for some reasons my N900 no longer 'see' my drives. I was able to attached them and worked with them before with N900. I checked the hostmode file, it seems that h.e.n. sees the drive, but N900 could not mount it.
I have power kernel 47. Would appreciate some help.
thank you for your time,
cheers,
Attached is the hostmode file.
|
|
2011-05-18
, 03:04
|
|
Posts: 362 |
Thanked: 143 times |
Joined on Mar 2008
|
#235
|
@Estel, thank for giving me the helping hand.
I am able to connect(to both of my drives) again. The solution: one really needs to SLOW DOWN. For my case, I select the speed, then set the VBUS boost on, then select "enumerate" and then wait for at least 5 seconds(I went to check the log to ensure that no newer entries are written to it), and then select the 'mount'.
As for charging, I got
sleep 1 status 0x00
status: 0x00 mode: STANDBY FULL
so, I don't know whether it is working for me or not; but my guess is that it is not working. The 'status:0x00 mode: STANDBY FULL' message repeat itself at the xterm with the value of Battery Voltage dropping at each successive message.
What is the difference between status 0x00 and 0x02?
I have tried the CTRL-C and then re-executed the charger script; but I got the same result(ie. status 0x00 and STANDBY FULL)
One more observation, there is about 3 to 5 seconds wait time between the 1st and then the showing of the 2nd messages.
As a recap, I connect the stuffs as follows:
1. 4-port usb hub connects to the wall A/C.
2. n900 connects to the hub with a straight usb cable
3. usb drive connects to the hub with a Y-cable
Cheers,
I am able to connect(to both of my drives) again. The solution: one really needs to SLOW DOWN. For my case, I select the speed, then set the VBUS boost on, then select "enumerate" and then wait for at least 5 seconds(I went to check the log to ensure that no newer entries are written to it), and then select the 'mount'.
As for charging, I got
sleep 1 status 0x00
status: 0x00 mode: STANDBY FULL
so, I don't know whether it is working for me or not; but my guess is that it is not working. The 'status:0x00 mode: STANDBY FULL' message repeat itself at the xterm with the value of Battery Voltage dropping at each successive message.
What is the difference between status 0x00 and 0x02?
I have tried the CTRL-C and then re-executed the charger script; but I got the same result(ie. status 0x00 and STANDBY FULL)
One more observation, there is about 3 to 5 seconds wait time between the 1st and then the showing of the 2nd messages.
As a recap, I connect the stuffs as follows:
1. 4-port usb hub connects to the wall A/C.
2. n900 connects to the hub with a straight usb cable
3. usb drive connects to the hub with a Y-cable
Cheers,
| The Following User Says Thank You to cheve For This Useful Post: | ||
|
|
2011-05-20
, 16:40
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#236
|
Are You sure that Your battery isn't full or almost full, when You try to charge it while hostmode? I'll try to replicate this after my next charging cycle, but message seems quite self-explanatory. Can You post here Your voltage readings, when You got that message? Also, could You try hostmode charging with battery ~50% (or lower, just to be sure)?
I'm glad that You succeed with mounting. Hope that charging will go as well.
Last edited by Estel; 2011-05-22 at 00:27.
I'm glad that You succeed with mounting. Hope that charging will go as well.
Last edited by Estel; 2011-05-22 at 00:27.
|
|
2011-05-20
, 23:48
|
|
Posts: 1,258 |
Thanked: 672 times |
Joined on Mar 2009
|
#237
|
You're reading it wrong for starters,
it's not "STANDBY FULL", it's:
Status: 0x00
Mode: Standby
Full: 0
Wall: 0
Status code is directly from the hw chip:
0 - Standby
1 - Charge in progress
2 - Charge done
Mode and Full are just flags tracked by the charge script for its own use. Wall is whether wall charger has been detected.
Things to note:
The charger chip is programmed on script start. There's no error recovery. Chip resets to defaults on some error conditions.
This means in some circumstanced the charger chip can go back to its defaults, which are to charge the battery to 20-40% at a slow rate.
The logs written in /home/user/MyDocs/ can provide some hints to whether there has been a fault condition.
it's not "STANDBY FULL", it's:
Status: 0x00
Mode: Standby
Full: 0
Wall: 0
Status code is directly from the hw chip:
0 - Standby
1 - Charge in progress
2 - Charge done
Mode and Full are just flags tracked by the charge script for its own use. Wall is whether wall charger has been detected.
Things to note:
The charger chip is programmed on script start. There's no error recovery. Chip resets to defaults on some error conditions.
This means in some circumstanced the charger chip can go back to its defaults, which are to charge the battery to 20-40% at a slow rate.
The logs written in /home/user/MyDocs/ can provide some hints to whether there has been a fault condition.
|
|
2011-05-21
, 18:04
|
|
Posts: 18 |
Thanked: 9 times |
Joined on Aug 2010
|
#238
|
USB sticks, mouse, and keyboard are working for me, but not my SD card reader (it does not show up as /dev/sd* and mount does not work). I get the following from dmesg:
Code:
[15168.828552] hub 1-0:1.0: hub_suspend [15168.828643] usb usb1: bus auto-suspend [15168.828674] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15168.828735] usb usb1: bus suspend fail, err -16 [15168.828765] hub 1-0:1.0: hub_resume [15168.828857] hub 1-0:1.0: port 1: status 0501 change 0000 [15168.828948] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15168.829010] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15168.953704] usb 1-1: new high speed USB device using musb_hdrc and address 36 [15169.078674] usb 1-1: device descriptor read/64, error -71 [15169.313018] usb 1-1: device descriptor read/64, error -71 [15169.547271] usb 1-1: new high speed USB device using musb_hdrc and address 37 [15169.672210] usb 1-1: device descriptor read/64, error -71 [15169.906768] usb 1-1: device descriptor read/64, error -71 [15170.141174] usb 1-1: new high speed USB device using musb_hdrc and address 38 [15170.562866] usb 1-1: device not accepting address 38, error -71 [15170.688079] usb 1-1: new high speed USB device using musb_hdrc and address 39 [15171.109710] usb 1-1: device not accepting address 39, error -71 [15171.109802] hub 1-0:1.0: unable to enumerate USB device on port 1 [15171.109832] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15171.109893] hub 1-0:1.0: port 1 enable change, status 00000501 [15173.262542] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1 [15173.828399] hub 1-0:1.0: hub_suspend [15173.828460] usb usb1: bus auto-suspend [15183.461425] slide (GPIO 71) is now closed [15199.992675] slide (GPIO 71) is now open [15257.087585] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2 [15259.161956] Forced hostmode error: no device attached [15259.162048] usb usb1: usb resume [15259.179992] hub 1-0:1.0: hub_resume [15259.180053] hub 1-0:1.0: port 1: status 0101 change 0001 [15259.289581] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15259.289642] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s [15259.414672] usb 1-1: new high speed USB device using musb_hdrc and address 40 [15259.539550] usb 1-1: device descriptor read/64, error -71 [15259.773956] usb 1-1: device descriptor read/64, error -71 [15260.008361] usb 1-1: new high speed USB device using musb_hdrc and address 41 [15260.133361] usb 1-1: device descriptor read/64, error -71 [15260.367706] usb 1-1: device descriptor read/64, error -71 [15260.602233] usb 1-1: new high speed USB device using musb_hdrc and address 42 [15261.023956] usb 1-1: device not accepting address 42, error -71 [15261.148925] usb 1-1: new high speed USB device using musb_hdrc and address 43 [15261.570648] usb 1-1: device not accepting address 43, error -71 [15261.570770] hub 1-0:1.0: unable to enumerate USB device on port 1 [15261.570800] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15261.570831] hub 1-0:1.0: port 1 enable change, status 00000501 [15263.828552] hub 1-0:1.0: hub_suspend [15263.828613] usb usb1: bus auto-suspend [15263.828643] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15263.828704] usb usb1: bus suspend fail, err -16 [15263.828735] hub 1-0:1.0: hub_resume [15263.828796] hub 1-0:1.0: port 1: status 0501 change 0000 [15263.828948] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15263.829010] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15263.953582] usb 1-1: new high speed USB device using musb_hdrc and address 44 [15264.078491] usb 1-1: device descriptor read/64, error -71 [15264.312957] usb 1-1: device descriptor read/64, error -71 [15264.547332] usb 1-1: new high speed USB device using musb_hdrc and address 45 [15264.672271] usb 1-1: device descriptor read/64, error -71 [15264.906860] usb 1-1: device descriptor read/64, error -71 [15265.141082] usb 1-1: new high speed USB device using musb_hdrc and address 46 [15265.562988] usb 1-1: device not accepting address 46, error -71 [15265.687896] usb 1-1: new high speed USB device using musb_hdrc and address 47 [15266.110015] usb 1-1: device not accepting address 47, error -71 [15266.110168] hub 1-0:1.0: unable to enumerate USB device on port 1 [15266.110229] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15266.110290] hub 1-0:1.0: port 1 enable change, status 00000501 [15268.828674] hub 1-0:1.0: hub_suspend [15268.828735] usb usb1: bus auto-suspend [15268.828796] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15268.828826] usb usb1: bus suspend fail, err -16 [15268.828857] hub 1-0:1.0: hub_resume [15268.828948] hub 1-0:1.0: port 1: status 0501 change 0000 [15268.829040] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15268.829101] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15268.953643] usb 1-1: new high speed USB device using musb_hdrc and address 48 [15269.079284] usb 1-1: device descriptor read/64, error -71 [15269.313049] usb 1-1: device descriptor read/64, error -71 [15269.547424] usb 1-1: new high speed USB device using musb_hdrc and address 49 [15269.672363] usb 1-1: device descriptor read/64, error -71 [15269.906799] usb 1-1: device descriptor read/64, error -71 [15270.141082] usb 1-1: new high speed USB device using musb_hdrc and address 50 [15270.562988] usb 1-1: device not accepting address 50, error -71 [15270.687927] usb 1-1: new high speed USB device using musb_hdrc and address 51 [15271.109924] usb 1-1: device not accepting address 51, error -71 [15271.110076] hub 1-0:1.0: unable to enumerate USB device on port 1 [15271.110137] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15271.110198] hub 1-0:1.0: port 1 enable change, status 00000501 [15273.828552] hub 1-0:1.0: hub_suspend [15273.828643] usb usb1: bus auto-suspend [15273.828674] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15273.828704] usb usb1: bus suspend fail, err -16 [15273.828735] hub 1-0:1.0: hub_resume [15273.828826] hub 1-0:1.0: port 1: status 0501 change 0000 [15273.828918] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15273.828979] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15273.953552] usb 1-1: new high speed USB device using musb_hdrc and address 52 [15274.078704] usb 1-1: device descriptor read/64, error -71 [15274.312988] usb 1-1: device descriptor read/64, error -71 [15274.547332] usb 1-1: new high speed USB device using musb_hdrc and address 53 [15274.672302] usb 1-1: device descriptor read/64, error -71 [15274.906799] usb 1-1: device descriptor read/64, error -71 [15275.141052] usb 1-1: new high speed USB device using musb_hdrc and address 54 [15275.562957] usb 1-1: device not accepting address 54, error -71 [15275.688049] usb 1-1: new high speed USB device using musb_hdrc and address 55 [15276.110015] usb 1-1: device not accepting address 55, error -71 [15276.110168] hub 1-0:1.0: unable to enumerate USB device on port 1 [15276.110229] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15276.110290] hub 1-0:1.0: port 1 enable change, status 00000501 [15278.828735] hub 1-0:1.0: hub_suspend [15278.828826] usb usb1: bus auto-suspend [15278.828857] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15278.828887] usb usb1: bus suspend fail, err -16 [15278.828918] hub 1-0:1.0: hub_resume [15278.829010] hub 1-0:1.0: port 1: status 0501 change 0000 [15278.829101] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15278.829162] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15278.953674] usb 1-1: new high speed USB device using musb_hdrc and address 56 [15279.078704] usb 1-1: device descriptor read/64, error -71 [15279.312988] usb 1-1: device descriptor read/64, error -71 [15279.547393] usb 1-1: new high speed USB device using musb_hdrc and address 57 [15279.672485] usb 1-1: device descriptor read/64, error -71 [15279.906860] usb 1-1: device descriptor read/64, error -71 [15280.141082] usb 1-1: new high speed USB device using musb_hdrc and address 58 [15280.562957] usb 1-1: device not accepting address 58, error -71 [15280.688568] usb 1-1: new high speed USB device using musb_hdrc and address 59 [15281.109954] usb 1-1: device not accepting address 59, error -71 [15281.110046] hub 1-0:1.0: unable to enumerate USB device on port 1 [15281.110076] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15281.110107] hub 1-0:1.0: port 1 enable change, status 00000501 [15283.828643] hub 1-0:1.0: hub_suspend [15283.828704] usb usb1: bus auto-suspend [15283.828735] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15283.828796] usb usb1: bus suspend fail, err -16 [15283.828826] hub 1-0:1.0: hub_resume [15283.828887] hub 1-0:1.0: port 1: status 0501 change 0000 [15283.828979] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15283.829040] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15283.953735] usb 1-1: new high speed USB device using musb_hdrc and address 60 [15284.078735] usb 1-1: device descriptor read/64, error -71 [15284.313079] usb 1-1: device descriptor read/64, error -71 [15284.547363] usb 1-1: new high speed USB device using musb_hdrc and address 61 [15284.672546] usb 1-1: device descriptor read/64, error -71 [15284.911956] usb 1-1: device descriptor read/64, error -71 [15285.143707] usb 1-1: new high speed USB device using musb_hdrc and address 62 [15285.562988] usb 1-1: device not accepting address 62, error -71 [15285.688232] usb 1-1: new high speed USB device using musb_hdrc and address 63 [15286.109802] usb 1-1: device not accepting address 63, error -71 [15286.109893] hub 1-0:1.0: unable to enumerate USB device on port 1 [15286.109924] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15286.109954] hub 1-0:1.0: port 1 enable change, status 00000501 [15288.828430] hub 1-0:1.0: hub_suspend [15288.828491] usb usb1: bus auto-suspend [15288.828491] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15288.828521] usb usb1: bus suspend fail, err -16 [15288.828521] hub 1-0:1.0: hub_resume [15288.828582] hub 1-0:1.0: port 1: status 0501 change 0000 [15288.828613] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15288.828643] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15288.953643] usb 1-1: new high speed USB device using musb_hdrc and address 64 [15289.078582] usb 1-1: device descriptor read/64, error -71 [15289.312957] usb 1-1: device descriptor read/64, error -71 [15289.547271] usb 1-1: new high speed USB device using musb_hdrc and address 65 [15289.672454] usb 1-1: device descriptor read/64, error -71 [15289.906860] usb 1-1: device descriptor read/64, error -71 [15290.141143] usb 1-1: new high speed USB device using musb_hdrc and address 66 [15290.562957] usb 1-1: device not accepting address 66, error -71 [15290.687866] usb 1-1: new high speed USB device using musb_hdrc and address 67 [15291.109710] usb 1-1: device not accepting address 67, error -71 [15291.109802] hub 1-0:1.0: unable to enumerate USB device on port 1 [15291.109832] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15291.109832] hub 1-0:1.0: port 1 enable change, status 00000501 [15293.828491] hub 1-0:1.0: hub_suspend [15293.828552] usb usb1: bus auto-suspend [15293.828552] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15293.828582] usb usb1: bus suspend fail, err -16 [15293.828582] hub 1-0:1.0: hub_resume [15293.828643] hub 1-0:1.0: port 1: status 0501 change 0000 [15293.828674] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15293.828704] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15293.953491] usb 1-1: new high speed USB device using musb_hdrc and address 68 [15294.078582] usb 1-1: device descriptor read/64, error -71 [15294.312927] usb 1-1: device descriptor read/64, error -71 [15294.547637] usb 1-1: new high speed USB device using musb_hdrc and address 69 [15294.672546] usb 1-1: device descriptor read/64, error -71 [15294.906646] usb 1-1: device descriptor read/64, error -71 [15295.141113] usb 1-1: new high speed USB device using musb_hdrc and address 70 [15295.562988] usb 1-1: device not accepting address 70, error -71 [15295.687927] usb 1-1: new high speed USB device using musb_hdrc and address 71 [15296.109832] usb 1-1: device not accepting address 71, error -71 [15296.109924] hub 1-0:1.0: unable to enumerate USB device on port 1 [15296.109954] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15296.109985] hub 1-0:1.0: port 1 enable change, status 00000501 [15298.828521] hub 1-0:1.0: hub_suspend [15298.828582] usb usb1: bus auto-suspend [15298.828582] musb_bus_suspend 2266: trying to suspend as a_host is_active=1 [15298.828613] usb usb1: bus suspend fail, err -16 [15298.828613] hub 1-0:1.0: hub_resume [15298.828674] hub 1-0:1.0: port 1: status 0501 change 0000 [15298.828704] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15298.828735] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [15298.954345] usb 1-1: new high speed USB device using musb_hdrc and address 72 [15299.078643] usb 1-1: device descriptor read/64, error -71 [15299.312988] usb 1-1: device descriptor read/64, error -71 [15299.547363] usb 1-1: new high speed USB device using musb_hdrc and address 73 [15299.672485] usb 1-1: device descriptor read/64, error -71 [15299.906921] usb 1-1: device descriptor read/64, error -71 [15300.141265] usb 1-1: new high speed USB device using musb_hdrc and address 74 [15300.563018] usb 1-1: device not accepting address 74, error -71 [15300.688140] usb 1-1: new high speed USB device using musb_hdrc and address 75 [15301.109802] usb 1-1: device not accepting address 75, error -71 [15301.109954] hub 1-0:1.0: unable to enumerate USB device on port 1 [15301.110015] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15301.110076] hub 1-0:1.0: port 1 enable change, status 00000501 [15302.943969] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1 [15303.828643] hub 1-0:1.0: hub_suspend [15303.828704] usb usb1: bus auto-suspend
|
|
2011-05-21
, 18:05
|
|
Posts: 18 |
Thanked: 9 times |
Joined on Aug 2010
|
#239
|
Also I tried to use an (unpowered) hub to use mouse and keyboard both with it and that did not work, I get the following from dmesg:
Any help would be appreciated. Thanks 
Code:
[15680.245086] wlan0: roaming signal from driver, sending LOWSIGNAL [15687.106628] wlan0: roaming signal from driver, sending HIGHSIGNAL [15738.547912] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2 [15739.313018] Forced hostmode error: no device attached [15739.313110] usb usb1: usb resume [15739.336486] hub 1-0:1.0: hub_resume [15739.336578] hub 1-0:1.0: port 1: status 0101 change 0001 [15739.445831] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000 [15739.445892] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s [15739.571563] usb 1-1: new high speed USB device using musb_hdrc and address 80 [15739.695953] usb 1-1: device descriptor read/64, error -71 [15739.930297] usb 1-1: device descriptor read/64, error -71 [15740.164733] usb 1-1: new high speed USB device using musb_hdrc and address 81 [15740.289581] usb 1-1: device descriptor read/64, error -71 [15740.523986] usb 1-1: device descriptor read/64, error -71 [15740.758239] usb 1-1: new high speed USB device using musb_hdrc and address 82 [15741.180267] usb 1-1: device not accepting address 82, error -71 [15741.305206] usb 1-1: new high speed USB device using musb_hdrc and address 83 [15741.727111] usb 1-1: device not accepting address 83, error -71 [15741.727233] hub 1-0:1.0: unable to enumerate USB device on port 1 [15741.727294] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [15741.727355] hub 1-0:1.0: port 1 enable change, status 00000501 [15742.515472] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1 [15743.828521] hub 1-0:1.0: hub_suspend [15743.828582] usb usb1: bus auto-suspend
|
|
2011-05-22
, 00:35
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#240
|
It MAY be the same problem cheve had with mounting - being too hasty. until i learned to click "VBUST ON" 2-3 seconds after plugging cable, and "Enumerate" after another 6-7 seconds, many times i get same errors.
Also, remember to always unplug device (be it HUB, stick, mouse, whatever) from N900 before trying to start from scratch. Cable and adapter can sit on N900, but nothing can be connected to them. You can connect anything only after setting speed (then, do not exceed 3-4 seconds before You click VBUS ON, but also don't do it 0.1 second after plugging device - not too late, not too early), otherwise you get exact same errors. At least, that is in my case, always, 100% reproduceable.
On side note, i would NOT recommend plugging and unplugging again cable direct from N900 when You want start "hostmod(d)ing" from scratch - it's better to unplug device/adapter from end of the cable. We don't want to stress too much our N900 USB port...
Also, remember to always unplug device (be it HUB, stick, mouse, whatever) from N900 before trying to start from scratch. Cable and adapter can sit on N900, but nothing can be connected to them. You can connect anything only after setting speed (then, do not exceed 3-4 seconds before You click VBUS ON, but also don't do it 0.1 second after plugging device - not too late, not too early), otherwise you get exact same errors. At least, that is in my case, always, 100% reproduceable.
On side note, i would NOT recommend plugging and unplugging again cable direct from N900 when You want start "hostmod(d)ing" from scratch - it's better to unplug device/adapter from end of the cable. We don't want to stress too much our N900 USB port...
| The Following User Says Thank You to Estel For This Useful Post: | ||
 |
| Tags |
| awesome!, bada rox, h-e-n hostmode, more noise |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 20:15.
it says no system file...
cn ny1 help???????