[U-Boot-Users] flash erase

[VanBaren, Gerald (AGRE)]

Christian:

It looks like you have your memory controller (BRx/ORx) configured for 32 bits but your actual memory width is 16 bits so the processor is reading 32 bits on every bus cycle, half of which are garbage.

gvb


> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net]On Behalf Of CG
> Sent: Thursday, May 27, 2004 2:46 PM
> To: Wolfgang Denk
> Cc: u-boot-users at lists.sourceforge.net
> Subject: Re: [U-Boot-Users] flash erase
>
>
> I use only one 16-bit flash device.  Also, I wrote some data
> in different
> flash area and it works partially.
>
> I can execute these command :
> cp.b 2000000 10000000 2   => It copies 2 byte (data = 0x0006)
> at 0x10000000
> it seems to work
> cp.b 2000000 10000002 2   => It copies 2 byte at 0x10000002
> cp.b 2000000 10000004 2   => It copies 2 byte at 0x10000004,
> I got problem
> sometimes... it writes only 0x0002 instead of 0x0006
>
> If I type this command:
> cp.b 2000000 10000000 4   => I got problem as I said in my
> previous e-mail
>
> Copy to Flash... not erased at 10000002 (0)
>
> You can see the memory content:
> 10000000: ffff0006 ffffff10 ffff0430 fffffd30
>
> The only problem that I can see now is the home-made PCB that
> I use to test
> the memory flash with the dev.  board.  In fact, I use 56
> long wires to
> connect each IO from the "flash pcb" to the dev. board.  It's
> maybe why the
> communication is unstable.  But I hope that it's the only problem.
>
> Regards
>
> Christian
>
>
> ----- Original Message -----
> From: "Wolfgang Denk" <wd at denx.de>
> To: "CG" <christian at mcdi.com>
> Cc: "Stephan Linz" <linz at mazet.de>;
> <u-boot-users at lists.sourceforge.net>
> Sent: Thursday, May 27, 2004 2:10 PM
> Subject: Re: [U-Boot-Users] flash erase
>
>
> > In message <052401c443f1$218d1550$6b01a8c0 at cc> you wrote:
> > > Do you have an example to know how to erase the flash
> 28F128J3 from
> INTEL?
> >
> > This has little to do with which chip is being used,  but 
> more  with
> > how  your  board is organized, i. e. bus width and how many
> chips are
> > used to form a bank. I think you use 2 chips in 16 bit mode
> to form a
> > 32 bit wide bank. This must be implemented in the driver.
> >
> > > I use 16-bit data width, CS0.  I would like to use this
> flash in order
> to
> > > store u-boot and applications (linux and ramdisk).
> >
> > Are you really sure? To me it looks more as if there ware 2
> x 16  bit
> > devices on a 32 bit wide bus.
> >
> > Best regards,
> >
> > Wolfgang Denk
> >
> > --
> > Software Engineering:  Embedded and Realtime Systems, 
> Embedded Linux
> > Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email:
> wd at denx.de
> > Sorry, but my karma just ran over your dogma.
> >
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market...
> Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************