From: Shawn Jin <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Porting UBoot without UART
Date: Tue, 22 Feb 2005 11:21:01 -0800 [thread overview]
Message-ID: <c3d0340b0502221121c489be4@mail.gmail.com> (raw)
Hi,
We're using some emulation box to develop our SoC. Somehow the UART
will the last component available for firmware development. Without
UART, it's very hard to debug UBoot. Can we "easily" drive a car
without eyes?
But it's not impossible to do that. My first thought about porting
UBoot under this circumstance is to disable the serial driver in UBoot
and to redirect all printf to a fixed memory area, just as what a
circular log buffer does. I'm wondering how much workload this will
be. Is this kind of mechasim already existent in UBoot?
Thank you for your comments.
-Shawn.
next reply other threads:[~2005-02-22 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 19:21 Shawn Jin [this message]
2005-02-22 19:49 ` [U-Boot-Users] Porting UBoot without UART Ladislav Michl
2005-02-24 22:39 ` Wolfgang Denk
2005-02-25 6:40 ` Grant Likely
2005-02-25 7:51 ` Wolfgang Denk
2005-02-25 16:00 ` Grant Likely
2005-02-25 20:09 ` Wolfgang Denk
2005-02-27 11:55 ` Adam Kent
2005-02-25 17:55 ` Shawn Jin
2005-02-25 18:00 ` Grant Likely
2005-02-24 22:38 ` Wolfgang Denk
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=c3d0340b0502221121c489be4@mail.gmail.com \
--to=shawnxjin@gmail.com \
--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