I got a bricked PW 1 (only amber light - never reaches green - NS blank CODEX on USB)
after reading a in the forum I started to try my luck in unbricking it - but to be honest I did not get the idea why the K5-Touch and K5-Paperwhite1 stories are mixed together in the forum and I did not find a good explanation .. from my understanding the hardware and board layout is different – so maybe the bootloader too?!?
I figured out that my PW1 is in USB download mode (it displays “NS blank CODEX” in the device Manager in Windows).
I opened the PW1 and attached a 1v8 TTL USB converter to the serial port to see if there was some output over the console -> long story short: no, nothing.
Next step was to try MFGTool to upload U-Boot into RAM directly - this seems to work up to a point :
1st MFG detects the kindle -> that’s OK
2nd MFG is able to upload U-Boot according to profile into RAM -> that’s OK
3rd I do get a serial output on the Console: -> that’s OK
Code:
U-Boot 2009.08-lab126 (Feb 19 2012 - 05:01:38)
CPU: Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock : 50000000Hz
ipg per clock : 50000000Hz
uart clock : 24000000Hz
ahb clock : 100000000Hz
axi_a clock : 400000000Hz
axi_b clock : 200000000Hz
weim_clock : 100000000Hz
ddr clock : 800000000Hz
esdhc1 clock : 80000000Hz
esdhc2 clock : 80000000Hz
esdhc3 clock : 80000000Hz
esdhc4 clock : 80000000Hz
MMC: FSL_ESDHC: 0, FSL_ESDHC: 1
Timeout waiting for DAT0 to go high!
mmc switch failed: -19
### ERROR ### Please RESET the board ###
4th after ‘MMC: FSL_ESDHC: 0, FSL_ESDHC: 1’ there is a long wait period -> that’s might be OK, I do not have a comparison.
5th the ‘timeout message appears’ and after this the PW1 reboots. -> that’s is most likely NOT OK
To confirm my approach I have the following questions:
- Is the logged behavior expected? – I think the answer is ‘no’
- Is the logged timeout triggered because of a wrong u-boot version (that was compiled for the K5-Touch and not for the K5-PW1) and do I only need a correct U-Boot for the PW1?
- Do I have a hardware fault on the PW1 board – maybe an EMMC hardware fault?
To find out about an error situation, a valid approach might be to upload a U-Boot with debugging enabled so that the output on the serial console is a little more verbose – does anybody know of a pre-compiled U-Boot version for the PW1 out there in the Internet that I could upload into my PW1?
In Addition to the scenario described above where I used U-Boot included in this forums pre-tailored MFGTool distribution I uploaded u-Boot with the fastboot server included by eureka into my PW1 – but the outcome was not different I had the same error message as in the other version on the serial console.
u-boot serial log with embedded fastboot by eureka on my PW1:
Code:
U-Boot 2009.08-lab126 (Dec 14 2013 - 16:51:54)
MMC: FSL_ESDHC: 0, FSL_ESDHC: 1
Timeout waiting for DAT0 to go high!
mmc switch failed: -19
### ERROR ### Please RESET the board ###
So guys, can you provide a hint if I can stop trying to unbrick my PW1 or if I should try to connect to the EMMC directly to try to read / or restore the content.
Thanks for your help....
BTW. Which shielding on the PW1-Board contains the emmc chip? The one with the engraved 1, 2, 3 or 4?