maemo.org - Talk - Only boots up in RD Mode

Page 1 of 4

Show 40 post(s) from this thread on one page

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

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

- - Only boots up in RD Mode (https://talk.maemo.org/showthread.php?t=63259)

mega	2010-10-02 18:49

Only boots up in RD Mode

N900 does not boot up in normal mode but boots up in R&D mode.

Normal Mode:
Phone comes on the and nokia logo fades away but does not restart

When charger in it keeps restarting

mega	2010-10-02 22:25

Re: N900 does not boot up but boots up in R&D Mode

And the battery does not charge

lew247

2010-10-02 22:29

Re: N900 does not boot up but boots up in R&D Mode

Remove the charger, remove the battery for a few minutes
Put the battery back in - DO NOT turn the phone on or even try to.
Plug the charger in, leave it to charge for a few hours before turning the phone on
even if it doesn't appear to be charging at first
It should be fine then.

mega	2010-10-03 11:12

Re: Only boots up in R&D Mode

Still not working

When I plug it in when its on it says Not Charging

mega	2010-10-06 16:24

Re: Only boots up in RD Mode

Help anyone only boots up in RD mode is gets stuck when I disable on start up.

jvollmann

2011-07-08 18:49

Re: Only boots up in RD Mode

Nobody could solve this?? I'm having this same issue, tried reflashing, enabling and disabling R&D mode, removing the battery for a whole day and NOTHING!! I appreciate any help..

TMavica

2011-07-08 18:51

Re: Only boots up in RD Mode

Have you try to reflash the kernel only??

jvollmann

2011-07-08 18:55

Re: Only boots up in RD Mode

Quote:

Originally Posted by TMavica (Post 1047256)

Have you try to reflash the kernel only??

Yes, I also tried only flashing the bootloader but still the same...

TMavica

2011-07-08 19:07

Re: Only boots up in RD Mode

Quote:

Originally Posted by jvollmann (Post 1047257)

Yes, I also tried only flashing the bootloader but still the same...

what have you do before this happen?

jvollmann

2011-07-08 19:19

Re: Only boots up in RD Mode

Quote:

Originally Posted by TMavica (Post 1047272)

what have you do before this happen?

I just bought it, it's a 3 month used phone. The guy who owned it told me that he ran out of battery a week ago. When he get to his house and tried to charge the battery, the device started with the booting loop issue.

As soon as I get the phone I reflashed the device but the problem of booting still persisted. Just booting in R&D mode makes it start..

TMavica

2011-07-08 19:22

Re: Only boots up in RD Mode

reflashed the emmc plus firmware ??

jvollmann

2011-07-08 19:33

Re: Only boots up in RD Mode

Quote:

Originally Posted by TMavica (Post 1047283)

reflashed the emmc plus firmware ??

Also tried that! Both procedures ended successfully but with no luck booting... (Flashing in different OS's: Windows Vista 32bits and Ubuntu 10.04 32bits), also flashing the FIASCO image first (without restarting) and then the VANILLA image...

TMavica

2011-07-08 19:47

Re: Only boots up in RD Mode

O..
you get cheated??
sorry, I cant help, reflash also nil help , really dont know

jvollmann

2011-07-08 19:54

Re: Only boots up in RD Mode

Quote:

Originally Posted by TMavica (Post 1047312)

O..
you get cheated??
sorry, I cant help, reflash also nil help , really dont know

Hahaha,, I hope not!

I think it can be fixed because it boots perfectly in R&D mode, so I don't think it's a hardware failure.

Thanks anyway!

Mentalist Traceur

2011-07-08 21:51

Re: Only boots up in RD Mode

Quote:

Originally Posted by jvollmann (Post 1047323)

Hahaha,, I hope not!

I think it can be fixed because it boots perfectly in R&D mode, so I don't think it's a hardware failure.

Thanks anyway!

You could install syslogd and use that to store up logs over a few posts. Then post them here so people can help you if you don't understand what the hell the logs are all about. (Also, uninstall syslogd after you're done logging, because it will over time fill up your rootfs space with logs. (Symlinking the log file out to /opt would defeat the purpose of logging for possible errors though - since /opt isn't mounted until some time into boot.)

Hurrian

2011-07-09 00:56

Re: Only boots up in RD Mode

The device is probably in no-usb-charging mode.
Anyways, unset the RD flags and try a cold flash.

Mentalist Traceur

2011-07-09 01:26

Re: Only boots up in RD Mode

Quote:

Originally Posted by Hurrian (Post 1047541)

The device is probably in no-usb-charging mode.
Anyways, unset the RD flags and try a cold flash.

What would no-usb-charging have to do with not being able to boot in normal mode, but being able to boot in rd mode?

If the device was really out of power, r&d mode wouldn't let it boot.

Estel

2011-07-09 01:49

Re: Only boots up in RD Mode

AFAIK R&D mode disables certain watchdogs + make keyboard blinking on "disk" activity - many people (including hawaii, from top of my head) are using it for everyday work with device. So, this MY not be tragic, but...

...but there IS certainly something wrong with the device, if it boot only that way [obvious statement]. My absolutely uneducated guess is that for some reasons, watchdog reset device into loop, and using R&D avoid watchdog. Ho ever, event that cause watchdog to reset in non-R&D mode still exist happily. If Mentalist idea about syslog doesn't help, I'm also out of ideas.

jvollmann

2011-07-09 04:01

Re: Only boots up in RD Mode

Hello everyone, I'm going to install syslog inmediately.. I will post the logs as soon as I can. I really appreciate your help, thanks!

jvollmann

2011-07-09 16:36

Re: Only boots up in RD Mode

Hi, I installed syslog using apt-get install sysklogd.. Where do I find the log files? is a .log extension file?

sethkha

2011-07-09 16:56

Re: Only boots up in RD Mode

Had the same (not exactly) issue. Formatted optfs from ubuntu. Then did a cold flash. Flashed with an image with backupmenu. Restored backups with backupmenu. Not sure about order or images.

jvollmann

2011-07-09 17:56

Re: Only boots up in RD Mode

Hello again.. Now I think it could be a battery monitor problem. When maemo starts up (in R&D mode) the battery life keeps low and after 5 minutes of use a notification appears telling "battery low" (altough the battery is fully charged --i use a nokia 5800--). However, I can use the phone for like 5 hours using wi-fi, web browser, app manager.
Minutes ago, I installed Nitdroid but when it's booting a red light starts blinking and then shuts down (the android desktop appears telling: "Shutting Down"). I read that this is because a BME problem.
What do you think?

jvollmann

2011-07-11 14:06

Re: Only boots up in RD Mode

update: I installed Meego 1.1 and it boots ok (a little slow but i think it's because my sd card is class 4). I tried to charge the battery when Meggo started up, the battery icon showed like it would be charging but the phone led didn't turn on or blink, after some time the phone turned off because the battery drained.

Estel

2011-07-11 14:47

Re: Only boots up in RD Mode

bq_27200 chip damaged? How do You charge battery anyway, using external charger?

jvollmann

2011-07-11 14:55

Re: Only boots up in RD Mode

Quote:

Originally Posted by Estel (Post 1048909)

bq_27200 chip damaged? How do You charge battery anyway, using external charger?

I charge it with a Nokia 5800... Do you know if there's any diagnostic tool/app (or a boot log file) to know if the chip is really damaged?

RobbieThe1st

2011-07-11 15:09

Re: Only boots up in RD Mode

Go install i2c-tools from extras-devel(ignore the warning).
Here's the charge-script used in backupmenu; should tell you something:

Code:

#/bin/bash

# Reset



#echo -n Reset...

#i2cset -y -m 0x80 2 0x6b 0x04 80

#echo -n Done. Sleep 1...

#sleep 1

#echo -n Done.



#echo "Charger: " $(cat /sys/devices/platform/musb_hdrc/charger)



# Disable charger for configuration:

i2cset -y 2 0x6b 0x01 0xcc # No limit, 3.4V weak threshold, enable term, charger disable





# Register 0x04

# 8: reset

# 4: 27.2mV  # charge current

# 2: 13.6mV

# 1: 6.8mV

# 8: N/A

# 4: 13.6mV # termination current

# 2: 6.8mV

# 1: 3.4mV

# 7-1250 6-1150 5-1050 4-950 3-850 2-750 1-650 0-550

# 7-400 6-350 5-300 4-250 3-200 2-150 1-100 0-50

i2cset -y -m 0xFF 2 0x6b 0x04 0x50;



# Register 0x02

# 8: .640 V

# 4: .320 V

# 2: .160 V

# 1: .080

# 8: .040

# 4: .020 (+ 3.5)

# 2: otg pin active at high (default 1)

# 1: enable otg pin

i2cset -y -m 0xfc 2 0x6b 0x02 0x8c; 

# 4.2 = 3.5 + .640 + .040 + .02 = 8c

# 4.16 = 3.5 + .640V + .020 = 84

# 4.1 = 3.5 + .320 + .160 + .08 + .04 = 78

# 4.0 = 3.5 + .320 + .160 + .02 = 64

# 3.9 = 3.5 + .320 + .080 = 50



# Register 0x1

# 8: 00 = 100, 01 = 500, 10 = 800mA

# 4: 11 = no limit

# 2: 200mV weak threshold default 1

# 1: 100mV weak treshold defsult 1 (3.4 - 3.7)

# 8: enable termination

# 4: charger disable

# 2: high imp mode

# 1: boost

i2cset -y 2 0x6b 0x01 0xc8; 

#0110 1011



# Register 0x00

# 8: Read:  OTG Pin Status

#    Write: Timer Reset

# 4: Enable Stat Pin

# 2: Stat : 00 Ready 01 In Progress

# 1:      : 10 Done  11 Fault

# 8: Boost Mode

# 4: Fault: 000 Normal 001 VBUS OVP 010 Sleep Mode 

# 2:        011 Poor input or Vbus < UVLO 

# 1:        100 Battery OVP 101 Thermal Shutdown

#           110 Timer Fault 111 NA

i2cset -y 2 0x6b 0x00 0x00; 



#echo -n "Charge parameters programmed. Sleep 1..."

sleep 1

#echo "Status: " $(i2cget -y 2 0x6b 0x00)

i2cset -y 2 0x6b 0x00 0x80 # timer reset

cat /sys/devices/platform/musb_hdrc/charger >/dev/null



# Initialize variables

THROTTLE=0

FULL=0

MODE="STANDBY"

WALLCHARGER=0



# Assuming a nice round number 20mOhm for bq27200 sense resistor

RS=20



get_nac ()

{

    NAC=$(i2cget -y 2 0x55 0x0c w)

    NAC=$(($NAC * 3570 / $RS / 1000))

}

get_rsoc ()

{

    RSOC=$(i2cget -y 2 0x55 0x0b)

    RSOC=$((RSOC))

}

get_volt ()

{

   VOLT=$(i2cget -y 2 0x55 0x08 w)

   VOLT=$(($VOLT))

}



STATUS=$(i2cget -y 2 0x6b 0x00)

while true ; do

   sleep 10; 

   STATUS=$(i2cget -y 2 0x6b 0x00)

   #echo $STATUS



   i2cset -y -m 0x80 2 0x6b 0x00 0x80; # timer reset

   get_nac

   get_rsoc

   get_volt



   if [ $MODE == "STANDBY" ] ; then

      if [ $STATUS == 0x10 ] || [ $STATUS == 0x90 ] ; then

         MODE="CHARGING"

         #echo $(date) "standby -> CHARGING. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log

         echo 60 > /sys/class/backlight/acx565akm/brightness

         WALLCHARGER=$(cat /sys/devices/platform/musb_hdrc/charger)

      fi

   fi

   if [ $MODE == "CHARGING" ] ; then

      if [ $STATUS == 0x00 ] ; then

         MODE="STANDBY"

         echo 15 > /sys/class/backlight/acx565akm/brightness

         #echo $(date) "charging -> STANDBY. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log

         WALLCHARGER=0

         # This will stop USB from eating power as long as you haven't plugged it into a PC

         echo 0 > /sys/devices/platform/musb_hdrc/connect

      fi

   fi



   if [ $STATUS == 0xa0 ] && [ $FULL == 0 ] ; then

      #echo "Charge done"

      #echo $(date) "FULL: " $NAC "mAh" >> /home/user/MyDocs/charger.log

      FULL=1

   fi

   if [ $STATUS == 0x00 ] && [ $FULL == 1 ] ; then

      FULL=0

   fi

   echo Status: $STATUS Mode: $MODE Full: $FULL WallCharger: $WALLCHARGER Battery Voltage: $VOLT NAC: $NAC Battery level: $RSOC %

done

Save it as charge.sh (anywhere but mydocs/sd) and run "chmod +x /path/to/charge.sh".
Then run it. Every ~10 or so seconds, you'll get a message telling what's going on.

jvollmann

2011-07-11 15:21

Re: Only boots up in RD Mode

Thanks. I will post the log later..

Mentalist Traceur

2011-07-11 22:03

Re: Only boots up in RD Mode

To elaborate on Estel's previous post, not only Hawaii, but MohammadAG and I also run our N900s in R&D mode regularly. If you disable the keyboard flickering battery life should be identical.

The only difference, depending on what flags you set, is that sometimes your device might hang instead of spontaneously reboot (as in, some deep system process will crash and normally watchdogs or lifeguard reset would reboot the device - with those disabled, if you choose to do so, the device won't reboot itself during some of those crashes and sometimes you have to pull the battery if it's something important that crashes. The advantage is that sometimes stuff will crash and then restart and while you notice it, your device doesn't reboot on you, which is nice, and the "crucial" process that the system supposedly had to reboot for a lack of just restarts and the device keeps working. Honestly even when it hangs and has to be rebooted/battery-pulled, I MUCH prefer to do that than have the device spontaneously turn off on me. One is just irksome, the other is like a slap in the face with barb wire and poison ivy tangled together.

jvollmann

2011-07-11 22:44

Re: Only boots up in RD Mode

Quote:

Originally Posted by Mentalist Traceur (Post 1049167)

Ok, I get it,,, I haven't had any problems running in R&D mode actually.
There are only two things that bothers me: 1)I can't charge the battery and, 2) I can't run Nitdroid.

Is there any "hack"to disable or trick the battery monitor?

PS. I will post the log from i2c-tools in a couple of minutes

jvollmann

2011-07-11 23:28

Re: Only boots up in RD Mode

Also tried with: modprobe bq27x00_battery, the results were all 0 but the voltage, current, temp and design:

cat /sys/class/power_supply/bq27200-0/capacity
0
cat /sys/class/power_supply/bq27200-0/charge_full
0
cat /sys/class/power_supply/bq27200-0/charge_now
0
cat /sys/class/power_supply/bq27200-0/time_to_empty_avg
0
cat /sys/class/power_supply/bq27200-0/time_to_empty_now
0
cat /sys/class/power_supply/bq27200-0/time_to_full_now
0

cat /sys/class/power_supply/bq27200-0/charge_full_design
2056320

Estel

2011-07-12 00:00

Re: Only boots up in RD Mode

Just little addition to what Mentalist said - AFAIK device hanging totally instead of rebooting has one disadvantage - possible filesystem corruptions. Watchdogs tends to unmount filesystem before rebooting, just like bme does (#fixme if I'm wrong).

Anyway, especially this line:

cat /sys/class/power_supply/bq27200-0/charge_full_design
0

...makes me wonder, if Your ID pin of battery is even connected/recognized? That could be source of problems, BUT - (another AFAIK) bme turns device on in < 1 second when unable to probe ID pin. I never heard that R&D mode disables this behavior - can someone running on R&D confirm/deny this?

And, wasn't temperature also probed on ID pin? :confused:

It's VERY strange all together. could other people, reporting there "same issues" do similar cat probing? I think first of all, we need to check if it's "reproduceable" problem, that may hit some devices, or jvollmann's troubles are unique, and other doesn't share same symptoms.

From top of my head i would still say "damaged bq_27200 chip", but somehow voltage and temp is probed correctly... Huge WTF.

jvollmann

2011-07-12 00:19

Re: Only boots up in RD Mode

Quote:

Originally Posted by RobbieThe1st (Post 1048925)

Go install i2c-tools from extras-devel(ignore the warning).
Here's the charge-script used in backupmenu; should tell you something:

Code:

#/bin/bash

# Reset



#echo -n Reset...

#i2cset -y -m 0x80 2 0x6b 0x04 80

#echo -n Done. Sleep 1...

#sleep 1

#echo -n Done.



#echo "Charger: " $(cat /sys/devices/platform/musb_hdrc/charger)



# Disable charger for configuration:

i2cset -y 2 0x6b 0x01 0xcc # No limit, 3.4V weak threshold, enable term, charger disable





# Register 0x04

# 8: reset

# 4: 27.2mV  # charge current

# 2: 13.6mV

# 1: 6.8mV

# 8: N/A

# 4: 13.6mV # termination current

# 2: 6.8mV

# 1: 3.4mV

# 7-1250 6-1150 5-1050 4-950 3-850 2-750 1-650 0-550

# 7-400 6-350 5-300 4-250 3-200 2-150 1-100 0-50

i2cset -y -m 0xFF 2 0x6b 0x04 0x50;



# Register 0x02

# 8: .640 V

# 4: .320 V

# 2: .160 V

# 1: .080

# 8: .040

# 4: .020 (+ 3.5)

# 2: otg pin active at high (default 1)

# 1: enable otg pin

i2cset -y -m 0xfc 2 0x6b 0x02 0x8c; 

# 4.2 = 3.5 + .640 + .040 + .02 = 8c

# 4.16 = 3.5 + .640V + .020 = 84

# 4.1 = 3.5 + .320 + .160 + .08 + .04 = 78

# 4.0 = 3.5 + .320 + .160 + .02 = 64

# 3.9 = 3.5 + .320 + .080 = 50



# Register 0x1

# 8: 00 = 100, 01 = 500, 10 = 800mA

# 4: 11 = no limit

# 2: 200mV weak threshold default 1

# 1: 100mV weak treshold defsult 1 (3.4 - 3.7)

# 8: enable termination

# 4: charger disable

# 2: high imp mode

# 1: boost

i2cset -y 2 0x6b 0x01 0xc8; 

#0110 1011



# Register 0x00

# 8: Read:  OTG Pin Status

#    Write: Timer Reset

# 4: Enable Stat Pin

# 2: Stat : 00 Ready 01 In Progress

# 1:      : 10 Done  11 Fault

# 8: Boost Mode

# 4: Fault: 000 Normal 001 VBUS OVP 010 Sleep Mode 

# 2:        011 Poor input or Vbus < UVLO 

# 1:        100 Battery OVP 101 Thermal Shutdown

#           110 Timer Fault 111 NA

i2cset -y 2 0x6b 0x00 0x00; 



#echo -n "Charge parameters programmed. Sleep 1..."

sleep 1

#echo "Status: " $(i2cget -y 2 0x6b 0x00)

i2cset -y 2 0x6b 0x00 0x80 # timer reset

cat /sys/devices/platform/musb_hdrc/charger >/dev/null



# Initialize variables

THROTTLE=0

FULL=0

MODE="STANDBY"

WALLCHARGER=0



# Assuming a nice round number 20mOhm for bq27200 sense resistor

RS=20



get_nac ()

{

    NAC=$(i2cget -y 2 0x55 0x0c w)

    NAC=$(($NAC * 3570 / $RS / 1000))

}

get_rsoc ()

{

    RSOC=$(i2cget -y 2 0x55 0x0b)

    RSOC=$((RSOC))

}

get_volt ()

{

   VOLT=$(i2cget -y 2 0x55 0x08 w)

   VOLT=$(($VOLT))

}



STATUS=$(i2cget -y 2 0x6b 0x00)

while true ; do

   sleep 10; 

   STATUS=$(i2cget -y 2 0x6b 0x00)

   #echo $STATUS



   i2cset -y -m 0x80 2 0x6b 0x00 0x80; # timer reset

   get_nac

   get_rsoc

   get_volt



   if [ $MODE == "STANDBY" ] ; then

      if [ $STATUS == 0x10 ] || [ $STATUS == 0x90 ] ; then

         MODE="CHARGING"

         #echo $(date) "standby -> CHARGING. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log

         echo 60 > /sys/class/backlight/acx565akm/brightness

         WALLCHARGER=$(cat /sys/devices/platform/musb_hdrc/charger)

      fi

   fi

   if [ $MODE == "CHARGING" ] ; then

      if [ $STATUS == 0x00 ] ; then

         MODE="STANDBY"

         echo 15 > /sys/class/backlight/acx565akm/brightness

         #echo $(date) "charging -> STANDBY. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log

         WALLCHARGER=0

         # This will stop USB from eating power as long as you haven't plugged it into a PC

         echo 0 > /sys/devices/platform/musb_hdrc/connect

      fi

   fi



   if [ $STATUS == 0xa0 ] && [ $FULL == 0 ] ; then

      #echo "Charge done"

      #echo $(date) "FULL: " $NAC "mAh" >> /home/user/MyDocs/charger.log

      FULL=1

   fi

   if [ $STATUS == 0x00 ] && [ $FULL == 1 ] ; then

      FULL=0

   fi

   echo Status: $STATUS Mode: $MODE Full: $FULL WallCharger: $WALLCHARGER Battery Voltage: $VOLT NAC: $NAC Battery level: $RSOC %

done

Save it as charge.sh (anywhere but mydocs/sd) and run "chmod +x /path/to/charge.sh".
Then run it. Every ~10 or so seconds, you'll get a message telling what's going on.

I downloaded i2c-tools and then runned the script but didn't show up anything:

# chmod +x /home/user/MyDocs/charge.sh
#

Estel

2011-07-12 00:25

Re: Only boots up in RD Mode

From output You provided, it seems that You only chmod it. Now, You need to run it.

Also, you placed it in MyDosc, while Robbie clearly asked You to place it anywhere EXCEPT MyDocs or vFAT partition of microSD. vFAT is set as noexec on N900.

[off-topic]Robbie, it's same script that shadowjk created for HEN? If that, is it latest version?[/off-topic]

jvollmann

2011-07-12 00:26

Re: Only boots up in RD Mode

Quote:

Originally Posted by Estel (Post 1049220)

I didn't type the infos wich weren't zero, here they are:

# cat /sys/class/power_supply/bq27200-0/temp
# 333
#cat /sys/class/power_supply/bq27200-0/voltage_now
# 3858000
# cat /sys/class/power_supply/bq27200-0/current_now
# 168147

It's all very weird,,, hope all the community can help!

Estel

2011-07-12 00:29

Re: Only boots up in RD Mode

non-zero outputs are perfectly fine - 168 mAh current @ probing moment, 3,858 V battery (~50 %) and 33,3 Celsius scale battery temperature.

Also, we posted on almost very same moment, so please check my last post in case You missed it.

jvollmann

2011-07-12 03:21

Re: Only boots up in RD Mode

Quote:

Originally Posted by Estel (Post 1049227)

You're right.. I moved the file (I copied exactly the same code that Robbie posted) to /home directory. However:

# chmod +x /home/charge.sh
# ./charge.sh
: not found line 3:
:not found line 9:
.
.
.
/ 1000 / 20 line 88: syntax error: 0x0000

I checked i2c-tools just in case I forgot to install but it is installed.

jvollmann

2011-07-12 03:28

Re: Only boots up in RD Mode

Quote:

Originally Posted by Estel (Post 1049220)

I'm sorry Estel.. I mistyped this line:

"cat /sys/class/power_supply/bq27200-0/charge_full_design
0"

the actual value is: 2056320, i missed that!

I know that confused you but I wrote it from the phone's terminal to the pc and thought that was also 0...

About other people with similar problems: I wrote a private message to @mega (the guy who started this thread), and he told me that he solved the problem taking the phone to a nokia center. I also wrote on quokka's thread: http://talk.maemo.org/showthread.php...03#post1049103 , and asked him to try R&D mode to see if he has similar issues.

jvollmann

2011-07-12 18:04

Re: Only boots up in RD Mode

Just to know (correct me if i'm wrong):

The problem with restart loop is that the device won't start up because the battery charge is low (or the device "thinks" is low, as it's my case).

I guess that this step is skipped on R&D mode and that's why it can boot perfectly when one enables it.

Estel

2011-07-12 18:23

Re: Only boots up in RD Mode

Not for sure. Info you get from bq_27200 module is read-only data, independent from bme (battery monitor entity), which MAY or MAY NOT think the same - unfortunately, AFAIK we can't check this, thank to Nokia closed source bme (curse them 1000 times for that, for MANY reasons).

So, ID PIN is definitely probed correctly. Ho ever, at least bq_module think, that battery capacity at full charge is still 0 - this may be symptom of problem, but may also mean that bq module haven't had a chance to perform internal calibration of values (which shouldn't cause the problem on itself).

I think You could try 2 things, independent from each other:

1. Flash some framebuffer kernel, and see on which point normal boot-up fails

2. In R&D mode, install HEN + shadowjk charge script (this one surely work outside backupmenu) - You can find it in HEN thread (normally, it's used to charge while USB hostmode. Then, monitor voltage using bq_27200 module, and when it's close to 3,300V, enable HEN (this is easiest way to stop bme without risk of restart after 32 seconds, ho ever may be also possible by executing "kill bme" from terminal as root - I don't know if it triggers restart after 32 seconds in R&D also, so using HEN is 100% sure and won't hurt in any case), then wait for voltage to drop lower than 3,200 V. Then, quickly enable shadowjk's charge script, and charge it to the full (without disabling HEN!). After charge cycle is done, check again if charge_full is still reported as 0 by bq_27200.

Explanation:
bq_27200 module perform "learning cycle" (referred by me earlier in this post, as "calibration of internal values") IF voltage drops below 3,248 AND device doesn't shut down before being charged to 100%. Unfortunately, bme shuts down device @ ~3,200 (little lower), so it's hardly to ever happen. That may be (or may not) be the cause, why Your charge_full is reporting 0.

Doing that, we at least check it all bq_27200 reports can be correct - this way, it's most unlikely that bq_27200 chip is damaged. Still, nothing sure for 100%, but at least we can filter out one possible symptom.

jvollmann

2011-07-12 19:03

Re: Only boots up in RD Mode

Where can I download a "framebuffer kernel"?

I read about "jrBME" that should replace BME but activity percentile is 0%. The project was registered on 2010-06!!

Well, I'm going to try these options and I'll let you know how it works.
Thanks

All times are GMT. The time now is 21:09.

Page 1 of 4

Next >

Last »

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8