From: Wolfgang Denk <wd@denx.de>
To: "Yuxiao Xi" <xiyuxiao@harbournetworks.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Can not see any infomation on the console when using U-Boot 1.0.0 booting my board
Date: Sat, 06 Dec 2003 16:54:57 +0100 [thread overview]
Message-ID: <20031206155502.A27C8C5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 06 Dec 2003 18:32:20 +0800." <200312061024.EAA19753@lists.linuxppc.org>
In message <200312061024.EAA19753@lists.linuxppc.org> you wrote:
>
> My reference board is Sandpoint X2.
...
> and Sandpoint X2 was booted smoothly.
> Then I modified the serial port information in
> ~~/u-boot1.0.0/include/configs/sandpoint8240.h because the serial port
You should rather create your own board config file.
> address on my board is different from that on Sandpoint X2. Below are my
> modification:
...
> After "make" and "burn u-boot.bin in flash" I reset my board
> and I saw nothing on my console:(
> Any suggestion? Thanks in advance.
Well, what do you expect? Remote debugging through a telepathy link?
Obviously your changes are wrong and/or insufficient to make U-Boot
work on your baord.
Attach your BDI2000, fire up GDB and check what's going on there.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Name one thing windows is better than unix in?
Making money for Microsoft?
-- Randal L. Schwartz in <8cvi5t4c3t.fsf@gadget.cscaper.com>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-06 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 10:32 Can not see any infomation on the console when using U-Boot 1.0.0 booting my board Yuxiao Xi
2003-12-06 15:54 ` Wolfgang Denk [this message]
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=20031206155502.A27C8C5F5F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=xiyuxiao@harbournetworks.com \
/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;
as well as URLs for NNTP newsgroup(s).