Quote:
Originally Posted by hawhill
It tries to upload a) SoC register init values, e.g. for configuring the RAM, and b) uploads a small firmware into memory, which is supposed to do the dumping/flashing. However, the predefined data for a) and for b) is fit for evaluation boards from Freescale, not for the Kindle. Thus, customized versions of these would be needed. Hard work.
|
It should not be much harder than when I built the custom u-boot images for K4/K5 Select Boot. That was just a CD to the uboot directory and a ./configure (with just the right parameters), and a make. It build firmware image file (which contains the RAM init code and firmware image headers), ready to be loaded and run with MfgTool.
I suspect that the K3 is not much different (I hope). Someday, I may even get around to checking it out...
P.S. The Option flags needed to build the uboots is documented in "what we learned debricking my K4" thread linked in the first post of simple debricking...
My custom uboot images just replace the value with a constant after reading the idme bootmode var in the uboot source code. I have 3 versions (main, diags, fastboot). They do not SAVE the new bootmode var, but they do change how the system boots depending on those (forced) values. Simple and easy.
Oh... and I also fixed a bug in the uboot code, which I was sad to see remains broken in newer versions of the source code. They have serious case-conversion problems, so despite the code attempting to (incorrectly) force uppercase on serial numbers and such, it is best to type them correctly.