public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Tomas E" <tomas2003@home.se>
To: x0nishan@ti.com
Cc: linux-mtd@lists.infradead.org, nico@cam.org
Subject: Re: RE: cfi 0001
Date: Tue, 21 Mar 2006 08:20:04 +0100	[thread overview]
Message-ID: <1142925604.72140700tomas2003@home.se> (raw)


Hi, 

>Tomas,
> First you should tell us a bit more about your board reset.
>Just confirm if the warm-reset is linked to the reset pin of strata NOR.

The at91rm9200 has a built in hardware watchdog which has no external 
pin to make use of for a reset of the flash.

The flash is the intel strata 28F640 (rev C)



>CFI command sequences can put the NOR flash into a >state(e.g. in
>buffered write) where the flash contents are not >visible. If the CPU
>resets in the middle of this process and the NOR flash >is not reset back
>to the reset state, and the first instruction is being >executed from
>NOR, then you might face a state where even your >bootloader does not

Yes, I think this is the case but every time I ioremap the flash
0080 show up. I only write a small file but I could never see the
0080 go away. 

I expected the flash to become in a readable state
after a while when the write operation was done.


>work - this is not a fault of the driver or the flash, 
>rather is a problem with the board's signal routing as such.

Yes this is a problem as well. As long as there is no external reset
of the flash there is no 100% garantee but I would like to
minimize the problem.

>
>Regards,
>Nishanth Menon

Tomas

             reply	other threads:[~2006-03-21  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21  7:20 Tomas E [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-21  7:35 Re: cfi 0001 Tomas E
2006-03-21 16:08 ` Nicolas Pitre
2006-03-22 22:46   ` Tomas

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=1142925604.72140700tomas2003@home.se \
    --to=tomas2003@home.se \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nico@cam.org \
    --cc=x0nishan@ti.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox