public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Michael König" <Michael.Koenig@ipcas.de>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problems with cfi_cmdset_0002 and Atmel AT49BV642D
Date: Tue, 08 May 2007 15:04:51 +0200	[thread overview]
Message-ID: <D6B9D8921EDF6299768B8F76@franken3> (raw)
In-Reply-To: <acd2a5930705080449q2930ad50n521b70263d1c2fdb@mail.gmail.com>

Hello Vitaly

>> cse0: Probing a 0x04000000 bytes large window at 0xe0000000.
>
> that's b/c you're supplying too large a window, but that's harmless
> AFAICS.

Strange, I don't think I'm supplying that window size anywhere, so it must 
be some preset range by Axis. I just took a look at the output of a device 
with a smaller Flash and it was the same window.

>> Node totlen on flash (0xffffffff) != totlen from node ref (0x00000044)
>
> I'd check if you have the right width set up first.

Both kernelconfig files have the following settings for the Flash:
CONFIG_ETRAX_FLASH_BUSWIDTH=2
CONFIG_ETRAX_FLASH1_SIZE=8

The kernelconfig for Linux 2.6 also adds CONFIG_ETRAX_NANDFLASH_BUSWIDTH, 
which was set to 1. I didn't think it would matter, since we don't have 
NAND Flashes, just NOR ones. I set it to 2 as well, just to see what 
happens, but I still have the same behaviour.

To be totally sure, I changed the FLASH_BUSWIDTH to 1 and still have the 
same effects. It's a bit strange, I didn't expect it to work at all.

It still bugs me that I cannot find the command sequence that is used in 
do_write_buffer() in my Atmel documentation.

-- 
Mit freundlichen Grüßen
Best regards
Michael König

ipcas GmbH
Wetterkreuz 17
91058 Erlangen, Germany
Tel.: +49 9131 7677-31
Fax: +49 9131 7677-78
mailto:Michael.Koenig@ipcas.de

Geschäftsführer: Dipl.-Ing. S. Sutiono
Sitz der Gesellschaft: Erlangen
Registergericht: Fürth, HBR 3676
WEEE-Reg.-Nr. DE 77202473

Hinweis: Diese E-Mail und etwaige Anlagen können Betriebs- oder
Geschäftsgeheimnisse, dem Anwaltsgeheimnis unterliegen oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail
irrtümlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt.
Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail
und löschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System.
Ebenso dürfen Sie diese E-Mail oder seine Anlagen
nicht kopieren oder an Dritte weitergeben. Vielen Dank.

  reply	other threads:[~2007-05-08 13:04 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 [this message]
2007-05-09 13:34 ` Michael König
2007-05-09 13:46   ` Hans-Christian Egtvedt
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=D6B9D8921EDF6299768B8F76@franken3 \
    --to=michael.koenig@ipcas.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vitalywool@gmail.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