From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Larmour To: Alessandro Pinto Cc: ecos-discuss@sourceware.cygnus.com Subject: [ECOS] Re: Configuration tool problem Date: Thu, 01 Jun 2000 09:08:00 -0000 Message-id: <39368A96.5E0B737E@redhat.co.uk> References: <002001bfc9d5$a9f843a0$2901a8c0@21> <393436D7.104D0E0B@redhat.co.uk> <002c01bfca9f$d85197e0$2901a8c0@21> <3935726B.9AF476BC@redhat.co.uk> <008a01bfcc15$5ae24120$28259296@parades.rm.cnr.it> <39367B5B.76DE437A@redhat.co.uk> <01ce01bfcbe2$7cf0b360$2b259296@parades.rm.cnr.it> X-SW-Source: 2000-06/msg00012.html Alessandro Pinto wrote: > > The ecos build now is OK and I tried to compile some file automatic > generated by VCC and all is OK. > > But I'm brave and I'm thinking to use an ARM instuction set simulator. This > simulator need the RTOS library but the ones generated by the configuration > tool (libtarget.a) doesn't work. > There is the possibilities to compile the library for another compiler (in > this case armcc by arm) ? eCos uses features only found in GNU cc, so unfortunately that isn't an option worth pursuing. I believe the right way to go about running eCos with the ARMulator is to do a port of eCos to it. The reason is because eCos does not interwork with Angel on the boards, using the ROM monitor interface for I/O etc. To port eCos, the platform HAL would have to provide low-level communication with RDI/RDP. I don't know in detail how much work would be involved with that. We don't currently have plans to do it ourselves, so a contributed port would be welcome. Jifl -- Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762 "Plan to be spontaneous tomorrow." || These opinions are all my own fault