View Single Post
Old 06-05-2012, 06:11 PM   #43
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
Case solved...... I just used an external 1.8 volt supply and guess what IT WORKS..... this is really strange that I would get data from U-boot but, not the kernel. Guess you guys know what you are talking about. Thanks for all that replied to this thread.
Pins on an SoC, nearly all SoCs, nearly all pins, are programmable.

If the kernel was built with the early printK / early console option(s), then initializing the /dev/console driver would have been __almost__ the first thing it does after being uncompressed and the image starting execution.

Betting that the pin characteristics would be programmed by the kernel driver the same as either the SoC default or those programmed by U-boot is a poor bet.

So what you have learned just adds to our knowledge of the considerations in using this (un-documented for us) hardware.
knc1 is offline   Reply With Quote