public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Frank Young <young726@hotmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CFG_FLASH_BASE and CFG_MONITOR_BASE question
Date: Wed, 14 Jul 2004 22:00:00 -0700	[thread overview]
Message-ID: <BAY2-F24ZAxIRkaIZXS0001da16@hotmail.com> (raw)

Anyone else can share your success story? I just want to get some clues from 
the similiar cases.

Thanks!

Frank


>From: Wolfgang Denk <wd@denx.de>
>To: "Frank Young" <young726@hotmail.com>
>CC: u-boot-users at lists.sourceforge.net
>Subject: Re: [U-Boot-Users] CFG_FLASH_BASE and CFG_MONITOR_BASE question 
>Date: Thu, 15 Jul 2004 00:41:26 +0200
>
>In message <BAY2-F42kIFqFtucwpX000d8fad@hotmail.com> you wrote:
> > Yes, I did try it out. Seems the u-boot works fine and the example
> > application runs fine in SDRAM. But when I tried to load the kernel, 
>kernel
> > hangs when early_init (in head_4xx.S) is called. So I want to come back 
>to
> > u-boot and double check everything in u-boot is correct.
>
>I think we've been there before. How do  you  know  that  the  kernel
>"hangs", and what exactly means "hangs" here?
>
>Don't tell me again that you added some debug code to toggle LED's or
>write to memory or something like that.
>
>Your "it hangs" may be an "it chrashes because of  your  debug  code"
>with your debug code, and something completely different without it.
>
>Attach a debugger and find out what's really going on.
>
>In a first step, I recommend to re-read the FAQ section.
>
> > BTW, does anyone happen to have early_init problem and solved it? I saw 
>a
>
>Yes. Many people have posted such problems before, and in all cases I
>can remember the only problem was  some  debug  code  that  had  been
>added,  or  the attempt to use tools (or engineers) that have no idea
>what virtual memory is.
>
> > lot of discussions on the internet. But most of them didn't give a final
> > solution. It doesn't matter if we are using same board or CPU. I just 
>want
> > to get some idea of what could be wrong. Any input would be appreciated!
>
>We've been there before. Everything has been said before. follow  the
>advice,  or  ignore  it  -  your  choice. I give up here. I will stop
>reading this thread and replying to it.
>
>
>Wolfgang Denk
>
>--
>Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
>Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
>What about WRITING it first and rationalizing it afterwords?  :-)
>                        - Larry Wall in <8162@jpl-devvax.JPL.NASA.GOV>

_________________________________________________________________
MSN Life Events gives you the tips and tools to handle the turning points in 
your life. http://lifeevents.msn.com

             reply	other threads:[~2004-07-15  5:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15  5:00 Frank Young [this message]
2004-07-15 15:20 ` [U-Boot-Users] CFG_FLASH_BASE and CFG_MONITOR_BASE question Rune Torgersen
  -- 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=BAY2-F24ZAxIRkaIZXS0001da16@hotmail.com \
    --to=young726@hotmail.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