From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from www2.levante.de ([212.101.151.130] helo=www.levante.de) by canuck.infradead.org with esmtp (Exim 4.43 #1 (Red Hat Linux)) id 1Dcham-0002fa-RR for linux-mtd@lists.infradead.org; Mon, 30 May 2005 06:33:58 -0400 Message-ID: <429AEC25.4000309@fsforth.de> Date: Mon, 30 May 2005 12:34:13 +0200 From: Jonas MIME-Version: 1.0 To: Blair Barnett References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-mtd@lists.infradead.org Subject: Re: nand write problem List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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