Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 09-02-2016, 05:45 AM   #1
pudzian
Junior Member
pudzian began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2016
Device: Kindle Keyboard 3
Fix a bricked ( looping with crashed screen ) Voyage

Hi,

I have a K3 for reading purposes and I was looking for a high resolution e-ink display for a custom project with a mirror and bought a faulty kindle voyage.

Supposedly it shouldn't even be turning on, but the thing is, once I connected it to a charger, the background light lit up and the amber led turned on. Every 5/10 seconds the light goes off and on again and it seems to be stuck here.

Without the charging cable, if I press the power button the led turns green for a second and then disappears and the same behaviour ( light on and off every x seconds ).



This is the link to the video in case you can't see it here: https://www.youtube.com/watch?v=cLem-m_QgMw

So now I'm thinking that there may be a solution for this voyage. I do have several spare USB TTL adapters and I'm going to mod one for the 1.8v.

I've seen several tutorials for the jailbreak, but none for the firmware flash from scratch ( for this specific model ). I've also used the search and the wiki links but they are empty. Could someone please point me in the right direction?


Does this look like something fixable or should I just skip this step and go straight to disassembly to remove the screen?

Last edited by pudzian; 09-02-2016 at 05:59 AM.
pudzian is offline   Reply With Quote
Old 09-02-2016, 08:37 AM   #2
knc1
¯\_(ツ)_/¯ <- Clueless
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 11,808
Karma: 12397053
Join Date: Feb 2012
Location: Central Texas
Device: No PW2, KV, KOA
Follow the directions from any 5.x model -
only changes are the version number of the firmware being flashed that are model specific.

But you will most likely not need to do that (re-flash to a blank eMMC - there is firmware in there already, that is running).

It should be fixable, but get the serial port interface working before you decide HOW you are going to fix it or WHAT it is you are going to fix.

The step you should skip for now is the predefining what repairs the device needs before you have seen the messages being produced during its start up.

PS: Leave device on wall charger while thinking, planning, getting ready.
A few days on the wall charger might fix it.
knc1 is offline   Reply With Quote
Old 09-02-2016, 11:28 AM   #3
pudzian
Junior Member
pudzian began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2016
Device: Kindle Keyboard 3
Quote:
Originally Posted by knc1 View Post
Follow the directions from any 5.x model -
only changes are the version number of the firmware being flashed that are model specific.

But you will most likely not need to do that (re-flash to a blank eMMC - there is firmware in there already, that is running).

It should be fixable, but get the serial port interface working before you decide HOW you are going to fix it or WHAT it is you are going to fix.

The step you should skip for now is the predefining what repairs the device needs before you have seen the messages being produced during its start up.

PS: Leave device on wall charger while thinking, planning, getting ready.
A few days on the wall charger might fix it.

Thanks for the input.


I was able access the serial port and look at the messages... It seems to be complaining about a hw failure?

Code:
U-Boot 2009.08-lab126 (Aug 07 2014 - 00:52:13)


CPU: Freescale i.MX6 family TO0.0 at 996 MHz

Temperature:   33 C, calibration data 0x5955255f

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: Icewine 512

Boot Reason: [ POR ]

Boot Device: NAND

Board Id: xxxxxxxx

S/N: xxxxxxxxxxx

I2C:   ready

DRAM:  512 MB

Using default environment


In:    serial

Out:   serial

Err:   serial

Quick Memory Test 0x80000000, 0x1fff0000

POST done in 115 ms

Battery voltage: 4185 mV


check_haptic: ID = 0x07

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:    2593928 Bytes =  2.5 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK


Starting kernel ...


