Thread: JBPatch
View Single Post
Old 05-25-2012, 11:32 PM   #117
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
Why are these things so darned delicate? It seems that they brick if you look at them wrong, and the latest firmware update did not help, and perhaps made it worse. I will have to test this noads patch after my kindle decides it wants to boot again.
Guess #1 - Your SoC is running with the SoCVDD set too low:
http://git.freescale.com/git/cgit.cg...09.08_11.11.01
(Too low an internal VDD ruins the noise margins on the internal signals with the external effect of adding a bit of randomness to the device's function.)

In technically correct terms: "darned delicate".

Note that engineering change @ Freescale was made 6 months ago, but...
Such things take time to "trickle down" to the customer level.

Anyone here that can take a look at the Amazon released u-boot code and see if that two line change has made it into what the Kindle(s) are running?
knc1 is offline   Reply With Quote