From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6536 invoked by alias); 12 Jun 2007 23:30:31 -0000 Received: (qmail 6527 invoked by uid 22791); 12 Jun 2007 23:30:31 -0000 X-Spam-Check-By: sourceware.org Received: from elasmtp-kukur.atl.sa.earthlink.net (HELO elasmtp-kukur.atl.sa.earthlink.net) (209.86.89.65) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 12 Jun 2007 23:30:29 +0000 Received: from [76.167.219.232] (helo=PAULD) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1HyFoh-0001Gm-Av for ecos-discuss@ecos.sourceware.org; Tue, 12 Jun 2007 19:30:27 -0400 From: "Paul D. DeRocco" To: "eCos Discuss" Date: Wed, 13 Jun 2007 13:36:00 -0000 Message-ID: <000901c7ad49$a6a57e70$887ba8c0@PAULD> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook, Build 10.0.6822 X-ELNK-Trace: bd7d5d4e6f8f652c74cfc7ce3b1ad11381c87f5e519606886e752486d01c722254b39780bc060d75350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Configuring EB40A for JFFS2 X-SW-Source: 2007-06/txt/msg00139.txt.bz2 I have an old EB40A (ARM7) board, and am having trouble figuring out how to partition its 2MB flash memory. I already have Redboot burned into the flash, and FIS set up. The bootable version of Redboot is represented by an FIS image called "Redboot", covering the first 128K of flash. Not sure if that was necessary, but it seemed like a Good Idea. I have a boot script which currently just consists of "fis list"; I'll add an "fis load" command later. It doesn't appear as an image in "fis list", but I assume that that's because it's short, and there's some magic that allows short boot scripts to be stored directly in the FIS directory, instead of in an image. (Did I read that somewhere, or did I just make that up?) Anyway, what I want to do next is create an eCos app that uses JFFS2. The rest of my flash, then, must be divided between the area where I store the app, and the area used for JFFS2 file storage. I don't want to store the app inside a JFFS2 file, as I'm content to use Redboot to write each new version of the app into flash manually. I have a vague memory of reading somewhere that there's a way to get JFFS2 to use a named FIS image, rather than having to hard code a start address and length in my eCos app. Is this true? If so, do I first use Redboot to manually create an empty image of the appropriate name, using "fis create -n ...", and then later let Redboot create an image for my app using the rest of the space? Or should I first create an image for my app, possibly padding it for future growth, and then create an empty image for JFFS2 to use out of the remaining space? Next question: with only 2M flash, and with my app written in C++, I don't have a lot of room to spare. I'd like to store my app as GZIPped binary, but my current version of Redboot doesn't have support for that. Among the available packages, I see something called "Zlib compress/decompress". Is that the same thing as GZIP? If I include that, will it automatically add support for the "fis load" command -d option, or do I have to do something else? (I do have a working RAM version of Redboot, which I can use to burn a new ROM version into flash, by the way.) --=20 Ciao, Paul D. DeRocco Paul mailto:pderocco@ix.netcom.com=20 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss