<blockquote>
<tt>On Thu, 2007-10-18 at 10:00 -0400, Ben Warren wrote:</tt><br>
<tt><font color="#737373">> Hi Joseph,</font></tt><br>
<tt><font color="#737373">> </font></tt><br>
<tt><font color="#737373">> Joseph E. Sacco, Ph.D. wrote:</font></tt><br>
<tt><font color="#737373">> > Hi, </font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > I am new to U-Boot. </font></tt><br>
<tt><font color="#737373">> > [Yes... I have been reading the documentation, albeit slowly. There is</font></tt><br>
<tt><font color="#737373">> > much to learn.]</font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > I need to modify include/flash.h to support Spansion S29JL064H flash</font></tt><br>
<tt><font color="#737373">> > memory</font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > <a href="http://www.spansion.com/products/S29JL064H.html">http://www.spansion.com/products/S29JL064H.html</a></font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > A search through previous postings to this list did not reveal</font></tt><br>
<tt><font color="#737373">> > appropriate values for</font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > * Device ID</font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > * Internal FLASH identification code</font></tt><br>
<tt><font color="#737373">> ></font></tt><br>
<tt><font color="#737373">> > [Do I need one or the other or both?]</font></tt><br>
<tt><font color="#737373">> > </font></tt><br>
<tt><font color="#737373">> This chip is CFI compliant. CFI stands for 'Common Flash Interface', and </font></tt><br>
<tt><font color="#737373">> means that software can learn the chip's topology via a standard query </font></tt><br>
<tt><font color="#737373">> method. In short, you shouldn't need to do anything with flash.h, all </font></tt><br>
<tt><font color="#737373">> you need to do is specify in your board's /include/configs/*.h file that </font></tt><br>
<tt><font color="#737373">> your board uses CFI. Lots of other boards use it, so look through the </font></tt><br>
<tt><font color="#737373">> source to figure out the exact syntax.</font></tt><br>
<tt><font color="#737373">> </font></tt><br>
<tt><font color="#737373">> regards,</font></tt><br>
<tt><font color="#737373">> Ben</font></tt><br>
<br>
<tt>===========================================================================</tt><br>
<tt>Ben,</tt><br>
<br>
<tt>Thanks for responding. I will poke through the source to find the</tt><br>
<tt>corrrect syntax, which is a great way to learn about u-boot. A simple</tt><br>
<tt>grep for CFI offers up some perspective candidates to explore.</tt><br>
<br>
<tt>FWIW... I am working on a board with </tt><br>
<tt>* (1) MPC8270</tt><br>
<tt>* (2) 16MB SDRAM [32MB: 4M x 64]</tt><br>
<tt>* (2) 8 MB flash chips [16MB: 4M x 32]</tt><br>
<tt>* (1) LXT972A PHY [connected to FCC1]</tt><br>
<br>
<tt>I "inherited" an implementation of u-boot for this board based upon a</tt><br>
<tt>pre-release, CVS version of u-boot-1.0.2. This implementation hacked</tt><br>
<tt>the existing files for the MPC8260ADS board rather than creating a new</tt><br>
<tt>board type. Some of the generic u-boot files were also hacked to support</tt><br>
<tt>the specific processor version and flash type.</tt><br>
<br>
<tt> I am slowly working through each hack in an attempt to understand what</tt><br>
<tt>was done and why. My goal is to define a new board type and then port</tt><br>
<tt>the results to u-boot-1.2.0. Creating a new board type within the</tt><br>
<tt>existing code base was a simple matter of renaming some files and</tt><br>
<tt>tweaking a few others. Porting the results to u-boot-1.2.0 will be more</tt><br>
<tt>challenging. The Fun begins...</tt><br>
<br>
<tt>Be well,</tt><br>
<br>
<tt>-Joseph</tt>
</blockquote>
<br clear="all"><br>-- <br>drjesacco [at] gmail [dot] com