From: Vipin Malik <vmalik@danielind.com>
To: Jonas Holmberg <jonas.holmberg@axis.com>
Cc: 'Erwin Authried' <eauth@softsys.co.at>,
"'mtd@infradead.org'" <mtd@infradead.org>
Subject: Re: reset/read mode cmd for AMD compatible flash
Date: Thu, 08 Mar 2001 09:15:10 -0600 [thread overview]
Message-ID: <3AA7A1FE.B07D5797@danielind.com> (raw)
In-Reply-To: E6FE4E054F02D511818E00025558B61D429E7A@cluster01.axis.se
>From the AMD 29LV017 CFI flash data sheet (pg. 16) (talking about the CFI cmd register and commands):
"Writing incorrect address or data values or in the impropper sequence resets the device to reading array data."
Vipin
Jonas Holmberg wrote:
> I _think_ it should be 0xf0 (but 0xff seems to work on AM29LV160DB and DT!?). Isn't it just a typo?
>
> BTW: did you try amd_flash_probe() with your Atmel chip? In that case can you give me manufacturer id, device id and eraseregions info, please? I'd like to add support for as many AMD compatible chips as possible in the AMD driver.
>
> Best regards
> /Jonas
>
> > -----Original Message-----
> > From: Erwin Authried [mailto:eauth@softsys.co.at]
> > Sent: Thursday, March 08, 2001 9:30 AM
> > To: 'mtd@infradead.org'
> > Subject: reset/read mode cmd for AMD compatible flash
> >
> >
> > In cfi-probe.c, it seems that the command 0xff is used to
> > switch the flash
> > into read mode. I have studied several datasheets of AMD
> > compatible flash
> > (AMD29F160, Fujitsu MB29F160, Atmel AT49BV160...), and they specify
> > 0xf0 as the reset mode command. Can anybody please enlighten me?
> >
> > -Erwin
> >
> >
> >
> >
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-08 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 11:11 reset/read mode cmd for AMD compatible flash Jonas Holmberg
2001-03-08 15:15 ` Vipin Malik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-08 8:29 Erwin Authried
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=3AA7A1FE.B07D5797@danielind.com \
--to=vmalik@danielind.com \
--cc=eauth@softsys.co.at \
--cc=jonas.holmberg@axis.com \
--cc=mtd@infradead.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