[    0.097953] No Legacy reboot reason code to print
[    0.276709] LPDDR2 MfgId: 0x1 [Samsung]
[    0.280572] 
[    0.280574] just text: vaddr c013f678, va 0xc013f200 pa 0x801000c3 attr 0x6
[    0.293042] 
[    0.293045] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.301910] 
[    0.301913] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.310329] 
[    0.310331] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.321113] 
[    0.321116] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.334549] 
[    0.334552] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.344395] 
[    0.344398] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.356830] 
[    0.356834] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.366750] 
[    0.366753] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 PREEMPT Wed Apr 15 11:43:56 PDT 2015 armv7l
[    1.683462] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    1.690749] Regulator Fault Occurred! Retrying powerup...
[    1.768603] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    1.775871] Regulator Fault Occurred! Retrying powerup...
[    1.848604] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    1.855871] Regulator Fault Occurred! Retrying powerup...
[    1.876500] imx_epdc_fb imx_epdc_fb: EPDC powerup timeout/error.
[    1.936578] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    1.943817] Regulator Fault Occurred! Retrying powerup...
[    2.018590] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    2.025857] Regulator Fault Occurred! Retrying powerup...
[    2.098606] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    2.105873] Regulator Fault Occurred! Retrying powerup...
[    2.126491] imx_epdc_fb imx_epdc_fb: EPDC powerup timeout/error.
[    2.186571] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    2.193811] Regulator Fault Occurred! Retrying powerup...
[    2.268614] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    2.275884] Regulator Fault Occurred! Retrying powerup...
[    2.348618] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
[    2.355886] Regulator Fault Occurred! Retrying powerup...
[    2.376489] imx_epdc_fb imx_epdc_fb: EPDC powerup timeout/error.
[    2.382528] imx_epdc_fb imx_epdc_fb: Failed to do initialization sequence -901

