All of lore.kernel.org
 help / color / mirror / Atom feed
From: CG <christian@mcdi.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] flash erase
Date: Thu, 27 May 2004 14:46:06 -0400	[thread overview]
Message-ID: <060f01c4441a$df400610$6b01a8c0@cc> (raw)
In-Reply-To: 20040527181030.2F350C109F@atlas.denx.de

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@denx.de>
To: "CG" <christian@mcdi.com>
Cc: "Stephan Linz" <linz@mazet.de>; <u-boot-users@lists.sourceforge.net>
Sent: Thursday, May 27, 2004 2:10 PM
Subject: Re: [U-Boot-Users] flash erase


> In message <052401c443f1$218d1550$6b01a8c0@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.
>

  reply	other threads:[~2004-05-27 18:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BSuZH-0005Nd-Ox@sc8-sf-list1.sourceforge.net>
2004-05-26  9:42 ` [U-Boot-Users] is there any irc channel for u-boot Annamalai Prakash
2004-05-26 14:19   ` [U-Boot-Users] flash erase CG
2004-05-26 17:26     ` Wolfgang Denk
2004-05-27  8:06     ` Stephan Linz
2004-05-27 13:47       ` CG
2004-05-27 15:16         ` Stephan Linz
2004-05-27 18:10         ` Wolfgang Denk
2004-05-27 18:46           ` CG [this message]
2004-05-26 17:22   ` [U-Boot-Users] is there any irc channel for u-boot Wolfgang Denk
2004-05-27 19:13 [U-Boot-Users] flash erase VanBaren, Gerald
2004-05-27 20:15 ` CG
  -- strict thread matches above, loose matches on Subject: below --
2004-05-27 20:45 Kerl, John
2004-05-28 20:15 ` CG
2004-05-28 21:35   ` Ed Okerson
2004-05-28 22:04     ` christian at mcdi.com
2004-06-01 14:01 Brad Kemp

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='060f01c4441a$df400610$6b01a8c0@cc' \
    --to=christian@mcdi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.