From: Sam Song <samsongshu@yahoo.com.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re： why "go 0x0" and "go 0x0c000000" could start u-boot?
Date: Tue, 15 May 2007 13:39:41 +0800 (CST) [thread overview]
Message-ID: <565380.11909.qm@web15908.mail.cnb.yahoo.com> (raw)
In-Reply-To: <46446235.4080403@sina.com>
HoHo_Zhao <hoho_zhao@sina.com> wrote:
> hello, everyone:
>
> (Will somebody write to me to tell me how i can see your replies?)
If you gotten two replies at the same time, it means you can
see my reply and our replies.
> I am sure u-boot was flashed in 0x0c000000, but why "go 0x0" has the
> same effect?!
Probably 0x0 is kind of invalid address for normal access. So
'go 0x0' made CPU in check-stop status and then it restart CPU
like reset from 0x0c000000. Pls check the board memory map
to understand it.
Regards,
Sam
___________________________________________________________
????????-3.5G???20M???
http://cn.mail.yahoo.com
prev parent reply other threads:[~2007-05-15 5:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 12:31 [U-Boot-Users] why "go 0x0" and "go 0x0c000000" could start u-boot? HoHo_Zhao
2007-05-15 5:39 ` Sam Song [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=565380.11909.qm@web15908.mail.cnb.yahoo.com \
--to=samsongshu@yahoo.com.cn \
--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