=== kernel printk buffer (23243 bytes) ===
<5>[    0.000000] Linux version 3.0.35-lab126 (jenkins-official@sjc10-jbuild08) (collect2: ld returned 1 exit status) #1 PREEMPT Wed Apr 15 11:43:56 PDT 2015
<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: 131072
<7>[    0.000000] free_area_init_node: node 0, pgdat c05395b8, 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: 960 pages used for memmap
<7>[    0.000000]   Normal zone: 121920 pages, LIFO batch:31
<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: 130048
<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: 8fffc000
<6>[    0.000000] log_buf_len: 32768
<6>[    0.000000] early log buf free: 31330(95%)
<6>[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[    0.000000] Memory: 512MB = 512MB total
<5>[    0.000000] Memory: 514184k/514184k available, 10104k 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 : 0xe0800000 - 0xf2000000   ( 280 MB)
<5>[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
<5>[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
<5>[    0.000000]       .init : 0xc0008000 - 0xc012c000   (1168 kB)
<5>[    0.000000]       .text : 0xc012c000 - 0xc0505000   (3940 kB)
<5>[    0.000000]       .data : 0xc0506000 - 0xc053a0e0   ( 209 kB)
<5>[    0.000000]        .bss : 0xc053a104 - 0xc055f960   ( 151 kB)
<6>[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
<6>[    0.000000] Preemptible hierarchical RCU implementation.
<6>[    0.000000] .Verbose stalled-CPUs detection is disabled.
<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.000266] Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896)
<6>[    0.060124] pid_max: default: 32768 minimum: 301
<6>[    0.060384] 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.067668] print_constraints: dummy: 
<6>[    0.067838] NET: Registered protocol family 16
<6>[    0.072267] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal 
<6>[    0.072584] print_constraints: vddcore: 725 <--> 1300 mV at 1475 mV fast normal 
<6>[    0.072900] print_constraints: vddsoc: 725 <--> 1300 mV at 1475 mV fast normal 
<6>[    0.073217] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal 
<6>[    0.073575] print_constraints: vdd1p1: 800Ô <--> 1400 mV at 1100 mV fast normal 
<6>[    0.073916] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal 
<4>[    0.075672] LAB126 Board id - 04709011439403BY
<6>[    0.080379] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
<6>[    0.080391] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
<6>[    0.080405] hw-breakpoint: maximum watchpoint size is 4 bytes.
<6>[    0.080423] L310 cache controller enabled
<6>[    0.080433] l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02030000, Cache size: 262144 B
<6>[    0.089693] bio: create slab <bio-0> at 0
<6>[    0.094000] max77696> regulator init
<6>[    0.094993] spi_imx imx6q-ecspi.0: probed
<6>[    0.095405] usbcore: registered new interface driver usbfs
<6>[    0.095533] usbcore: registered new interface driver hub
<6>[    0.095684] usbcore: registered new device driver usb
<4>[    0.097923] Reboot Reason - Metric Framework Reporting
<6>[    0.097938] kernel: kernel_metric_generic,0,counter,event_recorder,ercflags,ercflag_empty,1,
<4>[    0.097947] Reboot Reason - Legacy Metric Reporting
<3>[    0.097953] No Legacy reboot reason code to print
<6>[    0.104279] MAX77696 TOPSYS 1.0.0 Installed
<6>[    0.106979] max77696-gpio max77696-gpio.0: gpio#0 -- -- func-0 in 
<6>[    0.108443] max77696-gpio max77696-gpio.0: gpio#1 -- -- func--1 in 
<6>[    0.109902] max77696-gpio max77696-gpio.0: gpio#3 -- -- func-0 in 
<6>[    0.111750] MAX77696 GPIO Driver 1.0.0 Installed
<4>[    0.112998] buck mode: 4
<4>[    0.113752] buck mode: 4
<6>[    0.114700] print_constraints: max77696_buck1: 900 <--> 1300 mV at 1250 mV fast normal idle standby
<4>[    0.115299] buck mode: 4
<6>[    0.116250] print_constraints: max77696_buck1dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby
<4>[    0.116835] buck mode: 4
<4>[    0.117571] buck mode: 4
<6>[    0.118512] print_constraints: max77696_buck2: 900 <--> 1300 mV at 1200 mV fast normal idle standby
<4>[    0.119062] buck mode: 4
<6>[    0.120007] print_constraints: max77696_buck2dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby
<6>[    0.120563] print_constraints: max77696_buck3: 600 <--> 3387 mV at 1300 mV fast normal idle standby
<4>[    0.121284] buck mode: 4
<4>[    0.122020] buck mode: 4
<6>[    0.122781] print_constraints: max77696_buck4: 1200 mV fast normal idle standby
<4>[    0.123347] buck mode: 4
<6>[    0.124293] print_constraints: max77696_buck5: 600 <--> 3387 mV at 1800 mV fast normal idle standby
<4>[    0.124857] buck mode: 2
<6>[    0.125803] print_constraints: max77696_buck6: 600 <--> 3387 mV at 3200 mV fast normal idle standby
<6>[    0.125845] MAX77696 Buck Regulators Driver 1.0.1 Installed
<6>[    0.126685] print_constraints: max77696_ldo1: 800 <--> 3950 mV at 3300 mV normal idle standby
<6>[    0.127269] print_constraints: max77696_ldo2: 800 <--> 3950 mV at 3000 mV normal idle standby
<6>[    0.127844] print_constraints: max77696_ldo3: 800 <--> 3950 mV at 2500 mV normal idle standby
<6>[    0.128412] print_constraints: max77696_ldo4: 800 <--> 2375 mV at 1800 mV normal idle standby
<6>[    0.128973] print_constraints: max77696_ldo5: 800 <--> 2375 mV at 1800 mV normal idle standby
<6>[    0.129547] print_constraints: max77696_ldo6: 800 <--> 3950 mV at 3200 mV normal idle standby
<6>[    0.130119] print_constraints: max77696_ldo7: 800 <--> 3950 mV at 3200 mV normal idle standby
<6>[    0.130678] print_constraints: max77696_ldo8: 800 <--> 2375 mV at 1100 mV normal idle standby
<6>[    0.131255] print_constraints: max77696_ldo9: 800 <--> 2375 mV at 1100 mV normal idle standby
<6>[    0.131830] print_constraints: max77696_ldo10: 2400 <--> 5550 mV at 5200 mV normal idle standby
<6>[    0.132620] MAX77696 Linear Regulators Driver 1.0.2 Installed
<6>[    0.133407] print_constraints: max77ˇ696_lsw1: 
<6>[    0.133789] print_constraints: max77696_lsw2: 
<6>[    0.134130] print_constraints: max77696_lsw3: 
<6>[    0.134467] print_constraints: max77696_lsw4: 
<6>[    0.134511] MAX77696 Load Switches Driver 1.0.0 Installed
<6>[    0.135758] print_constraints: max77696-display: 
<6>[    0.136535] print_constraints: max77696-vcom: 
<6>[    0.136893] print_constraints: max77696-vee: 
<6>[    0.137256] print_constraints: max77696-vneg: 
<6>[    0.137628] print_constraints: max77696-vpos: 
<6>[    0.137970] print_constraints: max77696-vddh: 
<6>[    0.138969] 
<6>[    0.138972] EPD vreg probe complete!
<6>[    0.139579] print_constraints: max77696_vddq: 240 <--> 984 mV at 600 mV 
<6>[    0.139638] MAX77696 LPDDR2 Termination Supply Driver 1.0.1 Installed
<6>[    0.141072] MAX77696 I2C Driver 1.0.0 Installed
<4>[    0.144471] i2c-core: driver [max17135] using legacy suspend method
<4>[    0.144483] i2c-core: driver [max17135] using legacy resume method
<6>[    0.144515] Switching to clocksource mxc_timer1
<6>[    0.156618] NET: Registered protocol family 2
<6>[    0.156714] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
<6>[    0.156899] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
<6>[    0.157114] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
<6>[    0.157223] TCP: Hash tables configured (established 16384 bind 16384)
<6>[    0.157231] TCP reno registered
<6>[    0.157241] UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>[    0.157258] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>[    0.157572] NET: Registered protocol family 1
<6>[    0.157772] RPC: Registered named UNIX socket transport module.
<6>[    0.157781] RPC: Registered udp transport module.
<6>[    0.157788] RPC: Registered tcp transport module.
<6>[    0.157795] RPC: Registered tcp NFSv4.1 backchannel transport module.
<4>[    0.162276] etb: probe of etb failed with error -2
<4>[    0.162576] etm: probe of etm.0 failed with error -2
<6>[    0.162868] Static Power Management for Freescale i.MX6
<6>[    0.162878] wait mode is enabled for i.MX6
<6>[    0.163036] cpaddr = 0 suspend_iram_base=f2900000
<6>[    0.163077] PM driver module loaded
<6>[    0.163353] IMX usb wakeup probe
<7>[    0.163374] the wakeup pdata is 0xde161680
<6>[    0.163735] IMX usb wakeup probe
<7>[    0.163754] the wakeup pdata is 0xde161800
<6>[    0.163918] cpu regulator mode:ldo_bypass
<6>[    0.164319] i.MXC CPU frequency driver
<6>[    0.181307] squashfs: version 4.0 (2009/01/31) Phillip Lougher
<6>[    0.182377] msgmni has been set to 1004
<6>[    0.182849] io scheduler noop registered
<6>[    0.182930] io scheduler cfq registered (default)
<6>[    0.183400] MAX77696 Backlight Driver 1.0.0 Installed
<6>[    0.184224] imx-sdma imx-sdma: loaded firmware 1.1
<6>[    0.189151] imx-sdma imx-sdma: initialized
<6>[    0.191179] Serial: IMX driver
<6>[    0.191300] imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
<6>[    0.191329] console [ttymxc0] enabled, bootconsole disabled
<6>[    0.196183] loop: module loaded
<6>[    0.196448] MAX77696 32kHz Oscillator Driver 1.0.0 Installed
<6>[    0.197069] input: max77696-onkey as /devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-onkey.0/input/input0
<6>[    0.200238] MAX77696 ONKEY Driver 1.0.0 Installed
<6>[    0.215860] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.0 as rtc0
<6>[    0.235748] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.1 as rtc1
<6>[    0.255180] MAX77696 RTC Driver 1.0.2 Installed
<6>[    0.255915] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc2
<6>[    0.256093] i2c /dev entries driver
<6>[    0.259769] MAX77696 Fuel Gauge Driver 1.0.0 Installed
<6>[    0.263577] MAX77696 USB Interface Circuit Driver 1.ˇ0.0 Installed
<6>[    0.266676] max77696-adc max77696-adc.0: ADC average rate: 32 sample(s)
<6>[    0.266687] max77696-adc max77696-adc.0: ADC delay: 0 nsec
<6>[    0.266695] max77696-adc max77696-adc.0: ADC cur src: 50 uA
<6>[    0.266703] MAX77696 ADC Driver 1.0.1 Installed
<6>[    0.267391] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
<6>[    0.268221] sdhci: Secure Digital Host Controller Interface driver
<6>[    0.268235] sdhci: Copyright(c) Pierre Ossman
<6>[    0.268348] mmc0: no vmmc regulator found
<7>[    0.269369] sdhci: =========== REGISTER DUMP (mmc0)===========
<4>[    0.269379] 
<4>[    0.269381] 0xe0858000:  00000000 00010200 00000000 083a0000
<4>[    0.269393] 0xe0858010:  00000900 ffffffff 320f5903 00000b00
<4>[    0.269404] 0xe0858020:  00000000 ff888088 08800024 008e0118
<4>[    0.269415] 0xe0858030:  00000000 007f0003 007f0003 00000000
<4>[    0.269425] 0xe0858040:  07f3b407 08000880 00000011 00000000
<4>[    0.269435] 0xe0858050:  00000000 00000000 00000000 00000000
<4>[    0.269445] 0xe0858060:  00000000 00000200 00000000 0800ff00
<4>[    0.269455] 0xe0858070:  00000000 00000000 00000000 00000000
<4>[    0.269465] 0xe0858080:  00000000 00000000 00000000 00000000
<4>[    0.269475] 0xe0858090:  00000000 00000000 00000000 00000000
<4>[    0.269485] 0xe08580a0:  00000000 00000000 00000000 00000000
<4>[    0.269495] 0xe08580b0:  00000000 00000000 00000000 00000000
<4>[    0.269505] 0xe08580c0:  2000780b 00000000 00000006 00212800
<7>[    0.269518] CCM: CSCMR1(0x00900040), CSCDR1(0x00490b40)
<7>[    0.269526] CCM: CCOSR(0x000a000c), CCGR6(0x00000030)
<7>[    0.269532] CCM: CMEOR(0x7fffffff)
<7>[    0.269539] sdhci: ===========================================
<6>[    0.269864] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA
<6>[    0.270937] mmc1: no vmmc regulator found
<7>[    0.271956] sdhci: =========== REGISTER DUMP (mmc1)===========
<4>[    0.271965] 
<4>[    0.271967] 0xe0860000:  00000000 00010000 00000000 00000000
<4>[    0.271978] 0xe0860010:  00000000 00000000 00000000 00000000
<4>[    0.271989] 0xe0860020:  00000000 ff888088 08800020 0080800f
<4>[    0.271999] 0xe0860030:  00000000 007f0003 007f0003 00000000
<4>[    0.272010] 0xe0860040:  07f3b407 08100810 80000000 00000000
<4>[    0.272021] 0xe0860050:  00000000 00000000 00000000 00000000
<4>[    0.272031] 0xe0860060:  00000000 00000200 00000000 0800ff00
<4>[    0.272042] 0xe0860070:  00000000 00000000 00000000 00000000
<4>[    0.272052] 0xe0860080:  00000000 00000000 00000000 00000000
<4>[    0.272062] 0xe0860090:  00000000 00000000 00000000 00000000
<4>[    0.272073] 0xe08600a0:  00000000 00000000 00000000 00000000
<4>[    0.272082] 0xe08600b0:  00000000 00000000 00000000 00000000
<4>[    0.272092] 0xe08600c0:  2000780b 00000000 00000006 00212800
<7>[    0.272106] CCM: CSCMR1(0x00900040), CSCDR1(0x00490b40)
<7>[    0.272113] CCM: CCOSR(0x000a000c), CCGR6(0x000000c0)
<7>[    0.272119] CCM: CMEOR(0x7fffffff)
<7>[    0.272125] sdhci: ===========================================
<6>[    0.272218] mmc0: mmc_rescan_try_freq: trying to init card at 400000 Hz
<6>[    0.273564] mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
<7>[    0.274471] Registered led device: max77696-leds.0
<6>[    0.274481] MAX77696 LED Driver #0 1.0.0 Installed
<7>[    0.274985] Registered led device: max77696-leds.1
<6>[    0.274995] MAX77696 LED Driver #1 1.0.0 Installed
<6>[    0.275584] nf_conntrack version 0.5.0 (8034 buckets, 32136 max)
<6>[    0.276482] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[    0.276548] TCP cubic registered
<6>[    0.276558] NET: Registered protocol family 17
<6>[    0.276576] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
<3>[    0.276709] LPDDR2 MfgId: 0x1 [Samsung]
<3>[    0.280572] 
<3>[    0.280574] just text: vaddr c013f678, va 0xc013f200 pa 0x801000c3 attr 0x6
<3>[    0.293042] 
<3>[    0.293045] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
<3>[    0.301910] 
<3>[    0.301913] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
<3>[    0.310329] 
<3>[    0.310331] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
<3>[    0.321113] 
<3>[    0.321116] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
<3>[    0.334549] 
<3>[    0.334552] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
<3>[    0.344395] 
<3>[    0.344398] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
<3>[    0.356830] 
<3>[    0.356834] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
<3>[    0.366750] 
<3>[    0.366753] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
<6>[    0.377549] Bus freq driver module loaded
<6>[    0.377561] Bus freq driver Enabled
<6>[    0.388659] mxc_dvfs_core_probe
<6>[    0.389137] DVFS driver module loaded
<4>[    0.395670] regulator_init_complete: max77696_ldo10: incomplete constraints, leaving on
<4>[    0.406105] regulator_init_complete: max77696_ldo7: incomplete constraints, leaving on
<4>[    0.409653] regulator_init_complete: max77696_ldo6: incomplete constraints, leaving on
<4>[    0.416449] regulator_init_complete: max77696_buck6: incomplete constraints, leaving on
<4>[    0.417068] regulator_init_complete: max77696_buck5: incomplete constraints, leaving on
<4>[    0.418129] regulator_init_complete: max77696_buck2dvs: incomplete constraints, leaving on
<4>[    0.418612] regulator_init_complete: max77696_buck1dvs: incomplete constraints, leaving on
<6>[    0.435418] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
<6>[    0.435624] max77696-rtc max77696-rtc.0: setting system clock to 2000-01-01 01:00:07 UTC (946688407)
<6>[    0.472116] mmc0: new high speed DDR MMC card at address 0001
<6>[    0.472884] mmcblk0: mmc0:0001 004G90 3.68 GiB 
<6>[    0.473042] mmcblk0boot0: mmc0:0001 004G90 partition 1 2.00 MiB
<6>[    0.473251] mmcblk0boot1: mmc0:0001 004G90 partition 2 2.00 MiB
<6>[    0.474337]  mmcblk0: p1 p2 p3 p4
<6>[    0.478308]  mmcblk0boot1: unknown partition table
<6>[    0.481176]  mmcblk0boot0: unknown partition table
<6>[    0.481504] mmc1: mmc_rescan_try_freq: trying to init card at 400000 Hz
<6>[    0.486200] MAX77696 Main Charger Driver 1.0.0 Installed
<6>[    0.488955] MAX77696 Energy Harvester Driver 1.0.0 Installed
<6>[    0.489473] Freeing init memory: 1168K
<4>[    0.498935] mxc_epdc_eink: module license 'proprietary' taints kernel.
<4>[    0.498948] Disabling lock debugging due to kernel taint
<4>[    0.499319] INFO:Loaded module /lib/modules/mxc_epdc_eink.ko  (10784 bytes)
<6>[    0.507112] imx_epdc_fb imx_epdc_fb: Found a video mode override (EBA)
<6>[    0.553126] mmc1: mmc_rescan_try_freq: trying to init card at 300000 Hz
<6>[    0.624299] mmc1: mmc_rescan_try_freq: trying to init card at 200000 Hz
<6>[    0.696996] mmc1: mmc_rescan_try_freq: trying to init card at 100000 Hz
<6>[    0.871268] KERNEL: I pmic:fg battery init::mg config init successful
<6>[    0.872110] max77696-battery max77696-battery.0: Voltage alert     3400mV ... 4400mV
<6>[    0.872570] max77696-battery max77696-battery.0: SOC alert         (disabled)
<6>[    1.184557] add wake up source irq 104
<6>[    1.623614] Retrieved voltage control information
<6>[    1.683395] kernel: kernel_metric_high_priority,946688408,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    1.683430] kernel: kernel_metric_high_priority,946688408,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    1.683462] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    1.690749] Regulator Fault Occurred! Retrying powerup...
<6>[    1.768541] kernel: kernel_metric_high_priority,946688408,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    1.768574] kernel: kernel_metric_high_priority,946688408,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    1.768603] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    1.775871] Regulator Fault Occurred! Retrying powerup...
<6>[    1.848544] kernel: kernel_metric_high_priority,946688408,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    1.848575] kernel: kernel_metric_high_priority,946688408,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    1.848604] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    1.855871] Regulator Fault Occurred! Retrying powerup...
<6>[    1.875515] kernel: kernel_metric_high_priority,946688408,counter,kernel,imx_epdc_fb,powerup_timeout,1,
<3>[    1.876500] imx_epdc_fb imx_epdc_fb: EPDC powerup timeout/error.
<6>[    1.936518] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    1.936549] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    1.936578] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    1.943817] Regulator Fault Occurred! Retrying powerup...
<6>[    2.018530] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    2.018562] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    2.018590] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    2.025857] Regulator Fault Occurred! Retrying powerup...
<6>[    2.098545] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    2.098577] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    2.098606] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    2.105873] Regulator Fault Occurred! Retrying powerup...
<6>[    2.125505] kernel: kernel_metric_high_priority,946688409,counter,kernel,imx_epdc_fb,powerup_timeout,1,
<3>[    2.126491] imx_epdc_fb imx_epdc_fb: EPDC powerup timeout/error.
<6>[    2.186510] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    2.186542] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    2.186571] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    2.193811] Regulator Fault Occurred! Retrying powerup...
<6>[    2.254589] KERNEL: I pmic:fg battery id check::wario_battery_valid=1
<6>[    2.268555] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    2.268586] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    2.268614] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    2.275884] Regulator Fault Occurred! Retrying powerup...
<6>[    2.348558] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VEE_fault,1,
<6>[    2.348590] kernel: kernel_metric_high_priority,946688409,counter,kernel,max77696-epd,VDD_fault,1,
<3>[    2.348618] max77696-epd max77696-epd.0: EPDINT: Regulator Fault Detected [12]
<3>[    2.355886] Regulator Fault Occurred! Retrying powerup...
<6>[    2.375511] kernel: kernel_metric_high_priority,946688409,counter,kernel,imx_epdc_fb,powerup_timeout,1,
<3>[    2.376489] imx_epdc_fb imx_epdc_fb: EPDC powerup timeout/error.
<3>[    2.382528] imx_epdc_fb imx_epdc_fb: Failed to do initialization sequence -901
<6>[    2.393849] Device spi0.0 removed
<4>[    2.394003] imx_epdc_fb: probe of imx_epdc_fb failed with error -901
<4>[    2.394460] ERROR:insmod(/lib/modules/mxc_epdc_fb.ko) : init_module error: error 19 (19)
<4>[    2.394711] ERROR:eink_init: failed to load eink driver /lib/modules/mxc_epdc_fb.ko: error 19 (19)
<4>[    2.394801] INFO:Rebooting ... 
<4>[    2.394927] ERROR:failed to create failure log... -1 

