Thread: K3 using serial port problem
View Single Post
Old 06-05-2012, 12:23 PM   #37
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
Hi guys, I was just kidding about the language translation. I have the clip downloaded from youtube so, I can see what should be displayed on my screen. Please look at my post #11. As I said before, I am working with a good unit that boots correctly with my serial adaptor connected. My next step is going to be monitoring the data flow with my scope and see if it ends at the same time I stop getting text on the computer screen. I am beginning to think something is wrong with my minicom setup but, the scope will confirm this.
Disable flow control in minicom.
U-boot may not recognize flow control but /dev/console does and your only getting as far as the kernel initialization of /dev/console if the messages are to be beleived.

Also - this adapter __must__ be 1.8v __not__ 3.3v
It is not known that the Kindle SoC is 3.3v tolerant.
knc1 is offline   Reply With Quote