From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4982 invoked by alias); 3 May 2005 10:14:57 -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 4873 invoked from network); 3 May 2005 10:14:45 -0000 Received: from unknown (HELO anchor-post-36.mail.demon.net) (194.217.242.86) by sourceware.org with SMTP; 3 May 2005 10:14:45 -0000 Received: from calivar.demon.co.uk ([83.104.54.243] helo=xl5.calivar.com) by anchor-post-36.mail.demon.net with esmtp (Exim 4.42) id 1DSuQO-0005ik-Jh; Tue, 03 May 2005 10:14:44 +0000 Received: from xl5.calivar.com (localhost [127.0.0.1]) by xl5.calivar.com (Postfix) with ESMTP id E67503A0DA; Tue, 3 May 2005 11:14:42 +0100 (BST) To: =?utf-8?b?R29uw6dhbG8gQW50dW5lcw==?= Cc: References: <200504262003.j3QK3dex009649@router.bonfrer.thuis> <004801c54abe$f9cb0240$0200a8c0@pcgoncalo> <20050427053432.GY17364@lunn.ch> <001d01c54d35$4b9e05e0$0200a8c0@pcgoncalo> From: Nick Garnett Original-Sender: nickg@ecoscentric.com Date: Tue, 03 May 2005 10:14:00 -0000 In-Reply-To: <001d01c54d35$4b9e05e0$0200a8c0@pcgoncalo> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [ECOS] i386 problem X-SW-Source: 2005-05/txt/msg00019.txt.bz2 Gon=C3=A7alo Antunes writes: > Hello again! >=20 > I tried to start with a plain net template, changed the HAL_STARTUP to > FLOPPY and the error on the "make tests" is the same: >=20 > >> /home/gmma/config_install/lib/vectors.o:/tmp/ccfRQjJM.s: undefined > >> reference > >> to 'hal_saved_interrupt_state' > >> make: leaving directory '/home/gmma/config_build' > >> collect2: ld returned 1 exit status >=20 >=20 > If I put it to RAM, it works fine... >=20 > When I first installed ecos (without any CVS update), the FLOPPY > startup worked fine... >=20 > What can I do? The main problem seems to be with the profiling support that Bart added in March. I'll leave him to decide what to do about it in the repository, but in the interim you could try moving the #endif // CYGPKG_PROFILE_GPROF in hal_misc.c to just after the #endif // SMP I've not tried this, so I have no idea whether it will work. However, FLOPPY startup only allows for applications that occupy the lower 640k of RAM. Given all the packages you want to load, you may find this a bit of a squeeze. You would be better off using the GRUB startup type for large stand-alone programs, since these get loaded into RAM above the 1Mb boundary. During development, you should be using RedBoot and load RAM applications. You should only switch to FLOPPY or GRUB startup when you are ready to turn in to a product, not before. --=20 Nick Garnett eCos Kernel Architect http://www.ecoscentric.com The eCos and RedBoot experts -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss