public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: JP <jp-linux@att.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PXA270 board startup: printf does not work
Date: Wed, 14 May 2008 10:11:57 -0500	[thread overview]
Message-ID: <482B013D.6020206@att.net> (raw)
In-Reply-To: <482AF811.6000400@ge.com>

Jerry Van Baren wrote:
> 
> Your talk about having a corrupted local char buffer confused me.  If it 
> were not for that detail, I would have been positive that you have a 
> problem with handling your UART's Tx busy flag.
> 
> Your symptoms are typical of not waiting for the UART to complete 
> transmitting a character before stuffing the next one in once the UART 
> FIFO is full.  The result is that, if the string has fewer than /n/ 
> characters (/n/ being the depth of the UART's Tx FIFO, possibly a few 
> more), it works OK.  If the string is longer than /n/, it gets corrupted 
> by your s/w overwriting characters in the UART.  Depending on the UART 
> implementation, this could include the one currently being shifted out, 
> resulting in garbage characters.

A very long (already initialized) string prints correctly with puts, so 
I suspect the FIFO implementation is OK.   We're using the FFUART.
> 
> What in your processor is 32 bytes long?  UART FIFO?  Cache line? Hmmmm, 
> could you be having cache consistency problems?  Cache problems would be 
> consistent with garbage in memory.
> 
> BIG WARNING NOTE: Writing memory with a debugger is typically very 
> benign (s.l.o.w.) compared to writing with the processor.  Writing 
> single memory locations with the processor is typically benign compared 
> to a cache line burst read/write.  SDRAM (including DDR/DDR2) 
> initialization problems typically do *not* show up until cache is 
> enabled because it is the burst read/write that violates the "S" in 
> SDRAM (you end up out of sync "synchronous").
> FAQ: <http://www.denx.de/wiki/DULG/SDRAM>

Thanks for those ideas.  We haven't found many examples to compare our 
configuration to, but we did have trouble initially getting the SDRAM 
startup sequence working.  Your description and the wiki entry describe 
what could be happening.

JP

  reply	other threads:[~2008-05-14 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 13:49 [U-Boot-Users] PXA270 board startup: printf does not work JP
2008-05-14 14:32 ` Jerry Van Baren
2008-05-14 15:11   ` JP [this message]
2008-05-27 14:47     ` JP
2008-05-28  2:56       ` Jerry Van Baren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=482B013D.6020206@att.net \
    --to=jp-linux@att.net \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox