public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot running on DDR fails to detect the CFI compliant flash
Date: Wed, 20 Jan 2010 08:05:37 -0500	[thread overview]
Message-ID: <4B56FFA1.9000404@ge.com> (raw)
In-Reply-To: <b9c1f3ac1001200144j67ac441dkea054df16862c776@mail.gmail.com>

Hi Prakash

Please quote properly and don't top post.  Your emails are very hard to 
understand.

prakash bedge wrote:
> Hi Albert and Stefan,
>  
> I have used the proper commands.
> i.e.
> mw.b 0xfc000000 0xf0
> mw.b 0xfc000055 0x98
> md.b 0xfc000010
> But still no positive results.
> Last time I forgot to tell here, that I have commneted the for(;;) loop 
> in "hang" function after flash_init result testing in lib_ppc/board.c 
> and then I am able to run the above commands on uboot prompt.
>  
> 1) You're writing 32-bit words to the chip. At most it should be 16-bit 
> words, possibly even 8-bits. Try mw.w and mw.b.
> Prakash - I tried both but no success.
> How to crosscheck the chipwidth? Can someone tell what is chipwidth and 
> portwidth?
> I believe I am using chipwidth - 16 and portwidth - 8. How to validate 
> this against chipwidth and portwidth?

Number one thing you *MUST* do is read the flash data sheets, especially 
the command interface.  Repeat until you understand.  Then try the QRY 
command sequence by hand in all the various possibilities (see thread 
links below).

* In your hardware, the "55" and "AA" addresses may be shifted by one or 
two bits:
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31735>

* In your hardware, the command byte lane may be one byte wide, two 
bytes wide, or four bytes wide.  This changes the 55/AA addresses and 
which byte lane(s) are used for the command.
   * Do you have 1, 2, or 4 chips on your  board?
   * Is your memory bus 1, 2, or 4 bytes wide?

The thread links below will help explain.  Note that Robert is using the 
BDI, and thus using the BDI memory read/write commands.  You want to use 
u-boot's memory read/write commands instead.

Pay special attention to these posts:
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31588>
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31723>
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31724>
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31730>
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31735>
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31787>
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31738>

Good luck,
gvb

[snip]

  reply	other threads:[~2010-01-20 13:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 13:23 [U-Boot] U-boot running on DDR fails to detect the CFI compliant flash prakash bedge
2010-01-18  8:45 ` Stefan Roese
2010-01-19  6:24   ` prakash bedge
2010-01-19 13:49     ` Stefan Roese
2010-01-19 13:58       ` Jerry Van Baren
2010-01-19 14:19         ` Wolfgang Denk
2010-01-19 16:22         ` prakash bedge
2010-01-19 16:39           ` Stefan Roese
2010-01-19 16:44           ` Albert ARIBAUD
2010-01-20  9:44             ` prakash bedge
2010-01-20 13:05               ` Jerry Van Baren [this message]
2010-01-21 14:23                 ` prakash bedge
2012-02-15  8:14   ` Francisco

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=4B56FFA1.9000404@ge.com \
    --to=gerald.vanbaren@ge.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