From wry+yaffs@ecoscentric.com Sat Jan 23 12:56:13 2010
Received: from hagrid.ecoscentric.com ([212.13.207.197]
	helo=mail.ecoscentric.com) by stoneboat.aleph1.co.uk with esmtps
	(TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69)
	(envelope-from <wry+yaffs@ecoscentric.com>) id 1NYfX6-0007PR-Eu
	for yaffs@lists.aleph1.co.uk; Sat, 23 Jan 2010 12:56:13 +0000
Received: from localhost (hagrid.ecoscentric.com [127.0.0.1])
	by mail.ecoscentric.com (Postfix) with ESMTP id 35FAE2F7800A
	for <yaffs@lists.aleph1.co.uk>; Sat, 23 Jan 2010 12:56:02 +0000 (GMT)
X-Virus-Scanned: amavisd-new at ecoscentric.com
Received: from mail.ecoscentric.com ([127.0.0.1])
	by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id frNVHOfEb7n2; Sat, 23 Jan 2010 12:55:38 +0000 (GMT)
Received: from [192.168.2.129] (60.66.187.81.in-addr.arpa [81.187.66.60])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	(Authenticated sender: wry@ecoscentric.com)
	by mail.ecoscentric.com (Postfix) with ESMTP id E00692F78004
	for <yaffs@lists.aleph1.co.uk>; Sat, 23 Jan 2010 12:55:37 +0000 (GMT)
Message-ID: <4B5AF1C7.1030600@ecoscentric.com>
Date: Sat, 23 Jan 2010 12:55:35 +0000
From: Ross Younger <wry+yaffs@ecoscentric.com>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)
MIME-Version: 1.0
To: yaffs@lists.aleph1.co.uk
References: <a9db33d91001230301p466d0a0g92774ac7a7e38241@mail.gmail.com>
In-Reply-To: <a9db33d91001230301p466d0a0g92774ac7a7e38241@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 212.13.207.197
X-SA-Exim-Mail-From: wry+yaffs@ecoscentric.com
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	stoneboat.aleph1.co.uk
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=4.5 tests=BAYES_00,SPF_PASS
	autolearn=no version=3.2.5
X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000)
X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk)
Subject: Re: [Yaffs] MKYAFFS : Writing data into YAFFS2 filesystem
X-BeenThere: yaffs@lists.aleph1.co.uk
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: Discussion of YAFFS NAND flash filesystem <yaffs.lists.aleph1.co.uk>
List-Unsubscribe: <http://lists.aleph1.co.uk/cgi-bin/mailman/options/yaffs>,
	<mailto:yaffs-request@lists.aleph1.co.uk?subject=unsubscribe>
List-Archive: <http://lists.aleph1.co.uk/lurker/list/yaffs.html>
List-Post: <mailto:yaffs@lists.aleph1.co.uk>
List-Help: <mailto:yaffs-request@lists.aleph1.co.uk?subject=help>
List-Subscribe: <http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs>,
	<mailto:yaffs-request@lists.aleph1.co.uk?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2010 12:56:13 -0000

Saquib wrote:
> **>> yaffs chunk 64 was not erased
 > [...]
> !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!

> I am just thinking whether mkyaffs2image needs to be executed before 
> writing any data to flash after erasing it. Is my understanding correct 
> or wrong?

A properly erased flash device is ready for use by YAFFS; there is no 
separate "format" step. You should be able to mount the device and use 
it immediately after erasing it; I do. My guess would be that there's 
something funny going on in your MTD driver, that it's not matching your 
flash part in some way.

mkyaffs2image is a host-side tool which prepares a filesystem image to 
be programmed into your flash device later. Unless you know this will be 
useful to you, it won't be.


Ross


