<div dir="ltr">the most frustrating is that NOTHING output to my minicom,<br><br>IMHO, the reson it not work would be the incorrect uart clock <br>so it may mismatch with the host baudrate setting...<br><br>and also, i confirmed that FR use UART2 as serial console output from wiki<br>
<br><div class="gmail_quote">On Thu, Jul 24, 2008 at 11:57 PM, Andy Green <<a href="mailto:andy@openmoko.com">andy@openmoko.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br></div><div class="Ih2E3d">
Somebody in the thread at some point said:<br>
<br></div><div class="Ih2E3d">
| 2. config uart clock source as PCLK, 16Mhz,<br>
<br></div>
Make sure you set the GPIO registers for these pins to be in peripheral<br>
mode not GPIO. See GPHCON.</blockquote><div> <br>yes, i've enabled those UART to functional mode<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
There's also a peripheral clock mask register CLKCON, it says it resets<br>
to all enabled though.<br>
</blockquote><div><br>and the clock is enable. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
- -Andy<br>
-----BEGIN PGP SIGNATURE-----<div class="Ih2E3d"><br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
Comment: Using GnuPG with Fedora - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br></div>
iEYEARECAAYFAkiIpm4ACgkQOjLpvpq7dMqg8QCfQZxdk4wYkXkg67sH79tSp22e<br>
z/EAn37b59R5KUJ2+GJMqv+NZITLO5y1<br>
=yPco<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div>