public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "J. Doo" <doodiexx@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Re: NAND flash mounting problem
Date: Wed, 28 Feb 2007 17:17:18 +0200	[thread overview]
Message-ID: <87f18bad0702280717k6d50b712j9f166eb29f2ca734@mail.gmail.com> (raw)
In-Reply-To: <20070228094631.2e8f7b45@dhcp-252-105.norway.atmel.com>

> > # ./nanddump -l 512 -p /dev/mtd1
> > Block size 16384, page size 512, OOB size 16
> > Dumping data starting at 0x00000000 and ending at 0x00000200...
> > 0x00000000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > <skipping.., all values are ff >
> > 0x000001f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >   OOB Data: ff ff ff ff ff ff ff ff 19 85 20 03 00 00 00 08
> >
> > The 1985 and 2003 parts seem to be wrong endian ??
>
> What are the expected values?

According to the second table in
http://www.linux-mtd.infradead.org/faq/nand.html#L_nand_bootloader
It should be 85 19 03 20 ...

> I suspect there may be something funny going on with the avr32 I/O
> accessors, although I don't know the mtd nand code well enough to know
> more specifically what the problem might be in this case...

I don't think it's because of avr32 i/o, because I have added some
printf's in flash_eraseall to see the buffer to be written to flash
and it's the same, i.e. wrong order.

So I just wanted to have people's opinion before digging the source code.

>
> Did you write the NAND setup code yourself? If so, could you send me a
> patch so that I know how things are set up?

I ported it based on the nand code for at91, it's very basic, just
handles the ALE and CLE lines and chip select...

I'll try to send you a patch later today.

>
> > The processor is big endian,
> > kernel version 2.6.18
>
> Did you apply the Atmel BSP patches or something else? AVR32 isn't
> supported in plain 2.6.18.

Using Atmel's BSP patches.

BR,
J.Doo

  reply	other threads:[~2007-02-28 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28  7:52 NAND flash mounting problem doodiexx doodiexx
2007-02-28  8:41 ` Indrek Kruusa
2007-02-28 15:10   ` J. Doo
2007-02-28 15:18   ` J. Doo
2007-02-28 16:44     ` Indrek Kruusa
2007-02-28  8:46 ` Haavard Skinnemoen
2007-02-28 15:17   ` J. Doo [this message]
2007-02-28 16:06     ` Haavard Skinnemoen
2007-02-28 16:24       ` J. Doo
2007-03-01 10:40         ` Haavard Skinnemoen
2007-03-01 19:45           ` J. Doo

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=87f18bad0702280717k6d50b712j9f166eb29f2ca734@mail.gmail.com \
    --to=doodiexx@gmail.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