public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Gonçalo Antunes" <gmma@gmma.net>
To: "Nick Garnett" <nickg@ecoscentric.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] i386 problem
Date: Tue, 03 May 2005 10:37:00 -0000	[thread overview]
Message-ID: <005701c54fcc$0465a4a0$0200a8c0@pcgoncalo> (raw)
In-Reply-To: <m31x8opqem.fsf@xl5.calivar.com>

Thank you, Mr. Nick Garnett.
I will try to do what you said.
I will now try to start using Redboot during the development.

Thank you again.

Gonçalo Antunes.



----- Original Message ----- 
From: "Nick Garnett" <nickg@ecoscentric.com>
To: "Gonçalo Antunes" <gmma@gmma.net>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Tuesday, May 03, 2005 11:14 AM
Subject: Re: [ECOS] i386 problem


Gonçalo Antunes <gmma@gmma.net> writes:

> Hello again!
>
> 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:
>
> >> /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
>
>
> If I put it to RAM, it works fine...
>
> When I first installed ecos (without any CVS update), the FLOPPY
> startup worked fine...
>
> 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.


-- 
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

  reply	other threads:[~2005-05-03 10:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050426204513.30E1BE5BC7@ws7-2.us4.outblaze.com>
2005-04-27  0:21 ` [ECOS] RE: eCos Loader David Bonfrer
2005-04-27  0:33   ` [ECOS] i386 problem Gonçalo Antunes
2005-04-27  6:05     ` Andrew Lunn
2005-04-30  9:57       ` Gonçalo Antunes
     [not found]         ` <20050430171810.GA6601@lunn.ch>
2005-05-02 16:12           ` Gonçalo Antunes
2005-05-02 16:30             ` Andrew Lunn
2005-05-02 16:35               ` Gonçalo Antunes
2005-05-03 10:14         ` Nick Garnett
2005-05-03 10:37           ` Gonçalo Antunes [this message]
2005-05-03 20:30           ` Bart Veer
2005-04-27  8:25   ` [ECOS] RE: eCos Loader Andrew Lunn
2005-04-27 10:28   ` Nick Garnett
2005-04-27 18:06     ` Paul D. DeRocco
2005-04-28 10:06       ` Nick Garnett
2002-05-02  9:04 [ECOS] i386 problem Roland Caßebohm
2002-05-14 14:22 ` Jonathan Larmour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005701c54fcc$0465a4a0$0200a8c0@pcgoncalo' \
    --to=gmma@gmma.net \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=nickg@ecoscentric.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).