View Single Post
Old 06-05-2012, 08:12 AM   #30
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 BusterBrown View Post
Knci, Fresh battery (green light with charger cable plugged in) Serial connection is soldered to top of serial connector. I reset by removing the battery each time I watch the boot process on the terminal.

hawhill, I just want to snoop around in the K3G file system before trying to repair the bricked unit. I have used USBnet and know there are other ways to get inside the Kindle. I just can't figure out why I can't see anything on my console after Uncompressing Linux ............. If only I understood what "ustawienia portu szeregowego" in Seanik07's video was all about....
Google translate did not answer that for you?
"Serial port settings"
We are way past that point.

- - - -

What we do have is a set of circumstances that does not compute (no pun intended).

IFF:
The machine would boot to normal operation before surgery;
The machine would boot to normal operation after surgery __with serial port connection__
The serial port connection communicates normally with u-boot.
THEN:
The messages you see would not stop at the point they are reported to stop.
But the messages do stop at that point. TILT

So there is something wrong with the conditions as reported.

Here is how to narrow down where / what has happened:

"serial cable soldered to top of serial port connector" -
If that is litterally what you did - remove the two screws holding the top of the serial port connector on - remove serial port with cable still soldered on.
ELSE
Cut the three (there should only be three) wires you soldered to the top of the serial port connector at a place where it will later be convenient to splice them back together (I.E: Leave soldering iron cold).

Now confirm assumption #2
Ensure the machine will still re-boot to normal operation with the serial port connection you have made not connected.

If it fails to re-boot to normal operation (removing the top of the serial port connector will not affect this) -
Then what you saw and reported as the last message, is really the last message.

If it successfully re-boots to normal operation -
Then it is the serial adapter cable (or its attachment to top of connector) that is making the difference.

Things to check for:
Is the serial adapter cable in use one configured for 1.8v serial operation?
If it is a home built adapter cable, please discribe.
If it is a commercial product, name, model and if possible a link to the device description.

There are only three wires connected, Tx, Rx and Gnd.
Adapter cable is powered from the host computer, not from the Kindle. There are K3 serial port connection descriptions "on net" that show a 1.8v connection point but that is wrong - that is a floating CMOS input that can not source more than a few microamps of current.

Very, very carefully inspect the soldered connections for any problems.

re-splice the cut leads (if you had to cut them)

re-connect the cable to the K3, do not connect it to the host computer.
Confirm (again) that the K3 will re-boot to normal operation.

If it does, then (with the K3 powered off) connect the cable to the host computer;
Bring up your terminal emulator;
Configure for the adapter cable;
Power on the K3;
You should see it re-boot to normal operation and also see all of the boot messages on the terminal emulator.

There just isn't that many things that might be wrong after having done the above proceedure to diagnose the source of the reported problem.
knc1 is offline   Reply With Quote