From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3698 invoked by alias); 8 Sep 2006 16:58:47 -0000 Received: (qmail 3687 invoked by uid 22791); 8 Sep 2006 16:58:45 -0000 X-Spam-Check-By: sourceware.org Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 08 Sep 2006 16:58:38 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1GLjgZ-0007iD-00; Fri, 08 Sep 2006 18:58:35 +0200 Date: Fri, 08 Sep 2006 16:58:00 -0000 To: Gernot Zankl Cc: Bart Veer , ecos-discuss@sources.redhat.com Message-ID: <20060908165835.GL5807@lunn.ch> Mail-Followup-To: Gernot Zankl , Bart Veer , ecos-discuss@sources.redhat.com References: <0F0005CE495E094A96B04D78F24E5A7F385563@mana.decomsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0F0005CE495E094A96B04D78F24E5A7F385563@mana.decomsys.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: Andrew Lunn X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] JFFS2 Access and interrupts X-SW-Source: 2006-09/txt/msg00048.txt.bz2 On Fri, Sep 08, 2006 at 11:59:48AM +0200, Gernot Zankl wrote: > Hi all ! > > > A basic rule of working with flash is that if any code is erasing or > > programming part of the flash then no other code can access it. Some > > flash chips relax that restriction somewhat by providing several > > banks, but at best that is only a partial solution. Flash accesses can > > come from a variety of sources. > > I'm using ROMRAM versin of redboot and the applications runs in RAM, > too. > Are there any calls to the ROM version of the redboot during the > execution > of a "normal" application, which would cause reading access to the flash > ? There shoudn't be. But it is worth checking the interrupt vectors and VV are pointing to RAM addresses not ROM addresses. It could be the ROMRAM startup code is not quite right and its still using ROM addresses. Such a system might run, but experiance problems with interrupts during flash handling. > I want to give the v2 version a try. As far as i've seen, there exists a > flas_v2 branch in the CVS. > Are the modules devs/flash, io/flash and fs/jffs2 the only ones, I've to > upgrade ? If your problem is in Redboot, you might also need the redboot directory from the branch. > I built a test application (heavily based on one of the jffs2 tests), > where > cyclically files (with size f) are allocated, filed with rand()-values, > crc-checked and finally erased. > Starting with a fresh partition (all filled with 0xff) of size S, > it seems that after a number of iterations i, jffs2 produces a lot of > warnings > (see below), where always approx. i * f = S. > The test continues, but most of the time hangs some iterations later. It might be interesting to run this on the synthetic target. It has no interrupts as such, so you can test if this is a jffs2 problem, not a flash problem. Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss