Quote:
Originally Posted by MadMAXXX
For the serial communication i will use PuTTY on Windows 7 x64.
Attached the Log File you asked for.
|
Looking good.
See this part?
Code:
Hit any key to stop autoboot: 0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
If there had been a kernel image to boot -
it would have auto-booted it.
You would have had to "press any key" within 1 second of start-up to have stopped the auto-boot.
There are enough commands available that we could load the initial filesystem image over the serial port line.
Which would take approximately forever.
= = = background = = =
There are two ways that a Linux kernel can be laid out - -
With the kernel as one file and the initial (ram)filesystem as a second file.
(look in your VM's /boot directory to see those examples)
The other way is for those two file to be combined into a single file image.
Amazon/Lab126 builds the kernel/initial filesystem image the second way, as a single file. (Which makes their initramfs code GPLv2 - O.T. at this point.)
= = = =
The initial (ram) filesystem embedded within the kernel image include the "recovery menu".
Although I haven't seen it yet, I expect it to offer an easier way to get the 'main' filesytem image loaded.
So the next step will be to flash the 'main' kernel using fastboot.
At the top directory level where you un-packaged the update package, you should see a directory:
imx60_wario
Inside of that directory there will be a file named:
uImage (or maybe uimage).
**THAT** is the main kernel+initramfs image.
(There is also a copy of the u-boot binary in that directory - you don't need it - the one installed is in fine shape.)
So this step will be to use fastboot to flash that image file.
Yuck - I have forgotten the command - I will have to look it up and that may take awhile - don't hold your breath.
After that - then just re-booting the Kindle should load and run the just installed kernel.
That will (or **should**) fail to find the run-time main filesystem and abort into the "recovery menu".
Note: I don't recall where/when in this boot sequence the firmware checks /var/local and /mnt/us for the proper format.
If it seems to take forever to get to the "recovery menu" - that is expected, the system is re-creating the third and fourth partitions for us.
Keep a capture file setup on the serial port line - just in case something goes wrong or does not work like I expect it to.
Also, because I will need to see what choices that menu has to offer.