=== END ===
[    9.940185] imx2-wdt imx2-wdt.0: Device shutdown: Expect reboot!
[    9.947403] Restarting system.


Is this fixable?


Thanks!

Last edited by pudzian; 09-02-2016 at 04:47 PM.
pudzian is offline   Reply With Quote
Old 09-02-2016, 11:40 AM   #4
knc1
¯\_(ツ)_/¯ <- Clueless
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 11,808
Karma: 12397053
Join Date: Feb 2012
Location: Central Texas
Device: No PW2, KV, KOA
If the regulator is an external part, it can be replaced.
But most likely, it is grown as part of the SoC silicon.

So if you can't find the part by a visual search, then the answer is: no.
You now have a used battery for sale, the rest is junk.

Last edited by knc1; 09-02-2016 at 11:46 AM.
knc1 is offline   Reply With Quote
Old 09-02-2016, 01:37 PM   #5
pudzian
Junior Member
pudzian began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2016
Device: Kindle Keyboard 3
Quote:
Originally Posted by knc1 View Post
If the regulator is an external part, it can be replaced.
But most likely, it is grown as part of the SoC silicon.

So if you can't find the part by a visual search, then the answer is: no.
You now have a used battery for sale, the rest is junk.
Not everything will be lost because I actually bought it because of the screen which I want to use in another project.


