From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6785 invoked by alias); 20 Mar 2007 15:00:26 -0000 Received: (qmail 6766 invoked by uid 22791); 20 Mar 2007 15:00:24 -0000 X-Spam-Check-By: sourceware.org Received: from mail145.messagelabs.com (HELO mail145.messagelabs.com) (216.82.245.115) by sourceware.org (qpsmtpd/0.31) with SMTP; Tue, 20 Mar 2007 15:00:14 +0000 X-VirusChecked: Checked X-Env-Sender: js.stoezel@magellan.aero X-Msg-Ref: server-6.tower-145.messagelabs.com!1174402807!6058916!3 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- Received: (qmail 31121 invoked from network); 20 Mar 2007 15:00:08 -0000 Received: from unknown (HELO on01e201.malca.ds.magellanaerospace.com) (207.49.66.160) by server-6.tower-145.messagelabs.com with SMTP; 20 Mar 2007 15:00:08 -0000 Received: from mb01e201.magellanaerospace.com ([10.1.201.2]) by on01e201.malca.ds.magellanaerospace.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Mar 2007 10:57:58 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 20 Mar 2007 15:00:00 -0000 Message-ID: In-Reply-To: From: "JS Stoezel" To: "Grant Edwards" , 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: RE: [ECOS] Re: Preliminary questions on eCOS X-SW-Source: 2007-03/txt/msg00119.txt.bz2 Hello, Thanks for your answer. We have been looking at FreeRTOS and uc/COSII and where looking for alternate choices, because eCOS comes with added features (FreeRTOS and uC provide limited services. I will have to take a look at XMK. Jean-Sebastien > -----Original Message----- > From: ecos-discuss-owner@ecos.sourceware.org=20 > [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of=20 > Grant Edwards > Sent: Tuesday, March 20, 2007 9:54 AM > To: ecos-discuss@sources.redhat.com > Subject: [ECOS] Re: Preliminary questions on eCOS >=20 > On 2007-03-20, JS Stoezel wrote: >=20 > > I see there is no tool chain for this type of processor (this is=20 > > stated here: http://ecos.sourceware.org/ecos/getstart.html). > > However I can read: "Developers targeting one of the other=20 > > architectures must build a toolchain themselves at present. > > Full instructions for downloading source code and building=20 > a toolchain=20 > > are available.". Doesn't this mean I can port eCOS to the=20 > tool chain I=20 > > am using? >=20 > It means that if you want to target an architecture for which=20 > there aren't a pre-built gcc/binutils tool-chains, you have=20 > to download the gcc/binutils sources and build a tool-chain. >=20 > eCos uses a number of gcc C and C++ extensions as well as=20 > some rather unique binutils features. In theory you could=20 > port eCos to another tool-chain, but it's going to be tough.=20 > People on the mailing list have talked about attempting to do=20 > such a port, but I don't think anybody has reported success. >=20 > I'd probably look at other RTOSes (FreeRTOS, XMK, uC/OS-II)=20 > before I'd start thinking about porting eCos to a 16-bit=20 > processor using a non-gcc tool-chain. Though if you succeed=20 > you'll be the first to do so with either a 16-bit target or a=20 > non-gcc tool-chain, and you'll indeed be rolling in geek-points. >=20 > --=20 > Grant Edwards grante Yow!=20=20 > People humiliating > at a salami! > visi.com=20=20=20=20=20=20=20=20=20=20=20= =20 >=20 >=20 > -- > Before posting, please read the FAQ:=20 > http://ecos.sourceware.org/fom/ecos > and search the list archive:=20 > http://ecos.sourceware.org/ml/ecos-discuss >=20 >=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