This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Stand alone ecos kernel boot on armboard running armboot loader


Hi All

I am trying to build a stand alone ecos kernel image for my arm board
that  has arm926ejs core. This means an image which has ecos kernel and
application link to the kernel.

Problem defn:

ecos is designed as such that:

When you build eCos you do not end up with a single kernel image.
Instead you have a library, libtarget.a, which you link with your
application code. At link-time any functionality that is not required,
directly or indirectly by your application, is eliminated. For example
if your application does not need dynamic memory allocation then the
relevant code will not get linked in to your application. Cygnus has
enhanced the GNU linker to operate at the grain of individual linkable
entities such as functions and variables, in order to eliminate
overheads. 

Solution approach:

'stand-alone application' means it is an image which is build by linking
the kernel with an application  together ?
Is it not possible to build a 'stand-alone' kernel running with a shell?


-- since eCos does not have a shell, link the application against the
ecos
library to generate a single self-contained executable that contains
everything. Interactive use is either via RedBoot, or via GDB.

-- HOW to use this concept? anybody has any working examples?



My approach and work done!

1) I have the arm-elf-gcc for ecos-2.0 distribution.
2) I am done with BSP patches for my arm board( CDL files, my_board,
etc) all are patches 
   to ecos-2.0 directory.
3) configtool from ecos-2.0 builds sucessfully and generated libtarget.a
file for my arm board.


work that I would like to do further:

4) Some how create an image with libtarget.a and all ecos kernel library
just specific to my arm board.
   -- HOW do I do that?
5) If , step 4 is done, I want to make this image understand to my
existing boot armboot-1.1.0 loader, if I copy this image to certain
location in flash( by default we are copying  linux 
   image at 0x8000..
   -- How do I proceed? I am kind of stuk with steps 4) and 5)..

Pl, share you knowledge!

Regards
Raja 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]