Uboot needed for pw2

[knc1]

Originally Posted by Merlin09

hello.
thanks, I understand now. But how could I put my pw2 in usb download mode?

if I just boot, it never goes after "press any key to stop autoboot", but of course
nothing happens after that. if I go to uboot> by pressing enter early in the boot stages, well, nothing happend on the usb either (meaning that dmesg doesn't output anything)

If you can get to the u-boot prompt, why did you think you needed to install u-boot?

u-boot only talks to the serial port, it has only a command line interface, ask google.

[Merlin09]

ok, it seems I mixed up terminology.

I can get to the uboot prompt, but not launch bist to have fastboot.

In fact, it seems only the serial connection is working... basically, I understand what to do... but don't know how to do it.

sorry about the mix-up, I'm still struggling to place everything in order in my mind
so now, I guess what I should ask is... how can I restore bist and everything else, starting with only the serial connection?

[knc1]

Originally Posted by Merlin09

ok, it seems I mixed up terminology.

I can get to the uboot prompt, but not launch bist to have fastboot.

In fact, it seems only the serial connection is working... basically, I understand what to do... but don't know how to do it.

sorry about the mix-up, I'm still struggling to place everything in order in my mind
so now, I guess what I should ask is... how can I restore bist and everything else, starting with only the serial connection?

That is correct, u-boot only enables the serial port.
The same serial port that the SoC's internal code had been using prior to loading u-boot.
Also the same serial port that the kernel will use once it is loaded and executed.

That is three programs that pass off control of the serial port, one after the other as each larger application loads and runs.

(These are all basic things that a person who is messing around with the embedded firmware is expected to know. A Kindle is not the vehicle for first timer's learning. Instead, get a commercial "evaluation" board intended for self-taught instruction - they are much more forgiving of screw-ups.)

bist == Built In Self Test :: a (nearly) "full featured" build of u-boot.

The version of u-boot that first runs (and presents the prompt you reported) is a 'few featured' build of u-boot.

They are both contained in the same binary. If you have one, you have both.

Enter:
?
for a command list

Then enter:
bist
to switch to the full build

Then enter:
?
for the more complete command list.

If your device does not behave as above, then cut&paste the actual commands entered and outputs between 'code' '/code' tags of your next post.

Enable the capture feature (the logging feature) of your terminal emulator that you are using to make it easier to cut from that capture log and paste into the post here.
Also, use the 'advanced editor' here if you are not already using it.

[knc1]

You have u-boot access working.
You have not posted anything that would have disturbed the diags system.
Use u-boot to boot the diags system.
Connect the USB cord.
Use the diags system to export the USB storage.
Copy the Amazon main system update that you downloaded to the top level of USB storage.
Disconnect the USB cord.
(the system will auto-unexport the USB storage)
Use the diags menu to exit and reboot the Kindle.
During the reboot, the Kindle will discover the update file and install it.

Your Kindle should be back to normal operation.

[Merlin09]

OK, I will try this. But something seems seriously wrong since that was my problem. When I typed bist, it never switched to it.

I will try this in a few minutes. My understanding was that bist has its own partition, so wrong again it seems

[Merlin09]

ok, here it is:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.02.26 16:08:18 =~=~=~=~=~=~=~=~=~=~=~=
HW



U-Boot 2009.08-lab126 (Jan 16 2017 - 03:44:52)


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

Temperature:   32 C, calibration data 0x5524e15f

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: Unknown

Boot Reason: [ POR ]

Boot Device: NAND

Board Id: 

S/N: 

I2C:   ready

Invalid board id!  Can't determine system type for RAM init.. bailing!

DRAM:   0 kB

Using default environment


In:    serial

Out:   serial

Err:   serial

Quick Memory Test 0x80000000, 0xffff0000

POST done in 4 ms

Battery voltage: 3938 mV


Hit any key to stop autoboot:  1  0 

uboot > 

uboot > bist

then it stays stuck like this doing nothing.

But reading the log, I see Invalid board id! Can't determine system type for RAM init.. bailing!. Could it be a part of my problem?

[knc1]

Originally Posted by Merlin09

ok, here it is:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.02.26 16:08:18 =~=~=~=~=~=~=~=~=~=~=~=
HW



U-Boot 2009.08-lab126 (Jan 16 2017 - 03:44:52)


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

Temperature:   32 C, calibration data 0x5524e15f

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: Unknown

Boot Reason: [ POR ]

Boot Device: NAND

Board Id: 

S/N: 

I2C:   ready

Invalid board id!  Can't determine system type for RAM init.. bailing!

DRAM:   0 kB

Using default environment


In:    serial

Out:   serial

Err:   serial

Quick Memory Test 0x80000000, 0xffff0000

POST done in 4 ms

Battery voltage: 3938 mV


Hit any key to stop autoboot:  1  0 

uboot > 

uboot > bist

then it stays stuck like this doing nothing.

But reading the log, I see Invalid board id! Can't determine system type for RAM init.. bailing!. Could it be a part of my problem?

Without a correct board id, the u-boot code does not know how to start the dynamic (off SoC) ram.
Just like the message says.
Which is why it reports 0 kbyte of external ram rather than 256 (or 512) mbyte of ram.

bist is too big to run in internal ram, you must have the dynamic ram running so it can be used.

Use the imx_<something> program (which contains the DCD entries to start the dynamic ram).
or
Replace the missing boardid.
You might be able to do that from the minimum (first) sized u-boot.

Post the output of:
?
command (or of the help command, same-same thing)

Read the source code of KindleTool, it contains a fairly complete list of board ids.

= = = = =

How did those device specific values get over-written?
They are stored outside of the partitioned areas of the eMMC.

Did you enter the magic: "Erase All" command to see if it would work?
You almost must have done something like that.

PS:
Yes, "Erase All" does work, and does exactly what you would imagine from its name.

[Merlin09]

You're the man!

No I didn't erase anything. I think there has been a screw up while flashing, but I don't understand....

I entered the serial (with I wrote down), and the board sn (I read the sn on the sticker, right on the board. Now the board is seen as Pinot WFO, and bist does enter bist mode.Now I guess I "just" have to flash the diags and system.

[Merlin09]

so. I flashed both system and diags from ixtab's repository with fastboot.

I entered diags mode, with doesn't launch completly. Here is a log of the end of the boot sequence

[    1.874759] ADC value out of thermistor range! setting display temp to 3 deg C
[    2.017818] KERNEL: I pmic:charger chgina::charger connected
[    2.027778] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    2.051011] MAX77696 Main Charger Driver 1.0.0 Installed
[    2.057084] mmc0: unrecognised EXT_CSD revision 7
[    2.061817] mmc0: error -22 whilst initialising MMC card
[    2.079840] MAX77696 Energy Harvester Driver 1.0.0 Installed
[    2.097718] Freeing init memory: 1036K
3.0.35-lab126 #1 Tue Sep 3 03:12:16 PDT 2013 armv7l
[    2.258141] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    2.294617] mmc0: unrecognised EXT_CSD revision 7
[    2.299367] mmc0: error -22 whilst initialising MMC card
[    2.406435] add wake up source irq 104
[    2.529739] emmc: I def:mmcpartinfo:vendor=toshiba, host=mmc0:
[    2.561138] KERNEL: I pmic:fg battery init::mg config init successful
[    2.568798] max77696-battery max77696-battery.0: Voltage alert     3400mV ... 4260mV
[    2.577253] max77696-battery max77696-battery.0: SOC alert         (disabled)
[    2.589098] mmc0: unrecognised EXT_CSD revision 7
[    2.593827] mmc0: error -22 whilst initialising MMC card
[    3.527134] KERNEL: I pmic:fg battery id check::wario_battery_valid=1
[   62.040090] 
[   62.040099] ADC value out of thermistor range! setting display temp to 3 deg C

I guess this [ 2.299367] mmc0: error -22 whilst initialising MMC card is my next clue. Even if I'm... not very enlightened . I don't know were to go from this point...

If you have (again) a pointer, I'd thrilled.

Thanks again

[knc1]

What part of:
"The main system image is too large to be flashed with fastboot"
do you need help with?

[Merlin09]

lol. I understood. It was just a mistake while resuming what I did.

I flashed both diags images: kernel and system. But not the main system since it wouldn't work.

Then I tried to boot in diags mode, and that's when I received this error.

Without diags, I can't copy the main system image on the internal memory to continue with the next step can I ?

Sorry if I ask silly questions or am starting to get on your nerves.

Edit
I found out from an earlier post of yours that 5.4 may not be the best choice for my board.
I will try a more recent version if I can find one with diags images separated, since I can't upload a whole rootfs from fastboot.
Learning is a slow process, sorry if I'm not that great a student

Edit2

I found out that my kindle (sn prefix 9017) needs at least 5.4.5 version, and the one provided by ixtab is 5.4.0. I will search for more recent

[knc1]

Your device does not have an mmc card.

If your following the directions in the thread about recovering a device with fastboot - then you know you don't need the diags system at all.

Just stop trying to use what is known to be broken (your diags install).
Follow the directions in that 'fastboot' thread, the device there was recovered WITHOUT the diags system even installed.

[Merlin09]

ok, I officially am a fool. I can't find how to do this...
I only found some todo about fastboot including a flash of diags, then reboot in diags mode to copy the system binary in the memory.
But the images from ixtab are 5.4.0, and I found out pw2 with 9017 prefix are not supporting this one. I still need to either find a howto that I didn't enabling me to install without diags, or find an image with separated diags partitions (I only find full rootfs...)
I'm getting closer, but there is still work to do...

[knc1]

https://www.mobileread.com/forums/sh...d.php?t=269099

It contains a lot of O.T. posts, but the full process is described as we (madmaxxx and I) worked it out.
Pay attention to the logs attached, they show what to expect (for a PW-3, but the PW-2 will be very similar).

If you want a main image other than the current one, go to the first post of the current jailbreak, step #7, open spoiler, there find a choice of 5 other firmware versions for the PW-2.

Don't be concerned about the diags system not working, you don't need it to recover the Kindle.

[Merlin09]

OK. I think I understood most of what you did. I'll try it as soon as I finish taking care of my ill cat.