From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18786 invoked by alias); 7 Apr 2013 21:55:12 -0000 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 Received: (qmail 18773 invoked by uid 89); 7 Apr 2013 21:55:12 -0000 X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=BAYES_20,FREEMAIL_FROM,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD autolearn=ham version=3.3.1 Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.22) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Sun, 07 Apr 2013 21:55:11 +0000 Received: from 3capp-gmx-bs37.server.lan ([172.19.170.89]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Lzml3-1UcCw31Qu3-0153qA for ; Sun, 07 Apr 2013 23:55:08 +0200 Received: from [178.190.137.12] by 3capp-gmx-bs37.server.lan with HTTP; Sun Apr 07 23:55:08 CEST 2013 MIME-Version: 1.0 Message-ID: From: "Lukas Riezler" To: ecos-discuss@sourceware.org Content-Type: text/plain; charset=UTF-8 Date: Sun, 07 Apr 2013 21:55:00 -0000 Sensitivity: Normal Content-Transfer-Encoding: quoted-printable Subject: [ECOS] Dependency between eCos and RedBoot X-SW-Source: 2013-04/txt/msg00011.txt.bz2 Hello ecos-guys :-) I have modified both the variant HAL and platform HAL in a minimal way, to = get eCos ported on my FM3 (IAR KickStart Kit: MB9BF506R-SK). Modifying the CDL-Files will be my next step. But now I have a question about the dependency between eCos and RedBoot. If I'm rigt, Redboot comes with two elementary functions: - bootstrapping - debbuging My eval board has a kind of JTAG, so RedBoot's debugging facility isn't rea= lly needed by me. (?) In the documentation and the book it's the suggestion first to run RedBoot. But is RedBoot really essential to get eCos run on my board? Or are there a= ny other ways to get this goal? I don't have any experience with bootsrapping/-loading because I'm quite ne= w in this hardware-closeness business. Maybe I can burn ecos into flash? But I think = for developing this won't be the best way, is it? I have built some libraries for test cases with the config-tool, but I have= never seen any elf-file which I could load on my board - only if I used the RedBoot package! In this case= an elf-file was generated. Okay, what I have now is "redboot.elf". So I have to load RedBoot on my board. But how does RedBoot "load" my minim= al eCos application on the board? Is the following chain of thougt correct? 1) load "redboot.elf" on the board 2) RedBoot can handle the generated ecos-file "libtarget.a" (and eCos will = be started in this way?) Is it possible that anybody throws some light in this issue? :) =C2=A0 With kind regards, Lukas -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss