nand write problem

nand write problem

[Jonas]

Hi list,

I try to write some files within linux to my flash. But I always get the 
message
nand_write_ecc: Attempt to write not page aligned data
cp: Write Error: Invalid argument

This is my environment:
linux kernel 2.6.11
mtd-snapshot-20050524.tar.bz2
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 
3,3V 8-bit)

What I'm doing wrong?

Thanks for your help.
Jonas

Re: nand write problem

[Thomas Gleixner]

On Wed, 2005-05-25 at 16:29 +0200, Jonas wrote:
> I try to write some files within linux to my flash. But I always get the 
> message
> nand_write_ecc: Attempt to write not page aligned data
> cp: Write Error: Invalid argument

You can not use cp to write to a raw nand flash. NAND must be written
with page aligned data. 

Please read the FAQ and the tech docs on http://linux-mtd.infradead.org

tglx

Re: nand write problem

[Jonas]

Hi blair,
> I believe you need to use the -p (pad) option to nandwrite.
> Please let us see your nandwrite command line.
This is what I tried:

# ./nandwrite --jffs2 /dev/mtd/2 jffs2.img
Use -f option to enforce legacy placement on autoplacement enabled mtd 
device

# ./nandwrite -f /dev/mtd/2 jffs2.img
./nandwrite: illegal option -- f

# ./nandwrite -f --jffs2 /dev/mtd/2 jffs2.img
./nandwrite: illegal option -- f

# ./nandwrite -p /dev/mtd/2 jffs2.img
this takes a long time until it is finished.

then I mount it with
# mount -t jffs2 /dev/mtdblock/2 /mnt/
and get a lot of
CLEANMARKER node found at 0x00000000 has totlen 0xc != normal 0x0

Copy the image with nandwrite is the correct and only way? Or is there 
another possibility?

Jonas

Re: nand write problem

[Blair Barnett]

Hi Jonas,

Thanks for giving us explicit details...

On Mon, 2005-05-30 at 03:34, Jonas wrote:
> Hi blair,
> > I believe you need to use the -p (pad) option to nandwrite.
> > Please let us see your nandwrite command line.
> This is what I tried:
> 
> # ./nandwrite --jffs2 /dev/mtd/2 jffs2.img
> Use -f option to enforce legacy placement on autoplacement enabled mtd 
> device
What version of nandwrite (nandwrite -V) do you have? Version 1.30
supports -f.
> 
> # ./nandwrite -f /dev/mtd/2 jffs2.img
> ./nandwrite: illegal option -- f
> 
> # ./nandwrite -f --jffs2 /dev/mtd/2 jffs2.img
> ./nandwrite: illegal option -- f
> 
> # ./nandwrite -p /dev/mtd/2 jffs2.img
> this takes a long time until it is finished.
If your JFFS2 image has any size to it, I would expect it to take some
time.
> 
> then I mount it with
> # mount -t jffs2 /dev/mtdblock/2 /mnt/
> and get a lot of
> CLEANMARKER node found at 0x00000000 has totlen 0xc != normal 0x0
> 
> Copy the image with nandwrite is the correct and only way? Or is there 
> another possibility?
I've seen the CLEANMARKER errors before. How did you create the JFFS2
partition?

Check out this thread for a little more detail:
http://lists.infradead.org/pipermail/linux-mtd/2005-March/012045.html

Good luck! 

-blair

Re: nand write problem

[Jonas Dietsche]

Hi Blair,

thanks for your help!

>># ./nandwrite --jffs2 /dev/mtd/2 jffs2.img
>>Use -f option to enforce legacy placement on autoplacement enabled mtd 
>>device
> 
> What version of nandwrite (nandwrite -V) do you have? Version 1.30
> supports -f.

> 
>># ./nandwrite -f /dev/mtd/2 jffs2.img
>>./nandwrite: illegal option -- f
>>
>># ./nandwrite -f --jffs2 /dev/mtd/2 jffs2.img
>>./nandwrite: illegal option -- f
>>
>># ./nandwrite -p /dev/mtd/2 jffs2.img
>>this takes a long time until it is finished.
> 
> If your JFFS2 image has any size to it, I would expect it to take some
> time.
> 
>>then I mount it with
>># mount -t jffs2 /dev/mtdblock/2 /mnt/
>>and get a lot of
>>CLEANMARKER node found at 0x00000000 has totlen 0xc != normal 0x0
>>
>>Copy the image with nandwrite is the correct and only way? Or is there 
>>another possibility?
> 
> I've seen the CLEANMARKER errors before. How did you create the JFFS2
> partition?
> 
> Check out this thread for a little more detail:
> http://lists.infradead.org/pipermail/linux-mtd/2005-March/012045.html
> 
> Good luck! 
> 
> -blair
> 

-- 
Jonas Dietsche, FS Forth-Systeme GmbH, www.fsforth.de
Kueferstrasse 8, 79206 Breisach, Germany
Phone: +49 (7667) 908 189, FAX +49 (7667) 908 200

Re: nand write problem

[Jonas]

Uuups, wrong shortcut ;-)

>> What version of nandwrite (nandwrite -V) do you have? Version 1.30
>> supports -f.
I used version 1.30. Peter Grayson just sent a patch.

>>> then I mount it with
>>> # mount -t jffs2 /dev/mtdblock/2 /mnt/
>>> and get a lot of
>>> CLEANMARKER node found at 0x00000000 has totlen 0xc != normal 0x0
>>>
>>> Copy the image with nandwrite is the correct and only way? Or is 
>>> there another possibility?
>>
>>
>> I've seen the CLEANMARKER errors before. How did you create the JFFS2
>> partition?
I used flash_eraseall -j /dev/mtd/2 and then I copied it with the 
command above.

>> Check out this thread for a little more detail:
>> http://lists.infradead.org/pipermail/linux-mtd/2005-March/012045.html
Thanks.

Regards,
Jonas

Re: nand write problem

[Peter Grayson]

> # ./nandwrite -f /dev/mtd/2 jffs2.img
> ./nandwrite: illegal option -- f

The short option (-f) for the --forcelegacy option is broken in the
latest nandwrite. Check out the patch below.

--- nandwrite.c.orig    2005-05-31 09:22:00.000000000 -0600
+++ nandwrite.c 2005-05-31 09:22:08.000000000 -0600
@@ -124,7 +124,7 @@

        for (;;) {
                int option_index = 0;
-               static const char *short_options = "os:ajynqp";
+               static const char *short_options = "os:ajyfnqp";
                static const struct option long_options[] = {
                        {"help", no_argument, 0, 0},
                        {"version", no_argument, 0, 0},