public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Does U-boot supports Spansion S29GL512P NOR Flash?
Date: Fri, 9 Apr 2010 10:09:48 +0200	[thread overview]
Message-ID: <201004091009.48612.sr@denx.de> (raw)
In-Reply-To: <y2kb9c1f3ac1004090105wf0d01316j87485ebabc7f518d@mail.gmail.com>

On Friday 09 April 2010 10:05:02 prakash bedge wrote:
> >> Does it mean I have to CFI_MTD ot common CFI_DRIVER will works?
> 
> I was asking that do I also need to add below settings in my board config
> file.
> 
> /*
>  * Dynamic MTD partition support
>  */
> #define CONFIG_CMD_MTDPARTS
> #define CONFIG_MTD_DEVICE  /* needed for mtdparts commands */
> #define CONFIG_FLASH_CFI_MTD
> #define MTDIDS_DEFAULT  "nor0=fc000000.flash"

No, you don't need those defines for "normal" FLASH access in U-Boot.
 
> >And you need to configure your access timing for the chip select to the
> >NOR Chip correctly of course.
>
> In which source file I can see present access timings for the chip select.
> In which file I need to do these changes?

This is not really CFI driver related. It platforms/SoC specific. Which CPU 
are you using? Can you access the FLASH chip from your JTAG debugger?
 
> I tried with the below setting but I am getting the same error as flash not
> found. So I am little bit concerned.

What are the error messages? Please post a log.

> Please tell which boards supports the S29GL512P NOR flash, so that I can
> check for reference.

Check kilauea.h for example.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2010-04-09  8:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  5:26 [U-Boot] Does U-boot supports Spansion S29GL512P NOR Flash? prakash bedge
2010-04-09  6:10 ` Stefan Roese
2010-04-09  7:22   ` prakash bedge
2010-04-09  7:35     ` Stefan Roese
2010-04-09  7:55       ` Frank Svendsbøe
2010-04-09  8:05       ` prakash bedge
2010-04-09  8:09         ` Stefan Roese [this message]
2010-04-09  9:10           ` Frank Svendsbøe
2010-04-09 12:11             ` prakash bedge
2010-04-09 13:27               ` Frank Svendsbøe
2010-04-12  4:13                 ` prakash bedge
2010-04-12 17:01                   ` Frank Svendsbøe
2010-04-12 17:15                   ` Frank Svendsbøe
2010-04-13  6:31                     ` prakash bedge
2010-04-13  8:34                       ` Stefan Roese
2010-04-13 11:46                         ` prakash bedge
2010-04-13 12:16                           ` Stefan Roese
2010-04-14  5:03                             ` prakash bedge
2010-04-14  7:38                               ` Frank Svendsbøe
2010-04-14 12:05                               ` Stefan Roese
2010-04-16 14:38                                 ` prakash bedge
2010-04-20  9:25                                   ` prakash bedge
2010-04-09 13:35               ` Stefan Roese
2010-04-12  4:18                 ` prakash bedge
2010-04-12  7:59                   ` Stefan Roese
2012-03-10 10:47   ` Balaji Sivakumar
2012-03-10 18:29     ` Dirk Behme
2012-03-10 19:10     ` Wolfgang Denk
2010-04-09  7:48 ` Frank Svendsbøe
2010-04-09  8:07   ` prakash bedge
2010-04-09  8:23     ` Frank Svendsbøe

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=201004091009.48612.sr@denx.de \
    --to=sr@denx.de \
    --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