From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Wed, 12 Sep 2007 14:13:27 -0400 Subject: [U-Boot-Users] minimum bdi config to read flash on 85xx In-Reply-To: <46E82959.2090107@ovro.caltech.edu> References: <46DDCAED.8080006@ovro.caltech.edu> <46DEDAC0.10602@ovro.caltech.edu> <46DF1D78.2000001@ovro.caltech.edu> <50d8dde80709061403t576d0720lf1461bd6ee9e6730@mail.gmail.com> <46E079E5.5000102@ovro.caltech.edu> <50d8dde80709061841o61fa17ecmcebee9229c696190@mail.gmail.com> <46E0B0A6.8050306@ovro.caltech.edu> <46E82959.2090107@ovro.caltech.edu> Message-ID: <46E82C47.8050708@smiths-aerospace.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de David Hawkins wrote: > Hi Robert, [snip] > Go back to basics first; > > 1. Confirm that accesses to the addresses you believe the > Flash are located generate CE# and OE# > > (I'm sure you did this, but you didn't re-state it) David missed three steps here: 2. Read the flash data sheets, especially the command interface 3. ReRead the flash data sheets, especially the command interface 4. ReReRead the flash data sheets, especially the command interface Robert's statement "Maybe some CFI standard thing?" betrays him. If you (Robert) don't understand what those 0x55 and 0xAA magic numbers are, and especially if you don't understand how your hardware is wired up (one chip, two chips, four chips, 8x wide, 16x wide, 32x wide - note this is a lot of possible combinations), any success will be pure luck. > 5. Use memory commands to read the manufacturer ID > > 6. Use memory commands to write a word > > 7. Use memory commands to erase that sector > > 8. Repeat ****2**** > > 9. Use memory commands to erase the chip > > Then try the software equivalents. > Then try programming U-boot. > > Cheers, > Dave Good luck, ;-) gvb