This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Embedding eCos Application
- To: "K. Young Park" <pkyoung at palmpalm dot co dot kr>
- Subject: Re: [ECOS] Embedding eCos Application
- From: Jesper Skov <jskov at cambridge dot redhat dot com>
- Date: 06 Jul 2001 08:36:31 +0200
- Cc: <ecos-discuss at sources dot redhat dot com>
- References: <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