public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Socrates Socrates" <socrates.socrates@gmail.com>
To: "Socrates Socrates" <socrates.socrates@gmail.com>,
	 	ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Huge memory footprint for a simple "hello world"
Date: Wed, 07 Jun 2006 10:28:00 -0000	[thread overview]
Message-ID: <c3d1d81f0606070327p28bc7601gd1de914c1ef490b@mail.gmail.com> (raw)
In-Reply-To: <20060607095227.GR15066@lunn.ch>

Thank you for all that info you provided me with.

The first 3 steps are fine but "make -s tests" fails:

:~/work/atmel/060606$ make -s tests
headers finished
build finished
/home/socrates/work/atmel/060606/install/lib/libtarget.a(redboot_main.o):
In function `bist':
/opt/ecos/ecos-2.0/packages/redboot/v2_0/src/main.c:626: multiple
definition of `cyg_start'
tests/context.o:/opt/ecos/ecos-2.0/packages/hal/common/v2_0/tests/context.c:116:
first defined here
/opt/ecos/gnutools/arm-elf/bin/../lib/gcc-lib/arm-elf/3.2.1/../../../../arm-elf/bin/ld:
Warning: size of symbol `cyg_start' changed from 12 to 728 in
/home/socrates/work/atmel/060606/install/lib/libtarget.a(redboot_main.o)
collect2: ld returned 1 exit status
make[1]: *** [/home/socrates/work/atmel/060606/install/tests/hal/common/v2_0/tests/context]
Error 1
make: *** [tests] Error 2




On 6/7/06, Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, Jun 07, 2006 at 11:40:54AM +0200, Socrates Socrates wrote:
> > Hi Andrew,
> >
> > Since I have successfully built redboot and uploaded it onto the
> > board. What steps do I need to get a simple hellow world app running?
>
> > I was/am of the impression that from the directory where I built
> > redboot, the only file I need was the target.ld file? Am I correct?
>
> http://ecos.sourceware.org/docs-latest/user-guide/user-guide-programming.html
>
> You first need to build eCos for real applications.
>
> ecosconfig new eb55
> ecosconfig tree
> make -s
>
> What ends up in the install directory is what you need for building
> applications. You will find all the include files the application
> needs, the library containing eCos, the linker file etc.
>
> You can also build the eCos tests
>
> make -s tests
>
> They will then be placed into the install/tests directory tree. The
> following page shows you have you can download the test and run it.
>
> http://ecos.sourceware.org/docs-latest/user-guide/using-commandline-testcase.html
>
> Once you have that working try an hello world:
>
> http://ecos.sourceware.org/docs-latest/user-guide/building-and-running-sample-appliations.html
>
> You download and run this in the same way.
>
>     Andrew
>

-- 
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:[~2006-06-07 10:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 12:03 Socrates Socrates
2006-06-06 13:38 ` Andrew Lunn
2006-06-06 13:58   ` Socrates Socrates
2006-06-06 14:05     ` Andrew Lunn
2006-06-06 14:19       ` Socrates Socrates
2006-06-06 14:54         ` Andrew Lunn
2006-06-07  8:50           ` Socrates Socrates
2006-06-07  8:58             ` Andrew Lunn
2006-06-07  9:40               ` Socrates Socrates
2006-06-07  9:53                 ` Andrew Lunn
2006-06-07 10:28                   ` Socrates Socrates [this message]
2006-06-07 11:11                     ` Andrew Lunn
2006-06-07 11:48                       ` Socrates Socrates
2006-06-07 11:54                         ` Andrew Lunn
2006-06-08 12:28                           ` Socrates Socrates
2006-06-08 12:35                             ` Andrew Lunn
2006-06-08 12:48                               ` Socrates Socrates
2006-06-08 12:55                                 ` AW: " Ram Sudhir Tadavarthi
2006-06-07 11:57                 ` Gary Thomas
2006-06-07 12:09                   ` [ECOS] Python under eCos Evgeny Belyanco
2006-06-07 12:15                     ` Gary Thomas

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=c3d1d81f0606070327p28bc7601gd1de914c1ef490b@mail.gmail.com \
    --to=socrates.socrates@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).