Quote:
Originally Posted by hostar
|
I tried that last night. It says it successfully downloads code to the k4nt successfully executes it. After doing the exec, the USB port resets and I have to reattach it to my windows VM in Virtualbox. It makes sense that the usb would reset because the "random" code I sent to the kindle was just a copy of the freescale tool (wrong cpu). The tool docs show sending a file called uboot.bin.
I think that my k4nt "brick" problem was caused by a bug in the k4nt diagnostics mode "disable diagnostics" menu code. It normally erases /mnt/us/ENABLE_DIAGS and then it calls "idme" to change boot mode from diag to main. But idme can ALSO change the serial number and the board ID, with different parameters. I think that when the bad code failed to erase the missing ENABLE_DIAGS, it called idme with bad parameters that made it change my serial number and board ID to "1". And uboot does not know how to initialize RAM for a device with board ID "1".
I should have exited diags with a restart instead of disable diags.
Is there any recovery from a corrupted board ID? I do not know memory layout or device port mapping, so USB/HID mode is not much use to me at this time unless I compile my own uboot.The only thing I can think is to run a modified uboot in RAM that treats board ID 1 as a k4nt. Where do I find the k4nt uboot source code?
Does anybody have other ideas?
