public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Kevin Morfitt" <kevin.morfitt@ntlworld.com>
To: <linux-mtd@lists.infradead.org>
Subject: CLEANMARKER node found at 0x007a4000 has totlen 0xc != normal 0x0
Date: Mon, 11 Jun 2007 17:03:26 +0100	[thread overview]
Message-ID: <009201c7ac42$0cee6ec0$3902a8c0@FRN2> (raw)

Hi

I'm using mtd-utils-1.0.0 on a KB9202B with a 32M NAND flash. /dev/mtd0 is 
mapped as one partition:

[root@KB9202B:~] cat /proc/mtd
dev:    size   erasesize  name
mtd0: 02000000 00004000 "nand_fs"

I create my jffs image using:

mkfs.jffs2 --pad=0x4000 --eraseblock=0x4000 -l --root=kb9202_nfsroot/target_fs 
 -o full_fs.bin

To program the NAND, when I'm mounted via NFS, I do:

[root@KB9202B:~] flash_eraseall -j /dev/mtd0
Erasing 16 Kibyte @ 1ffc000 -- 99 % complete. Cleanmarker written at 
1ffc000.
[root@KB9202B:~] nandwrite -f /dev/mtd0 /full_fs.bin

When I re-boot from MTD I always get lots of messages like "CLEANMARKER node 
found at 0x007a4000 has totlen 0xc != normal 0x0". The board still boots but 
after a few re-boots I end up getting other messages like:

Empty flash at 0x007de204 ends at 0x007de400
JFFS2 notice: (187) check_node_data: wrong data CRC in data node at 
0x007de800: read 0x95b49b87, calculated 0xc429c7e8.

I've seen the other threads on this subjects and tried using '-n' in my 
mkfs.jffs2 command but if I do that nandwrite fails with:

[root@KB9202B:~] Input file is not page aligned
[root@KB9202B:~] Data did not fit into device, due to bad blocks

I've read somewhere else that the "wrong data CRC" message might mean my 
erase size is wrong but I don't know what the erase size should be anyway.

I'd appreciate any advice anyone could give.

Thanks
Kev 

             reply	other threads:[~2007-06-11 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:03 Kevin Morfitt [this message]
2007-06-12  6:08 ` CLEANMARKER node found at 0x007a4000 has totlen 0xc != normal 0x0 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='009201c7ac42$0cee6ec0$3902a8c0@FRN2' \
    --to=kevin.morfitt@ntlworld.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