All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Young <young726@hotmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] A question about sdram_init
Date: Thu, 13 May 2004 20:22:27 -0400	[thread overview]
Message-ID: <BAY2-F138np7Y5pnryM00015182@hotmail.com> (raw)

>Frank, frankly: you must learn to give us some  more  information  if
>you expect useful replies.
>

OK, the system I am using is PPC405 custom board. The board is same as 
WALNUT but install a special purpose I/F in ASIC. That's why I said it is 
similiar as WALNUT. Since that part won't interfere others, it can be 
considered same as WALNUT. The board has 8M bytes SDRAM installed. SDRAM 
address space is 0x0-0x7FFFFFFF. Flast ROM address space is 0xFFC00000 - 
0xFFFFFFFF.


> > > > 1. The sdram() hanged after 2nd line, i.e. after set up 4MB. But it
> > >didn't
> > > > go through 3rd line and didn't return.
>
>For example, until now you didn't bother to tell us which source file
>you are talking about. or what are the characteristics of your board.
>"similiar as WALNUT"? This doesn't mean anything.
>

Sorry, wrong function name. I've corrected in the second post. The problem 
happens in cpu/ppc4xx/sdram.c -> sdram_init().


> > I don't have a debugger. But I do have LEDs on the board, so I simply 
>use
>
>Get a debugger, so you can  singlestep,  check  register  and  memory
>contents, etc.
>

I know. But my boss keep saying learnning to use the debugger is 
time-consuming and refused to buy a debugger for me, which really pissed me 
off. Sigh... But this is the reality - I don't have a debugger and have to 
have to have the u-boot run on my system within one week...


> > >How do you know your code is correct?
> >
> > I didn't write any code. All these three lines were in original
> > sdram_init(). Original sdram_init() tried to detect sdram with different
>
>Which source file  are  you  talking  about?  cpu/ppc4xx/sdram.c?  or
>cpu/ppc4xx/spd_sdram.c? or what?
>

cpu/ppc4xx/sdram.c


> > BTW, I commented out udelay(200). But I don't think it will have any 
>affect.
>
>Why did you do that? RAM chips may have a power  on  delay.  Did  you
>read the RAM manufacturer's users manual?
>

Well, my purpose is just to find out why the 3rd instructions can not get 
through. So I just strip everything which is temporary is not related to 
this purpose. Do you think udelay can be a cause? I really doubt it because 
I've tried both occasions but none of them works.


Thanks!

Frank

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee? 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

             reply	other threads:[~2004-05-14  0:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  0:22 Frank Young [this message]
2004-05-14  7:35 ` [U-Boot-Users] A question about sdram_init Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-05-14  7:36 [U-Boot-Users] U-Boot on LH7A400 Wolfgang Denk
2004-05-14  8:15 ` [U-Boot-Users] A question about sdram_init Stefan Roese
2004-05-13 23:12 Frank Young
2004-05-13 23:39 ` Wolfgang Denk
2004-05-13 18:54 Frank Young
2004-05-13 19:27 ` 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-F138np7Y5pnryM00015182@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.