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 08:49:13 -0500 [thread overview]
Message-ID: <482AEDD9.7080500@att.net> (raw)
Starting up a new board with a PXA270, the console output from
printf calls in board.c contains garbage, whereas puts works fine.
It appears the vsprintf call in printf works correctly, but printf's
local char buffer has a few alternate correct characters at its
very beginning followed by junk.
Everything else seems to work correctly: this SDRAM area can be written
to with a debugger. But test functions (similar to printf) that copy a
string parameter to a local buffer and then call puts also produce garbage.
Buffers initialized (i.e., char t [12] = "Testing...";) in these
functions will print (with puts) ONLY if their size is <= 32. Their
contents become garbage when other data are copied to them, regardless
of size.
I haven't yet tried to start a ramdisk or image; without correct output
from printf or the debug () macro it would be futile.
Thanks for any ideas.
JP
next reply other threads:[~2008-05-14 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 13:49 JP [this message]
2008-05-14 14:32 ` [U-Boot-Users] PXA270 board startup: printf does not work Jerry Van Baren
2008-05-14 15:11 ` JP
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=482AEDD9.7080500@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