09-30-2017, 11:39 AM
|
#1 |
|
Member
  Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
PW2 Repair Code 0 after a few reboots
Sure enough, after the warranty on my PW2 expired, it started experiencing more and more frequent Repair Code 0s. Holding down the button & rebooting it usually solved it, until it didn't. Thanks to geekmaster's excellent diagram I built myself a 1.8v TTL shifter and consoled in. The boot log looked something like this:
Code:
U-Boot 2009.08-lab126 (Dec 30 2013 - 10:54:52) CPU: Freescale i.MX6 family TO0.0 at 996 MHz Temperature: 29 C, calibration data 0x5654e35f mx6sl pll1: 996MHz mx6sl pll2: 528MHz mx6sl pll3: 480MHz mx6sl pll8: 50MHz ipg clock : 66000000Hz ipg per clock : 66000000Hz uart clock : 80000000Hz cspi clock : 60000000Hz ahb clock : 132000000Hz axi clock : 198000000Hz emi_slow clock: 22000000Hz ddr clock : 396000000Hz usdhc1 clock : 198000000Hz usdhc2 clock : 198000000Hz usdhc3 clock : 198000000Hz usdhc4 clock : 198000000Hz MMC: FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2 Board: Pinot WFO 2GB Boot Reason: [ POR ] Boot Device: NAND Board Id: 02E22011XXXXXHIO S/N: B0DXXXXXXXXXXC3T I2C: ready DRAM: 256 MB Using default environment In: serial Out: serial Err: serial Quick Memory Test 0x80000000, 0xfff0000 POST done in 59 ms Battery voltage: 4065 mV Hit any key to stop autoboot: 1 0 ## Booting kernel from Legacy Image at 80800000 ... Image Name: Linux-3.0.35-lab126 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2426044 Bytes = 2.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... [ 0.095368] No Legacy reboot reason code to print [ 0.271361] LPDDR2 MfgId: 0x1 [Samsung] [ 0.275222] [ 0.275225] just text: vaddr 0xc011e9bc, va 0xc011e200 pa 0x801000c3 attr 0x6 [ 0.283710] [ 0.283714] nmx6sl_wfi_iram: vaddr 0xd081a000, va 0xd081a200 pa 0x902043 attr 0x2 [ 0.292696] [ 0.292699] mx6sl_ddr: vaddr 0xd0852000, va 0xd0852200 pa 0x903043 attr 0x2 [ 0.301157] [ 0.301160] mx6sl_iomux: vaddr 0xf40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149 [ 0.310045] [ 0.310047] ANATOP: vaddr 0xf40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149 [ 0.318506] [ 0.318509] CCM: vaddr 0xf40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149 [ 0.326706] [ 0.326708] MMDC_P0: vaddr 0xf41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149 [ 0.335253] [ 0.335256] L2: vaddr 0xf2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149 [ 0.343279] [ 0.343282] arm perif: vaddr 0xf2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149 [ 0.370543] max77696-adc max77696-adc.0: adc conversion timed out 3.0.35-lab126 #1 Wed Apr 23 01:26:01 PDT 2014 armv7l Press [ENTER] for recovery menu... 0 //-\|/-\|/-/-\|/-\|/-/-\|/- To resolve this, I entered diag mode, dropped to shell, formatted mmcblk0p1 with mkfs, loaded the 5.4.3.2 firmware bin onto the FAT partition, and did U to launch an update. (Note: 5.4.3.2 was the previous firmware as well, I never updated it beyond that revision). This worked, and I was able to boot up successfully. I installed the jailbreak, KUAL, and a few extensions (KOReader, USBNet, kterm, gawk, BatteryStatus, and leafpad). Reboots proceeded as normal throughout this time. I thought all was well, so I removed the serial hookup. Big mistake. Upon the next reboot, Repair Code 0 once more. I held down the button and had a successful reboot. The next one once more resulted in Repair Code 0, as did all subsequent reboots. Now I'm back where I started. Back to the serial hookup! The above log is identical to what I'm seeing now. What am I doing wrong? SEVERAL EDITS: This message keeps popping up in the log, any relevance? Code:
[ 3249.149939] max77696-adc max77696-adc.0: adc conversion timed out [ 3249.169930] max77696-adc max77696-adc.0: adc conversion timed out 1) It was charged on a fastcharger, pumping over 1A into it (I didn't put an ammeter in line with it but it's a 2A charger and I noticed it charged very rapidly). 2) Once charged, the charger would cut out and the Kindle would drain to zero over the course of about a week (left alone with no usage). Upon recharge, it would boot up fresh. This happened multiple times before the issue started cropping up. Seeing the above errors makes me wonder if this could be related to the power management IC, however I'm not sure how to proceed further on the diag side. It seems to charge the battery well, and reports its charge level appropriately both in fastboot and (while it was running) in the OS. I have also tried a different battery as I suspected the charging ordeals it went through could've damaged it, with identical outcomes. It's worth noting that these messages disappear when the Kindle OS is actually running. No idea in diag mode, will test now. Sure enough, diag mode: Code:
[ 62.032521] max77696-adc max77696-adc.0: adc conversion timed out [ 62.038790] [ 62.038793] ADC value out of thermistor range! setting display temp to 43 deg C [ 122.172461] max77696-adc max77696-adc.0: adc conversion timed out [ 122.192473] max77696-adc max77696-adc.0: adc conversion timed out [ 122.198745] [ 122.198748] ADC value out of thermistor range! setting display temp to 43 deg C Hmm.. based on knc1's comment it's hanging on a user storage reformat. I have no issue leaving it on a charger for a few days, if that'll actually resolve the issue. Going into the recovery menu in diags (trying to get into it in main doesn't register, goes straight into the "spinning" character sequence), I ran an erase mmc0, partition initialize, and firmware reflash. I also formatted mmcblk0p3. Upon reboot, back to "Your Kindle Needs Repair", but this time without any error codes, nor the DSN - yet back to the "spinning" sequence. I've placed it on a USB ammeter and am leaving it for a few days. Right now battery's at 80%/about 4V and it's not drawing any current from USB. Serial output's of course being logged. Fingers crossed. Last edited by varu; 09-30-2017 at 02:04 PM. |
|
|
|
09-30-2017, 07:42 PM
|
#2 | ||
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Leaving it on a charger will not repair the damage done by the "Erase All" command. Quote:
The Kindle has a battery management chip which includes charge control. You can plug the Kindle into the Hoover dam and it will still not charge at any rate other than what the battery management chip allows. Those amperage rating numbers on a source device is its maximum designed output. It is not the output that it "forces" the destination to absorb. We have threads here on how to recover from "Erase All" - use them. |
||
|
|
|
| Advert | |
|
|
|
09-30-2017, 08:51 PM
|
#3 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
OK, I've reflashed the main & diags kernels, reflashed the diags partition, and have access to diags once more. The first diags boot reformatted the /var/local partition as part of the boot process. I essentially followed the instructions in the new eMMC thread minus the uboot portions - everything checked out. Upon loading update_kindle_5.4.3.2.bin (which flashes successfully) and rebooting into main, it's once again sitting at the "spinner". What should I do next?
Last edited by varu; 09-30-2017 at 08:54 PM. |
|
|
|
|
09-30-2017, 11:37 PM
|
#4 | |
|
Just a Yellow Smiley.
Posts: 19,161
Karma: 83862859
Join Date: Jul 2015
Location: Texas
Device: K4, K5, fire, kobo, galaxy
|
Quote:
|
|
|
|
|
|
10-01-2017, 12:49 AM
|
#5 |
|
Guru
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
|
I don't know much about this flashing business, but I do know this.
I don't think it will be helpful, but I like to share. On my broken kindle ( with no screen ), when I get the spinner, typing a single / restarts the kindle. Good Luck. |
|
|
|
| Advert | |
|
|
|
10-01-2017, 12:59 AM
|
#6 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
Thank you coplate, I didn't know this and it was quite helpful in getting the kernel boot log (which was not otherwise printed out, although I managed to get a near identical readout by booting using the diags kernel). It looks like this:
Code:
U-Boot 2009.08-lab126 (Apr 23 2014 - 01:01:24) CPU: Freescale i.MX6 family TO0.0 at 996 MHz Temperature: 30 C, calibration data 0x5654e35f mx6sl pll1: 996MHz mx6sl pll2: 528MHz mx6sl pll3: 480MHz mx6sl pll8: 50MHz ipg clock : 66000000Hz ipg per clock : 66000000Hz uart clock : 80000000Hz cspi clock : 60000000Hz ahb clock : 132000000Hz axi clock : 198000000Hz emi_slow clock: 22000000Hz ddr clock : 396000000Hz usdhc1 clock : 198000000Hz usdhc2 clock : 198000000Hz usdhc3 clock : 198000000Hz usdhc4 clock : 198000000Hz MMC: FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2 Board: Pinot WFO 2GB Boot Reason: [ POR ] Boot Device: NAND Board Id: XXXX S/N: XXXXXX I2C: ready DRAM: 256 MB Using default environment In: serial Out: serial Err: serial Quick Memory Test 0x80000000, 0xfff0000 POST done in 59 ms Battery voltage: 3868 mV Hit any key to stop autoboot: 0 ## Booting kernel from Legacy Image at 80800000 ... Image Name: Linux-3.0.35-lab126 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2426044 Bytes = 2.3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... [ 0.095374] [ 0.265782] LPDDR2 MfgId: 0x1 [Samsung] [ 0.269678] [ 0.269681] just text: vaddr 0xc011e9bc, va 0xc011e200 pa 0x801000c3 attr 0x6 [ 0.278148] [ 0.278151] nmx6sl_wfi_iram: vaddr 0xd081a000, va 0xd081a200 pa 0x902043 attr 0x2 [ 0.287122] [ 0.287124] mx6sl_ddr: vaddr 0xd0852000, va 0xd0852200 pa 0x903043 attr 0x2 [ 0.295583] [ 0.295585] mx6sl_iomux: vaddr 0xf40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149 [ 0.304478] [ 0.304481] ANATOP: vaddr 0xf40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149 [ 0.312939] [ 0.312941] CCM: vaddr 0xf40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149 [ 0.321138] [ 0.321140] MMDC_P0: vaddr 0xf41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149 [ 0.329685] [ 0.329688] L2: vaddr 0xf2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149 [ 0.337710] [ 0.337713] arm perif: vaddr 0xf2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149 [ 0.367437] max77696-adc max77696-adc.0: adc conversion timed out [ 0.427948] max77696-adc max77696-adc.0: adc conversion timed out 3.0.35-lab126 #1 Wed Apr 23 01:26:01 PDT 2014 armv7l Press [ENTER] for recovery menu... 0 /|/ === kernel printk buffer (17617 bytes) === <5>[ 0.000000] Linux version 3.0.35-lab126 (jenkins-official@sjc10-jbuild10) (collect2: ld returned 1 exit status) #1 Wed Apr 23 01:26:01 PDT 2014 <4>[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d <4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache <4>[ 0.000000] Machine: Freescale i.MX 6SoloLite based Wario Board <6>[ 0.000000] Will try to place printk log at 8fffc000 <4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback <6>[ 0.000000] CPU identified as i.MX6SoloLite, silicon rev 1.2 <7>[ 0.000000] On node 0 totalpages: 65536 <7>[ 0.000000] free_area_init_node: node 0, pgdat c04e0f2c, node_mem_map c2000000 <7>[ 0.000000] DMA zone: 64 pages used for memmap <7>[ 0.000000] DMA zone: 0 pages reserved <7>[ 0.000000] DMA zone: 8128 pages, LIFO batch:0 <7>[ 0.000000] Normal zone: 448 pages used for memmap <7>[ 0.000000] Normal zone: 56896 pages, LIFO batch:15 <7>[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 <7>[ 0.000000] pcpu-alloc: [0] 0 <4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 <5>[ 0.000000] Kernel command line: rootwait log_pos_goal=0x8fffc000 console=ttymxc0,115200 root=/dev/mmcblk0p1 ro ip=off quiet video=mxcepdcfb:E60,bpp=8,x_mem=3M <4>[ 0.000000] Prink buffer will be relocated to physical address: 8fff2000 <6>[ 0.000000] log_buf_len: 32768 <6>[ 0.000000] early log buf free: 31341(95%) <6>[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes) <6>[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) <6>[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) <6>[ 0.000000] Memory: 256MB = 256MB total <5>[ 0.000000] Memory: 254640k/254640k available, 7504k reserved, 0K highmem <5>[ 0.000000] Virtual kernel memory layout: <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) <5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) <5>[ 0.000000] DMA : 0xfde00000 - 0xffe00000 ( 32 MB) <5>[ 0.000000] vmalloc : 0xd0800000 - 0xf2000000 ( 536 MB) <5>[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) <5>[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) <5>[ 0.000000] .init : 0xc0008000 - 0xc010c000 (1040 kB) <5>[ 0.000000] .text : 0xc010c000 - 0xc04ae000 (3720 kB) <5>[ 0.000000] .data : 0xc04ae000 - 0xc04e1a60 ( 207 kB) <5>[ 0.000000] .bss : 0xc04e1a84 - 0xc05072a0 ( 151 kB) <6>[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 <6>[ 0.000000] NR_IRQS:624 <6>[ 0.000000] MXC GPIO hardware <6>[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms <6>[ 0.000000] arm_max_freq=1GHz <6>[ 0.000000] MXC_Early serial console at MMIO 0x2020000 (options '115200') <6>[ 0.000000] bootconsole [ttymxc0] enabled <6>[ 0.000000] Console: colour dummy device 80x30 <6>[ 0.000267] Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896) <6>[ 0.060112] pid_max: default: 32768 minimum: 301 <6>[ 0.060375] Mount-cache hash table entries: 512 <6>[ 0.060736] CPU: Testing write buffer coherency: ok <6>[ 0.060877] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available <6>[ 0.067851] print_constraints: dummy: <6>[ 0.068018] NET: Registered protocol family 16 <6>[ 0.072030] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal <6>[ 0.072324] print_constraints: vddcore: 725 <--> 1300 mV at 1475 mV fast normal <6>[ 0.072625] print_constraints: vddsoc: 725 <--> 1300 mV at 1475 mV fast normal <6>[ 0.072924] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal <6>[ 0.073263] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal <6>[ 0.073574] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal <4>[ 0.075164] LAB126 Board id - XXXXXX <6>[ 0.079361] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers. <6>[ 0.079375] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step. <6>[ 0.079389] hw-breakpoint: maximum watchpoint size is 4 bytes. <6>[ 0.079407] L310 cache controller enabled <6>[ 0.079418] l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02030000, Cache size: 262144 B <6>[ 0.087864] bio: create slab <bio-0> at 0 <6>[ 0.091693] max77696> regulator init <6>[ 0.092595] spi_imx imx6q-ecspi.0: probed <6>[ 0.092966] usbcore: registered new interface driver usbfs <6>[ 0.093083] usbcore: registered new interface driver hub <6>[ 0.093219] usbcore: registered new device driver usb <4>[ 0.095345] Reboot Reason - Metric Framework Reporting <6>[ 0.095360] kernel: kernel_metric_generic,0,counter,event_recorder,ercflags,SFT_PRSTRT,1, <4>[ 0.095368] Reboot Reason - Legacy Metric Reporting <3>[ 0.095374] <6>[ 0.098444] MAX77696 TOPSYS 1.0.0 Installed <6>[ 0.101346] max77696-gpio max77696-gpio.0: gpio#0 -- -- func-0 in <6>[ 0.102826] max77696-gpio max77696-gpio.0: gpio#1 -- -- func--1 in <6>[ 0.104299] max77696-gpio max77696-gpio.0: gpio#3 -- -- func-0 in <6>[ 0.106162] MAX77696 GPIO Driver 1.0.0 Installed <4>[ 0.107103] buck mode: 4 <4>[ 0.107847] buck mode: 4 <6>[ 0.108796] print_constraints: max77696_buck1: 900 <--> 1300 mV at 1250 mV fast normal idle standby <4>[ 0.109337] buck mode: 4 <6>[ 0.110364] print_constraints: max77696_buck1dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby <4>[ 0.110935] buck mode: 4 <4>[ 0.111678] buck mode: 4 <6>[ 0.112625] print_constraints: max77696_buck2: 900 <--> 1300 mV at 1200 mV fast normal idle standby <4>[ 0.113148] buck mode: 4 <6>[ 0.114099] print_constraints: max77696_buck2dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby <6>[ 0.114638] print_constraints: max77696_buck3: 600 <--> 3387 mV at 1300 mV fast normal idle standby <4>[ 0.115349] buck mode: 4 <4>[ 0.116091] buck mode: 4 <6>[ 0.116832] print_constraints: max77696_buck4: 1200 mV fast normal idle standby <4>[ 0.117357] buck mode: 4 <6>[ 0.118307] print_constraints: max77696_buck5: 600 <--> 3387 mV at 1800 mV fast normal idle standby <4>[ 0.118839] buck mode: 4 <6>[ 0.119787] print_constraints: max77696_buck6: 600 <--> 3387 mV at 3200 mV fast normal idle standby <6>[ 0.119827] MAX77696 Buck Regulators Driver 1.0.1 Installed <6>[ 0.120724] print_constraints: max77696_ldo1: 800 <--> 3950 mV at 3300 mV normal idle standby <6>[ 0.121290] print_constraints: max77696_ldo2: 800 <--> 3950 mV at 3000 mV normal idle standby <6>[ 0.121844] print_constraints: max77696_ldo3: 800 <--> 3950 mV at 2500 mV normal idle standby <6>[ 0.122391] print_constraints: max77696_ldo4: 800 <--> 2375 mV at 1800 mV normal idle standby <6>[ 0.122924] print_constraints: max77696_ldo5: 800 <--> 2375 mV at 1800 mV normal idle standby <6>[ 0.123483] print_constraints: max77696_ldo6: 800 <--> 3950 mV at 3200 mV normal idle standby <6>[ 0.124036] print_constraints: max77696_ldo7: 800 <--> 3950 mV at 3200 mV normal idle standby <6>[ 0.124579] print_constraints: max77696_ldo8: 800 <--> 2375 mV at 1100 mV normal idle standby <6>[ 0.125120] print_constraints: max77696_ldo9: 800 <--> 2375 mV at 1100 mV normal idle standby <6>[ 0.125677] print_constraints: max77696_ldo10: 2400 <--> 5550 mV at 5200 mV normal idle standby <6>[ 0.126469] MAX77696 Linear Regulators Driver 1.0.2 Installed <6>[ 0.127088] print_constraints: max77696_lsw1: <6>[ 0.127422] print_constraints: max77696_lsw2: <6>[ 0.127743] print_constraints: max77696_lsw3: <6>[ 0.128049] print_constraints: max77696_lsw4: <6>[ 0.128094] MAX77696 Load Switches Driver 1.0.0 Installed <6>[ 0.129313] print_constraints: max77696-display: <6>[ 0.130052] print_constraints: max77696-vcom: <6>[ 0.130608] print_constraints: max77696-vee: <6>[ 0.130944] print_constraints: max77696-vneg: <6>[ 0.131279] print_constraints: max77696-vpos: <6>[ 0.131588] print_constraints: max77696-vddh: <6>[ 0.132598] <6>[ 0.132602] EPD vreg probe complete! <6>[ 0.133198] print_constraints: max77696_vddq: 240 <--> 984 mV at 600 mV <6>[ 0.133252] MAX77696 LPDDR2 Termination Supply Driver 1.0.1 Installed <6>[ 0.134560] MAX77696 I2C Driver 1.0.0 Installed <4>[ 0.137111] i2c-core: driver [max17135] using legacy suspend method <4>[ 0.137122] i2c-core: driver [max17135] using legacy resume method <6>[ 0.137157] Switching to clocksource mxc_timer1 <6>[ 0.147929] NET: Registered protocol family 2 <6>[ 0.148022] IP route cache hash table entries: 2048 (order: 1, 8192 bytes) <6>[ 0.148209] TCP established hash table entries: 8192 (order: 4, 65536 bytes) <6>[ 0.148323] TCP bind hash table entries: 8192 (order: 3, 32768 bytes) <6>[ 0.148382] TCP: Hash tables configured (established 8192 bind 8192) <6>[ 0.148390] TCP reno registered <6>[ 0.148399] UDP hash table entries: 256 (order: 0, 4096 bytes) <6>[ 0.148415] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) <6>[ 0.148752] NET: Registered protocol family 1 <6>[ 0.148932] RPC: Registered named UNIX socket transport module. <6>[ 0.148942] RPC: Registered udp transport module. <6>[ 0.148950] RPC: Registered tcp transport module. <6>[ 0.148956] RPC: Registered tcp NFSv4.1 backchannel transport module. <4>[ 0.153043] etb: probe of etb failed with error -2 <4>[ 0.153300] etm: probe of etm.0 failed with error -2 <6>[ 0.153607] Static Power Management for Freescale i.MX6 <6>[ 0.153617] wait mode is enabled for i.MX6 <6>[ 0.153773] cpaddr = d0820000 suspend_iram_base=d081c000 <6>[ 0.153829] PM driver module loaded <6>[ 0.154091] IMX usb wakeup probe <7>[ 0.154113] the wakeup pdata is 0xce298080 <6>[ 0.154448] IMX usb wakeup probe <7>[ 0.154466] the wakeup pdata is 0xce298200 <6>[ 0.154626] cpu regulator mode:ldo_bypass <6>[ 0.155025] i.MXC CPU frequency driver <6>[ 0.169241] squashfs: version 4.0 (2009/01/31) Phillip Lougher <6>[ 0.170245] msgmni has been set to 497 <6>[ 0.170630] io scheduler noop registered <6>[ 0.170709] io scheduler cfq registered (default) <6>[ 0.171151] MAX77696 Backlight Driver 1.0.0 Installed <6>[ 0.171909] imx-sdma imx-sdma: loaded firmware 1.1 <6>[ 0.176371] imx-sdma imx-sdma: initialized <6>[ 0.178579] Serial: IMX driver <6>[ 0.178693] imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX <6>[ 0.178722] console [ttymxc0] enabled, bootconsole disabled <6>[ 0.182461] loop: module loaded <6>[ 0.182696] MAX77696 32kHz Oscillator Driver 1.0.0 Installed <6>[ 0.183263] input: max77696-onkey as /devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-onkey.0/input/input0 <6>[ 0.186455] MAX77696 ONKEY Driver 1.0.0 Installed <6>[ 0.208600] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.0 as rtc0 <6>[ 0.228519] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.1 as rtc1 <6>[ 0.247818] MAX77696 RTC Driver 1.0.2 Installed <6>[ 0.248524] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc2 <6>[ 0.248680] i2c /dev entries driver <6>[ 0.252675] max77696-battery max77696-battery.0: Voltage alert 3400mV ... 4260mV <6>[ 0.253089] max77696-battery max77696-battery.0: SOC alert (disabled) <6>[ 0.253994] MAX77696 Fuel Gauge Driver 1.0.0 Installed <6>[ 0.255878] MAX77696 USB Interface Circuit Driver 1.0.0 Installed <6>[ 0.257657] max77696-adc max77696-adc.0: ADC average rate: 32 sample(s) <6>[ 0.257669] max77696-adc max77696-adc.0: ADC delay: 0 nsec <6>[ 0.257677] max77696-adc max77696-adc.0: ADC cur src: 50 uA <6>[ 0.257689] MAX77696 ADC Driver 1.0.1 Installed <6>[ 0.258189] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1) <6>[ 0.258565] sdhci: Secure Digital Host Controller Interface driver <6>[ 0.258574] sdhci: Copyright(c) Pierre Ossman <6>[ 0.258683] mmc0: no vmmc regulator found <6>[ 0.259964] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA <6>[ 0.261033] mmc1: no vmmc regulator found <6>[ 0.263410] mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA <7>[ 0.264107] Registered led device: max77696-leds.0 <6>[ 0.264118] MAX77696 LED Driver #0 1.0.0 Installed <7>[ 0.264306] Registered led device: max77696-leds.1 <6>[ 0.264315] MAX77696 LED Driver #1 1.0.0 Installed <6>[ 0.264829] nf_conntrack version 0.5.0 (3978 buckets, 15912 max) <6>[ 0.265550] ip_tables: (C) 2000-2006 Netfilter Core Team <6>[ 0.265617] TCP cubic registered <6>[ 0.265628] NET: Registered protocol family 17 <6>[ 0.265647] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 <3>[ 0.265782] LPDDR2 MfgId: 0x1 [Samsung] <3>[ 0.269678] <3>[ 0.269681] just text: vaddr 0xc011e9bc, va 0xc011e200 pa 0x801000c3 attr 0x6 <3>[ 0.278148] <3>[ 0.278151] nmx6sl_wfi_iram: vaddr 0xd081a000, va 0xd081a200 pa 0x902043 attr 0x2 <3>[ 0.287122] <3>[ 0.287124] mx6sl_ddr: vaddr 0xd0852000, va 0xd0852200 pa 0x903043 attr 0x2 <3>[ 0.295583] <3>[ 0.295585] mx6sl_iomux: vaddr 0xf40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149 <3>[ 0.304478] <3>[ 0.304481] ANATOP: vaddr 0xf40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149 <3>[ 0.312939] <3>[ 0.312941] CCM: vaddr 0xf40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149 <3>[ 0.321138] <3>[ 0.321140] MMDC_P0: vaddr 0xf41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149 <3>[ 0.329685] <3>[ 0.329688] L2: vaddr 0xf2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149 <3>[ 0.337710] <3>[ 0.337713] arm perif: vaddr 0xf2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149 <6>[ 0.350647] Bus freq driver module loaded <6>[ 0.350658] Bus freq driver Enabled <6>[ 0.351644] mxc_dvfs_core_probe <6>[ 0.351906] DVFS driver module loaded <4>[ 0.353738] regulator_init_complete: max77696_ldo10: incomplete constraints, leaving on <4>[ 0.354377] regulator_init_complete: max77696_ldo7: incomplete constraints, leaving on <4>[ 0.354596] regulator_init_complete: max77696_ldo6: incomplete constraints, leaving on <4>[ 0.355855] regulator_init_complete: max77696_buck6: incomplete constraints, leaving on <4>[ 0.356077] regulator_init_complete: max77696_buck5: incomplete constraints, leaving on <4>[ 0.356505] regulator_init_complete: max77696_buck2dvs: incomplete constraints, leaving on <4>[ 0.356725] regulator_init_complete: max77696_buck1dvs: incomplete constraints, leaving on <3>[ 0.367437] max77696-adc max77696-adc.0: adc conversion timed out <6>[ 0.387431] max77696-rtc max77696-rtc.0: setting system clock to 2000-01-01 02:18:18 UTC (946693098) <3>[ 0.427948] max77696-adc max77696-adc.0: adc conversion timed out <6>[ 0.434332] <6>[ 0.434335] ADC value out of thermistor range! setting display temp to 43 deg C <6>[ 0.434757] KERNEL: I pmic:charger chgina::charger connected <6>[ 0.440054] MAX77696 Main Charger Driver 1.0.0 Installed <6>[ 0.443282] MAX77696 Energy Harvester Driver 1.0.0 Installed <6>[ 0.443847] Freeing init memory: 1040K <6>[ 0.448117] emmc: I def:mmcpartinfo:vendor=micron, host=mmc0: <6>[ 0.483185] mmc0: new high speed DDR MMC card at address 0001 <6>[ 0.483482] mmcblk0: mmc0:0001 MMC02G 1.83 GiB <6>[ 0.483606] mmcblk0boot0: mmc0:0001 MMC02G partition 1 2.00 MiB <6>[ 0.483726] mmcblk0boot1: mmc0:0001 MMC02G partition 2 2.00 MiB <6>[ 0.485548] mmcblk0: p1 p2 p3 p4 <6>[ 0.487916] mmcblk0boot1: unknown partition table <6>[ 0.490004] mmcblk0boot0: unknown partition table <4>[ 0.561463] mxc_epdc_eink: module license 'proprietary' taints kernel. <4>[ 0.563499] Disabling lock debugging due to kernel taint <4>[ 0.563904] INFO:Loaded module /lib/modules/mxc_epdc_eink.ko (10776 bytes) <6>[ 1.177202] add wake up source irq 104 <6>[ 2.247219] KERNEL: I pmic:fg battery id check::wario_battery_valid=0 <6>[ 2.247257] kernel: kernel_metric_high_priority,946693100,counter,kernel,fg,wario battery invalid,1, <4>[ 3.307123] INFO:Loaded module /lib/modules/mxc_epdc_fb.ko (85104 bytes) <4>[ 3.483921] INFO:eink initialized... (786432 bytes) <4>[ 4.684638] INFO:Couldn't find localized image at /mnt/wfm/images/repair.raw.gz <4>[ 6.148819] INFO: <4>[ 6.148927] ===FL fadedown success=== <4>[ 6.149216] ERROR: <4>[ 6.149224] === BATTERY ID IS INVALID. STOPPING BOOT === <6>[ 6.165696] ARC USBOTG Device Controller driver (1 August 2005) <6>[ 6.169314] add wake up source irq 75 <4>[ 6.178597] USB Cable is already plugged in. Simulating event <4>[ 6.183045] INFO:Loaded module /lib/modules/arcotg_udc.ko (33324 bytes) <6>[ 6.205308] g_file_storage gadget: File-backed Storage Gadget, version: 1 September 2010 <6>[ 6.205340] g_file_storage gadget: Number of LUNs=1 <7>[ 6.205369] dr_controller_run: udc out low power mode <6>[ 6.205387] fsl-usb2-udc: bind to driver g_file_storage <4>[ 6.205481] INFO:Loaded module /lib/modules/g_file_storage.ko removable=1 vendor=0x1949 product=0x0004 release=0x0100 recovery_mode=1 (37756 bytes) **** Sent "/" ***** <4>[ 10.181095] INFO:Rebooting ... <6>[ 10.197724] unregistered gadget driver 'g_file_storage' <6>[ 10.202146] ARC USBOTG Device Controller driver unregistered <4>[ 10.396595] INFO:Couldn't find localized image at /mnt/wfm/images/reboot.raw.gz <6>[ 11.159072] Device spi0.0 removed EDIT: It's interesting to note that, whether I use the main or diags kernel with idme bootmode main (having flashed the diags kernel to the main kernel as an experiment), the battery ID check fails, whereas if idme bootmode is set to diags, the battery ID check passes and the system boots to diag. I'm thinking this is an issue with the main rootfs, however, both reflashing mmcblk0p1.bin from ixtab's site and running through the update_kindle_5.4.3.2.bin process (all of which succeeds, so at this point I doubt it's eMMC related) still results in the battery id check failing & the system hanging in main. At the very least I got the main kernel to spit out boot info by editing bootargs and removing 'quiet'; however, whether I add debug or not, the battery check still fails. I'm at wit's end, not sure where to go from here. EDIT2: ?!?!?! Now here's something quite strange. If I have bootmode set to main, then interrupt the boot process, enter bist, set bootmode to diags, and enter 'boot' instead of resetting, the Kindle boots just fine. If I run a restart from the Kindle OS, because the bootmode is diags, it boots into the diags partition. If I run a restart from the Kindle OS, interrupt boot, enter bist, set bootmode to main and reset, it fails the battery check again. At least I've got it booting and can confirm rootfs is OK. It's nice to have made some progress, but I can't for the life of me explain this behaviour. I've diffed the early boot sections of the two kernels/boot processes (up until the battery id check) and they're basically identical. In the bootargs, two main differences: Code:
main: rootwait log_pos_goal=0x8fffc000 console=ttymxc0,115200 root=/dev/mmcblk0p1 ro ip=off quiet video=mxcepdcfb:E60,bpp=8,x_mem=3M diags: rootwait log_pos_goal=0x8fffc000 console=ttymxc0,115200 root=/dev/mmcblk0p2 ro ip=off debug video=mxcepdcfb:E60,bpp=8,x_mem=3M EDIT3: When booting with idme bootmode diags set, the Kindle boots the main OS in diags mode, performing a filesystem check, but then booting the interface. wario_battery_valid=1. When booting with idme bootmode normal set, the kernel log is identical up to the wario_battery_valid line, which is now 0, causing boot to stop. The battery is now fully charged at nearly 4.2v. I don't know enough about the boot process to tell where it's getting this information from & whether the relevant module can be disabled. As it stands, I can't perform restarts without serial as I need to change the bootmode back to main, reset, then interrupt and change back to diags so the battery ID check passes. Last edited by varu; 10-01-2017 at 11:58 AM. |
|
|
|
|
10-02-2017, 05:38 PM
|
#7 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
No progress as of yet. I haven't yet figured out why it's failing this battery ID check (to be fair I haven't found nor looked at any sources yet). However, I successfully got it to boot by setting bootmode diags with uboot first booting using main (which preserves the main bootargs & thus gets the diags kernel to boot mmcblk01, resulting in a functional system).
I thus considered altering the diags bootargs value to always use mmcblk01 & flashing the main kernel to the diags kernel location. After all, should I encounter trouble in the future, I can always serial in & alter bootargs / flash the diags kernel back. However, both uboot & bist lack a saveenv command, so I'm not able to save a modified bootargs. I'm not sure where the built-in bootargs value is stored either; I looked through mmcblk0boot0 & boot1 but found nothing of the sort. Anything that could point me in the right direction is very much appreciated! |
|
|
|
|
10-02-2017, 07:19 PM
|
#8 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Why don't you install a current set of u-boot, main kernel, and main filesystem?
Keep in mind you can't use fastboot to install the main filesystem image - it is too big. Just use KindleTool to open any Amazon (PW2 - if that is what your writing about) update file, version of your choice, for the binary images. Some links available in the current jail break post, step #7, open the spoiler. |
|
|
|
|
10-02-2017, 09:03 PM
|
#9 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
I tried 5.7.4 & 5.8.7.0.1 - the latter updated uboot, but no changes in features that I could see. However, some strange behaviour:
1) If I flash update_PW2_5.4.3.2_initial.bin, I can get one to several successful main boots. Eventually I'll see a return to the battery ID check failing. 2) Newer firmwares crash the same way, but provide a bit more info: Code:
<4>[ 4.896568] DEBUG:eink.c:727:eink_draw_sprite():eink_draw_sprite(x0:480,y0:983,s->x_size=24,s->y_size=41,s->x_off=0,s->y_off=0) <4>[ 4.896915] INFO:eink.c:891:eink_printf():BATTERY INVALID: -22 <4>[ 5.511564] INFO:recovery-util.c:316:fl_control_fadedown(): <4>[ 5.511652] ===FL fadedown success=== <4>[ 5.511950] ERROR:recovery-util.c:346:battery_check(): <4>[ 5.511962] === BATTERY ID IS INVALID. STOPPING BOOT === It's also worth noting that, while I had the 5.4.3.2 firmware booting properly, I booted diags & mounted NFS over USBnet, taking a dd backup of the entire mmcblk0 in case it's something software causing the issue. I restored that backup and still ran into battery ID checks... at this point I'm beginning to suspect the hardware more and more. If it does turn out to be a hardware fault, I'm back to figuring out how to permanently change the diags bootargs to use mmcblk0p1 instead of 0p2 - this will give me a functional Kindle that can survive reboots, hardware be damned. Everything seems to work on 5.4.3.2 after all. EDIT: I've now reseated every flex cable on the board. No dice 
Last edited by varu; 10-02-2017 at 09:29 PM. |
|
|
|
|
10-02-2017, 09:38 PM
|
#10 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
When I wrote: "Your choice of Amazon version update packages"
I did not: Mean to include the non-customer released packages (the factory-use-only packages) - Hint: That is why I directed you to the spoiler in Step 7 of the jail break post. I did not: Tell you to use any menu entry to install the entire update package using the built-in updater. I did tell you to open the package with KindleTool so that you could manually install the binary images. = = = = Question: If you already know so much about the device and the process to recover from what you have already done - Then why are you wasting your time and ours by asking for advice. Regardless of the advice given, you are dead set on doing things your own way. So go do things your own way and save yourself the time of making the posts and us the time wasted with reading and replying to your posts. |
|
|
|
|
10-02-2017, 10:43 PM
|
#11 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
I'm posting everything I try both to keep track of what I did & in case it ends up being of some use to someone - at the very least as an overview of what doesn't work. I am certainly not dead set on doing things my way, else I would not be asking for advice, much less following it when it is given.
I extracted the 5.8.7.0.1 package linked in the #7 spoiler of the jailbreak post using KindleTool, booted into diags, mounted USB and copied u-boot.bin, fwo_rootfs.img and uImage to it, and used dd to flash each as per this post. I then set idme -d --bootmode main and rebooted. Unfortunately I still ended up with "BATTERY INVALID: -22". The current kernel log: Spoiler:
Last edited by varu; 10-03-2017 at 09:18 PM. Reason: Added spoiler. |
|
|
|
|
10-03-2017, 09:17 PM
|
#12 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
I had a poke through the kernel sources and found this in linux-3.0.35\drivers\power\max77696-battery.c:
Spoiler:
The battery check seems to go through this logic: IF the temp difference is less than 15 OR we're in diags OR it's a wario or woody board OR we've set the battery check to disabled, we can return 1 - we passed the check! This is where I believe my board goes wonky on the display thermistor side. The battery thermistor returns a proper value of about 82F - around 27-28C. The 5.4.0 & 5.4.3.2 kernels, when the ADC fails to retrieve a proper value for the display thermistor, hard-set it to 43C. If the battery is warm enough, the 15-degree delta check is passed and the battery ID check passes. This explains why I was able to have occasional successes booting with the 5.4.x firmware, but none with any higher. I took a look at the output of the 5.8.7.0.1 kernel: Spoiler:
That would explain it! The temp_delta is always greater than 15, so this returns false. Diags isn't set, so that also returns false. This isn't a wario or woody board (I believe), so this also returns false. The battery check is not disabled, also false. Because the entire OR chain is false, the check returns 0. When diags mode is set, the Diags condition of the above chain becomes true, setting the if conditional to true, returning 1, and passing the check. Looking at max77696-adc.c from the 5.8.7.0.1 sources, we see how the ADC logic works: The temp range it operates with, ranging from -10 to +75C: Spoiler:
As well as the code that operates on it. It seems to be a comparator, starting at -10C and going up to 75C hoping to strike a match against what it read. If a match is found, it is set to whatever the counter has reached. Otherwise, if the ADC value is outside of the -10/+75C bounds, if it's above the bound, it gets set to 75C. If it's below, it gets set to -10C. As it's being set to 75C, we know the value the ADC is reading is above 75. Spoiler:
Looking at max77696-adc.c from the 5.4.0 sources, sure enough! A range of +3 to +43C! Spoiler:
This confirms two scenarios I've seen: that of the display temp set to 43, and that of it set to 3. We now know where those values came from and how they ended up that way. The question now is what causes the max77696 to retrieve an incorrect value from the display thermistor (also perhaps to have a peek at what the value it retrieves *is*). |
|
|
|
|
10-03-2017, 10:09 PM
|
#13 |
|
Guru
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
|
That's fantastic research.
I think my paperwhite that has no screen plugged into it gives that same error, but I will have to double check. |
|
|
|
|
10-04-2017, 12:18 AM
|
#14 |
|
Member
Posts: 12
Karma: 10000
Join Date: Sep 2017
Device: Kindle PW2
|
The display temperature is retrieved as follows in max77696-adc.c:
Spoiler:
So MAX77696_ADC_CH_AIN2 is the specific sensor we want to look at. The kernel exposes this sensor & all others on the MAX77696 at /sys/devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-adc.0/ Running cat /sys/devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-adc.0/ain2 I get... Code:
max77696-adc max77696-adc.0: adc conversion timed out The code for the ADC conversion is in max77696-adc.c & looks like this: Spoiler:
The salient bit is as follows (with comments on what I think it does - I'm by no means a programmer). The 10msec value is drawn from earlier in the file: #define ADC_CONVERSION_TIME_OUT 10 /* in milli-seconds */ Code:
/* Check availability of ADC val by inspecting the ADCCONV bit.
* This bit is automatically cleared to 0
* when an ADC conversion sequence has completed.
*/
timeout = jiffies + msecs_to_jiffies(ADC_CONVERSION_TIME_OUT); // time when this function is ran plus 10msec (in jiffies)
do {
if (unlikely(time_after(jiffies, timeout))) { // if time when this is checked is *after* timeout, this check has taken too long
dev_err(me->dev, "adc conversion timed out\n");
rc = - -ETIMEDOUT;
goto out;
}
msleep(1); // sleep for 1ms
max77696_adc_reg_get_bit(me, ADCCNTL, ADCCONV, &adc_busy);
} while (likely(adc_busy));
As the display temperature check is all I'm concerned about, the next step is to rebuild the kernel with a modified max77696-battery.c where either wario_battery_check_disabled is hardcoded to 1, or where the temp_delta < BATT_ID_CHECK_TEMP_DELTA check is removed from the OR chain. That said, such a task is somewhat unexplored territory for me (bit of a different story than just compiling one on x86 from what I've read). If anyone reading can assist or think of a better approach, I welcome any and all suggestions! Last edited by varu; 10-04-2017 at 01:34 AM. |
|
|
|
|
10-04-2017, 11:06 AM
|
#15 |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Which is one certain way to create thermal runaway during battery charging.
Which is just fine, if your objective is to start a fire or a bragging rights you-tube video. Disabling it on the display just gives you an unreadable display (the e-ink waveform generator needs the value). |
|
|
|
 |
| Tags |
| boot, code, loop, repair |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| KPW1 needs repair. Code 2. Serial port fix. | amocus | Kindle Developer's Corner | 8 | 09-03-2015 02:30 PM |
| [Need Help] PW2 fault with Repair Code 2 | matrix121985 | Kindle Developer's Corner | 2 | 11-13-2014 03:37 AM |
| pw2 Repair Needed help please! | pes2014a | Kindle Developer's Corner | 7 | 04-21-2014 09:55 AM |
| Kindle PW2 now £89 for a short time with coupon code | BookCat | Amazon Kindle | 19 | 02-28-2014 03:30 PM |
All times are GMT -4. The time now is 12:38 PM.