View Single Post
Old 09-28-2012, 02:41 AM   #71
cavorite
looped
cavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the endcavorite knows the complete value of PI to the end
 
cavorite's Avatar
 
Posts: 42
Karma: 31420
Join Date: Sep 2006
Location: Milky Way galaxy, Orion-Cygnus arm, Sol-III, North America, USA, FL
Device: PRS-500, K3, DXG, various iDevices
Quote:
Originally Posted by knc1 View Post
I want to get some more information from your machine.

So lets use that functional serial interface port and whatever terminal emulator you have.

Get your communications all setup with the serial port, Kindle, terminal emulator, etc.

Enable the emulator's capture to file feature.
In (Linux) minicom it is in the configuration panels as "Capture File"
In (Windows) ??? I am not sure, it will depend on the application but should be somewhere - perhaps in configuration - session - logging.
Sorry, knowing what you may be using under Windows would not help me, I would have to look up that application's docs - I don't know windows.

This may give what is required at this point:
  • You have communications established over the serial port ;
  • You have set up recording the communications to a (capture, log, transcript, whatever) file ;
  • Use the: "Hold power switch forever" method of getting the Kindle to do a complete restart ;
  • Save the recorded result file ;
  • Start another recording file ;
  • Repeat the complete restart.
Twice? In two capture files?
Yes.
Because I think the DX is one of the machines which alternates between the two boot image files on the machine with each hard re-start.


The image files look as if they have two (2) complete sets of U-Boot environment and kernel images.
All stored in a device physically different than the device that has your broken system image.


zip or tar/gzip the two files, attach to post.
I expect they will tell me what to either do next or what to ask for next.
File is attached, just one. Took awhile. I'm on a Mac, OSX 10.8, using secureCRT to capture the session. Using FTDI TTL-232RG-VREG1V8-WE converter. Only one file because the system is in a loop and can only be interrupted at the U-boot point. The file has basically one iteration of the loop. Hope the information is helpful in spite of this.

I have a new problem that just ate up an additional couple of hours. My serial port has gone silent. With no changes to hardware setup, I suddenly have nothing coming out of the DX. Tried on two other computers with same result. Holding down power key seems to have no effect, though with enough random keypressing I have got into a reboot to happen, and even a recovery console once, but on DX screen only, silence from serial port.

To cover the obvious, I have examined my soldering and nothing has changed as far as I can see. Rebooted, tried on different computer, checked drivers, checked sanity. Research tomorrow.
Attached Files
File Type: gz kdx_loop.gz (3.4 KB, 38 views)
cavorite is offline   Reply With Quote