From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ims.2wire.com ([206.171.6.87]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1IucpZ-0001vq-10 for linux-mtd@lists.infradead.org; Tue, 20 Nov 2007 18:48:43 -0500 Message-ID: <474372DE.7020707@kenati.com> Date: Tue, 20 Nov 2007 15:50:54 -0800 From: Carlos Munoz MIME-Version: 1.0 To: Ricard Wanderlof Subject: Re: How to map nand chip ? References: <4739FA7A.9050403@kenati.com> <473C9D46.9060007@kenati.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux mtd List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ricard Wanderlof wrote: > Another thing that can cause this is if the ready/busy-pin is not read > properly by the chip driver. Again, the chip will probably respond quickly > to an id request, but when reading or writing the memory array, the access > times will be longer causing failure. > > That was the problem. The ready/busy pin was not working. Somehow, it's always high. For now I added a 20 usec delay and everything works. Thanks, Carlos