[U-Boot-Users] include/flash.h: Entries for Spansion S29JL064H flash?

[Joseph Sacco]

On Thu, 2007-10-18 at 10:00 -0400, Ben Warren wrote:
> Hi Joseph,
>
> Joseph E. Sacco, Ph.D. wrote:
> > Hi,
> >
> > I am new to U-Boot.
> > [Yes... I have been reading the documentation, albeit slowly. There is
> > much to learn.]
> >
> > I need to modify include/flash.h to support Spansion S29JL064H flash
> > memory
> >
> >         http://www.spansion.com/products/S29JL064H.html
> >
> >
> > A search through previous postings to this list did not reveal
> > appropriate values for
> >
> >         * Device ID
> >
> >         * Internal FLASH identification code
> >
> > [Do I need one or the other or both?]
> >
> This chip is CFI compliant. CFI stands for 'Common Flash Interface', and
> means that software can learn the chip's topology via a standard query
> method. In short, you shouldn't need to do anything with flash.h, all
> you need to do is specify in your board's /include/configs/*.h file that
> your board uses CFI. Lots of other boards use it, so look through the
> source to figure out the exact syntax.
>
> regards,
> Ben

===========================================================================
Ben,

Thanks for responding.   I will poke through the source to find the
corrrect syntax, which is a great way to learn about  u-boot.  A simple
grep for CFI offers up some perspective candidates to explore.

FWIW... I am working on a board with
* (1) MPC8270
* (2) 16MB SDRAM [32MB: 4M x 64]
* (2) 8 MB flash chips [16MB: 4M x 32]
* (1) LXT972A PHY [connected to FCC1]

I "inherited" an implementation of u-boot for this board based upon a
pre-release, CVS version of u-boot-1.0.2.  This implementation hacked
the existing files for the MPC8260ADS board rather than creating a new
board type. Some of the generic u-boot files were also hacked to support
the specific processor version and flash type.

 I am slowly working through each hack  in an attempt to understand what
was done and why.  My goal is to define a new board type and then port
the results  to u-boot-1.2.0.  Creating a new board type within the
existing code base was a simple matter of renaming some files and
tweaking a few others.  Porting the results to u-boot-1.2.0 will be more
challenging.  The Fun begins...

Be well,

-Joseph



-- 
drjesacco [at] gmail [dot] com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20071018/4d0611b1/attachment.htm