From: Tomas <Tomas2003@home.se>
To: Nicolas Pitre <nico@cam.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: cfi 0001
Date: Mon, 20 Mar 2006 23:04:44 +0100 [thread overview]
Message-ID: <ops6qfl6emoeqxpi@privat.utfors.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0603201102430.3631@localhost.localdomain>
Nicolas Pitre <nico@cam.org> skrev den Mon, 20 Mar 2006 11:08:19 -0500
(EST):
Hi,
> On Mon, 20 Mar 2006, Tomas E wrote:
>
>> Hi,
>>
>> I have a problem with writing to a Intel Strata flash
>> and then doing a warm reset.
>
> How do you "warm reset" ?
I use the at91rm9200 built in watchdog on a custom board, which is very
convient but there is no external pin from the watchdog to make the
a reset of the flash.
The flash has several partitions starting with the bootloader and
an other partition in the same flash is the jffs2 area.
>
>> When I do a simple write echo "xxxx" > /MyFlash/test.text the flash
>> writes but remain in the state that only 0080 can be read when I
>> ioremap some address in the flash.
>>
>> My problem is that the bootcode also exist in the flash so if the
>> watchdog resets the everything just hang.
>
> How does the watchdog perform its reset?
As described above no reset on external hw (but on periphial on the chip)
then ??? puts pc=0 where the flash is supposed to be located.
>
>> Is this a expected behavior or shouldn't a write put the flash in a
>> readable state (on a hardware level)?
>
> Normally, the flash is put back into read mode with cfi_intelext_reset()
> through a reboot notifier handler, assuming of course that you're
> using a standard kernel interface to reboot your system.
A normal reset power on/off works well but the problem is this watchdog.
Since there is no reset from the watchdog to the flash. I dont think I
cannot do anything useful before this warm reset.
I was hoping to minimize the time when the flash was in a non readable
state but with jffs2/mtdblock/cfi and caching/buffering is there anything
that can be done?
>
>> What should I do to debug this?
>
> First you should tell us a bit more about your board reset.
>
>
> Nicolas
>
Tomas
next prev parent reply other threads:[~2006-03-20 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 14:31 cfi 0001 Tomas E
2006-03-20 15:22 ` Wolfgang Mües
2006-03-20 15:26 ` David Woodhouse
2006-03-20 16:08 ` Nicolas Pitre
2006-03-20 22:04 ` Tomas [this message]
2006-03-20 22:35 ` Nicolas Pitre
2006-03-21 11:43 ` Tomas
2006-03-21 13:01 ` Josh Boyer
2006-03-21 15:55 ` Nicolas Pitre
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=ops6qfl6emoeqxpi@privat.utfors.se \
--to=tomas2003@home.se \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.org \
/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