Quote:
Originally Posted by Cex
Thank you for your reply.
I already had read that thread and all the logs seem to start with Uboot messages.
Although I have good soldering skills I'll check my work again, but I'm afraid somehow I toasted the TX pin in the SoC  |
Think it through -
If the eMMC can not be read -
The start-up code can not learn the DRAM parameters required to start the DRAM -
The SoC will generate a message on the serial port to that effect and shut down.
= = = =
Also see the thread about replacing the eMMC with a larger device.
That larger device came from the factory blank -
Which should be (almost) the same firmware path result as a dead device.
Here, "firmware" means that built into the SoC rom.
= = = =
Buy another KV - they are still being made -
Follow my thread on recovering the initial update_*.bin from it -
Follow that with making a copy of the 'diags' kernel and 'diags' system.
G.M's "get kernels' script will do the kernel recovery for you.
Note:
The 'diags' system and kernel are written to the eMMC while they are still on the tape (before being soldered to the board).
So making your own copy is the only (legal) way to go.
Note:
No hurry on that, your KV will run just fine without a 'diags' kernel and OS installed.
- - - -
What to do with the second KV?
Resell it, give it to a good cause, keep it - your choice.
Don't like the cost involved in the above procedure?
Well maybe it will remind you to make back-ups before doing anything invasive next time.