public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Socrates Socrates <socrates.socrates@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Huge memory footprint for a simple "hello world"
Date: Wed, 07 Jun 2006 11:57:00 -0000	[thread overview]
Message-ID: <1149681422.15359.78.camel@hermes> (raw)
In-Reply-To: <c3d1d81f0606070240w496bb32br17b8021076318d5a@mail.gmail.com>

On Wed, 2006-06-07 at 11:40 +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?
> 
> Better still if you are aware of a website which clearly shows how to
> build and upload a simple app could you please point it out?
> I have search the websites and the steps I've been following so far is
> what others say have done.

Try: http://www.mlbassoc.com/examples/

> 
> Regards;
> 
> 
> On 6/7/06, Andrew Lunn <andrew@lunn.ch> wrote:
> > On Wed, Jun 07, 2006 at 10:50:51AM +0200, Socrates Socrates wrote:
> > > Hi Andrew,
> > >
> > > The templete is redboot;
> >
> > You should only use the redboot tempate to build redboot.
> > To build applications you need to use a different template.
> >
> >    Andrew
> >

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2006-06-07 11:57 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
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 [this message]
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=1149681422.15359.78.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=socrates.socrates@gmail.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).