Anyway, it seems that MAX77696A is an external part:



This is the good news. The bad news is that the MOQ for this part is 2500 and I can't find it in lower quantities. No to mention that I still need to find someone with reballing equipment.

If anyone knows where to find this part please let me know.
pudzian is offline   Reply With Quote
Old 09-02-2016, 01:46 PM   #6
knc1
¯\_(ツ)_/¯ <- Clueless
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 11,808
Karma: 12397053
Join Date: Feb 2012
Location: Central Texas
Device: No PW2, KV, KOA
You don't need re-balling equipment - that is for when you re-use a removed chip.
You will need SMT re-work equipment (and a buyer for the other 2,499 parts).

So toss it, both the motherboard and the screen are junk.

But the battery info in the listing you posted seems to show you have a good, used, battery for sale.
knc1 is offline   Reply With Quote
Old 09-02-2016, 02:03 PM   #7
Yourcat
Zealot
Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.Yourcat knows the way to San Jose.
 
Posts: 147
Karma: 54048
Join Date: Mar 2016
Device: PW3 5.6.5-usbnet
aliexpess.com offers one. Have fun replacing the 225pin IC - most people can't do this.
Cleaning and heating the MB may help if a contact (R/C/L) does not work properly. 100°C for 30 minutes in the oven may help.
Yourcat is online now   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
KV Possible Software bricked Kindle Voyage - can it be recovered? mihaixp Kindle Developer's Corner 32 04-05-2016 02:14 PM
How to fix: Search This Book & About This Book oddities with Calibre AZW3s on Voyage sun surfer Devices 8 09-19-2015 03:52 AM
Arc Looping/Crashing Tapestries fix. Kobo-Robin Kobo Tablets 7 05-08-2015 10:05 AM
Voyage Yellow Screen Problems - How to Fix - Let the Glue Dry ?? IluvToRead Amazon Kindle 5 10-25-2014 11:33 PM
IQ ua.pocketbook.bookinfo has crashed... and crashed... Nightwish PocketBook 6 02-13-2011 02:15 PM


All times are GMT -4. The time now is 03:18 AM.


MobileRead.com is a privately owned, operated and funded community.