public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@cambridge.redhat.com>
To: "K. Young Park" <pkyoung@palmpalm.co.kr>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Embedding eCos Application
Date: Thu, 05 Jul 2001 23:36:00 -0000	[thread overview]
Message-ID: <otvgl6r2c0.fsf@zoftcorp.adsl.dk> (raw)
In-Reply-To: <DBEKKNGMOENKJBPNCIMFOECHCNAA.pkyoung@palmpalm.com>

>>>>> "K" == K Young Park <pkyoung@palmpalm.co.kr> writes:

K> Hi, all.  I want to embed my eCos application to my SA-1110 based
K> platform.  I ported redboot to the platform and it works fine.  I
K> developed an application using the remote debugging facility of
K> GDB.  Now I want to make the application stand alone, that is, it
K> should run on reset.  Of course I can make my redboot to load the
K> application and execute it, but it requires additional ROM and some
K> HAL codes will be duplicated.  I have tried to include the
K> application to the RedBoot, but the system crashes when it
K> encounters kernel API such as semaphore_wait.  Simple inclusion of
K> CYGPKG_KERNEL does not seem to properly initialize all the kernel
K> stuffs.  Now my question is what modification will be needed to the
K> RedBoot if I want to run an eCos application on the RedBoot?  Or do
K> you have any better idea for making the application stand-alone?
K> Thanks in advance.

Put a RAM startup copy of the app in flash and use RedBoot to load and
execute the image via a startup script.

Alternatively, make a ROM startup version of the application and
put it in the flash where RedBoot is now. This option doesn't allow
for easy updates of the application though.

Jesper

      reply	other threads:[~2001-07-05 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 23:19 K. Young Park
2001-07-05 23:36 ` Jesper Skov [this message]

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=otvgl6r2c0.fsf@zoftcorp.adsl.dk \
    --to=jskov@cambridge.redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=pkyoung@palmpalm.co.kr \
    /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).