From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16972 invoked by alias); 31 Jul 2005 20:33:47 -0000 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 Received: (qmail 16879 invoked by uid 22791); 31 Jul 2005 20:33:38 -0000 Received: from sta-206-168-96-204.rockynet.com (HELO hermes.chez-thomas.org) (206.168.96.204) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 31 Jul 2005 20:33:38 +0000 Received: by hermes.chez-thomas.org (Postfix, from userid 2000) id 4440A10001C; Sun, 31 Jul 2005 14:33:36 -0600 (MDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by hermes.chez-thomas.org (Postfix) with ESMTP id 810F8100006; Sun, 31 Jul 2005 14:33:33 -0600 (MDT) From: Gary Thomas To: Edgar Grimberg Cc: eCos Discussion In-Reply-To: <42ECFE3A.9060201@rms.ro> References: <42ECFE3A.9060201@rms.ro> Content-Type: text/plain Date: Sun, 31 Jul 2005 20:33:00 -0000 Message-Id: <1122842012.27647.369.camel@hermes> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [ECOS] JFFS2 no space left on device error X-SW-Source: 2005-07/txt/msg00326.txt.bz2 On Sun, 2005-07-31 at 19:37 +0300, Edgar Grimberg wrote: > Hi, > > I have loaded the jffs2 image provided in the eCos tree onto my board > (EB40A-like) using redboot and the serial port. I made an FIS entry > named JFFS2 with this image. (no errors so far) > After that, using the BDI2000 debugger, I have programmed the jffs2_1 > test onto the board. > It seems that the mounting of the jffs2 image is working OK (at least no > errors on the serial), I get some directory listing (perhaps not OK, > considering the file structure from the support/jffs2 folder): > > : reading directory / > : entry . [mode 016f0001 ino 00000001 nlink 1 size 0] > : entry .. [mode 016f0001 ino 00000001 nlink 1 size 0] > > Creating a file gives me: > > : create file /foo size 202 > : open() returned -1 No space left on device > : write() returned -1 Bad file handle > > and the bad file handle message continues. > > Any hints? When you created the image (in RedBoot), did you make it larger than the actual JFFS2 image that you created? In other words, JFFS2 needs additional FLASH space within the RedBoot (FIS) image in order to create new files (or even rewrite/update existing ones). -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss