From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19623 invoked by alias); 9 Jun 2005 10:19:16 -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 19614 invoked by uid 22791); 9 Jun 2005 10:19:11 -0000 Received: from mail.jenoptik.com (HELO mail.jenoptik.com) (217.17.196.194) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 09 Jun 2005 10:19:11 +0000 Received: from JO-EX01.JENOPTIK.NET ([10.250.1.4]) by mail.jenoptik.com (8.13.4/8.13.1) with ESMTP id j59AJ5At015636; Thu, 9 Jun 2005 12:19:07 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Jun 2005 10:19:00 -0000 Message-ID: <5A8A17126B73AC4C83968F6C4505E3C50238B375@JO-EX01.JENOPTIK.NET> From: "Neundorf, Alexander" To: "Hans Berglund" Cc: Subject: AW: AW: [ECOS] FLASH access from user program X-SW-Source: 2005-06/txt/msg00067.txt.bz2 Hi, > Von: Hans Berglund [mailto:hb@spacetec.no] >=20 > Hi again >=20 > I have read the thread, and found that this is what I need.=20 > The virtual vector interface currently implements read only. >=20 > But what was the conclusion of the thread? Is it now implemented in The conclusion was: it should be implemented using the VV interface. > eCos, or do I have to get some files from you to add to my=20 > application? >=20 > I read a suggestion of putting the flash updating into the virtual > vector interface. Is this implemented? Not yet. And right now I'm unsure what to do. Transferring all the functionality into redboot and calling it via VV means= adding a lot of opportunities for errors. Right now the code is simple: th= e fis table is directly accessed and manipulated. Using the VV for everythi= ng will introduce some indirections, which will make the code much less obv= ious and straightforward. Having to define some constants manually (e.g. the fis table location) is a= bad thing. At least some config informations should move to the VV.=20 And I also don't want to press fis manipulation into a rw-filesystem, since= that's not the intended use. It's a ro-filesystem, which can be updated wh= en the firmware of the device is updated. > BTW: It seems that a lot of effort is put into this to get it safe. Yes, and it works absolutely reliable for us. Alex -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss