From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Problems with cfi_cmdset_0002 and Atmel AT49BV642D
Date: Wed, 09 May 2007 15:46:19 +0200 [thread overview]
Message-ID: <1178718379.11554.34.camel@localhost.localdomain> (raw)
In-Reply-To: <B2FC9E5F094119A0F71B96EF@franken3>
On Wed, 2007-05-09 at 15:34 +0200, Michael König wrote:
> first of all, going through the GIT archive I found out that the
> cfi_cmdset_0002.c in the latest Axis SDK must be the one from 2006-09-22,
> since the last Atmel changes are present but the newest SST additions
> aren't.
>
> Through some testing I found out that do_write_one_word() works just fine,
> and the main problem seems to be do_write_buffer().
> To make it work without changing too much, I simply added a call to
> do_write_one_word() in the beginning of do_write_buffer() and then return.
> I'm sure it's less efficient that way, but I wanted to get it to work first.
Hmmm, AT49BV642D should not use the do_write_buffer() function at all.
There should be a fixup for this in the kernel.
Is there a "fixup_convert_atmel_pri" function which
<quote>
/* burst write mode not supported */
cfi->cfiq->BufWriteTimeoutTyp = 0;
cfi->cfiq->BufWriteTimeoutMax = 0;
</quote>
This will disable using the "cfi_amdstd_write_buffers" function.
> Since the problem obviously is in do_write_buffer(), I wonder how this
> command sequence works:
>
> cfi_send_gen_cmd(0xAA, cfi->addr_unlock1, chip->start, map, cfi,
> cfi->device_type, NULL);
> cfi_send_gen_cmd(0x55, cfi->addr_unlock2, chip->start, map, cfi,
> cfi->device_type, NULL);
> //cfi_send_gen_cmd(0xA0, cfi->addr_unlock1, chip->start, map, cfi,
> cfi->device_type, NULL);
> /* Write Buffer Load */
> map_write(map, CMD(0x25), cmd_adr);
This is the standard "Word program" command, take a look on page 11 in
the datasheet.
> I wasn't able to find that sequence either in the documentation of my Atmel
> chip, or in AMD or Spansion ones.
> Is this some undocumented command sequence that isn't implemented by Atmel?
> Why isn't the bypass mode used anymore?
The Atmel device has a dual-word write function, but AFAIK AMD
(Spansion) devices can write a lot more with a single command. Thus
AT49BV642D can not use the default AMD command for buffer writes.
> Thanks in advance for any insights that might clear up this issue.
Sorry for a bit incomplete answer, but this flash device is working on
the ATNGW100 kit from Atmel. So it should work for you as well.
--
With kind regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2007-05-09 13:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:44 Problems with cfi_cmdset_0002 and Atmel AT49BV642D Michael König
2007-05-08 11:49 ` Vitaly Wool
2007-05-08 13:04 ` Michael König
2007-05-09 13:34 ` Michael König
2007-05-09 13:46 ` Hans-Christian Egtvedt [this message]
2007-05-10 6:53 ` Michael König
2007-05-10 7:15 ` Hans-Christian Egtvedt
2007-05-10 7:41 ` Michael König
2007-05-10 8:27 ` Haavard Skinnemoen
2007-05-10 10:13 ` Michael König
2007-05-10 10:24 ` Hans-Christian Egtvedt
2007-05-10 10:41 ` Haavard Skinnemoen
2007-08-06 13:41 ` Ricard Wanderlof
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=1178718379.11554.34.camel@localhost.localdomain \
--to=hcegtvedt@atmel.com \
--cc=linux-mtd@lists.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