From: Rune Torgersen <runet@innovsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFG_FLASH_BASE and CFG_MONITOR_BASE question
Date: Thu, 15 Jul 2004 10:20:11 -0500 [thread overview]
Message-ID: <1089904811.29814.19.camel@runet> (raw)
In-Reply-To: <BAY2-F24ZAxIRkaIZXS0001da16@hotmail.com>
On Thu, 2004-07-15 at 00:00, Frank Young wrote:
> Anyone else can share your success story? I just want to get some clues from
> the similiar cases.
Problem is that there could be literally dozens of things wrong...
You will have to use a debugger to find out where linux stops. At least
check the linux output log (see DLUG, this can be read from u-boot after
a reboot, as long as the Memory isn't clobbered)).
A few thing that have bitten me is:
Wrong bd_info struct, Serial ports not configured correct, PCI not
configured correct.
And last but not least of the problems I have encountered... SDRAM....
That it works under U-Boot des NOT mean that it works 100%.... Some
timing problems (for me it was hardware timing) will ONLY show up when
linux is running (because of burst mode), and some only showed up when
doing GCC compiles or other memory intensive operations.
next prev parent reply other threads:[~2004-07-15 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 5:00 [U-Boot-Users] CFG_FLASH_BASE and CFG_MONITOR_BASE question Frank Young
2004-07-15 15:20 ` Rune Torgersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-15 17:13 Frank Young
2004-07-14 22:17 Frank Young
2004-07-14 22:41 ` Wolfgang Denk
2004-07-14 17:58 Frank Young
2004-07-14 20:16 ` 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=1089904811.29814.19.camel@runet \
--to=runet@innovsys.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