Re: [ECOS] how to configure eCos small enough to run on at91sam7s64

[wb ning <helloningwb at gmail dot com>]

hi, Sergei Gavrikov ,
Thank you very much. you are very helpful. I think you solved most of
my problems. And thank you for giving the link, that's
very clear.

2009/6/1 Sergei Gavrikov <sergei.gavrikov@gmail.com>:
> wb ning writes:
>
> [cut]
>
>> After building the library, i ?use the command " arm-eabi-gcc -g
>> -IBASE_DIR/ecos-work/install/include hello.c
>> -LBASE_DIR/ecos-work/install/lib -Ttarget.ld -nostdlib" to build the
>> HelloWorld test. Then a "a.out" exist.
>
> eCos has `examples' directory which contains the scripts to get up a
> proper Makefile to compile your eCos application.
>
>> But when i use shell command "./a.out", i cann't get any output. Must
>> i have download to the board to run the test?
>
> Of course, if that is _RAM_ startup build, otherwise, you should burn
> the application in the ROM like RedBoot and use JTAG, LED(s), or cross
> the fingers.
>
> And what is a reason to do not try the eCos tests first? Any eCos test
> is more useful than one-line greeting
>
> ?make -s hal/common/v3_0 tests
> ?ls -R install/tests
>
>> i can find the size of the "a.out" is 137k. ?Is this size the same as
>> your said "code/data size", How can i get the *.elf file and use
>> arm-eabi-size to find out the code/data size?
>
> Please, refer to eCos FAQ
> http://ecos.sourceware.org/fom/ecos?file=91
>
> Usually, an eCos application without the eCos kernel is just a few of
> kilobytes:
>
> ?arm-eabi-size install/tests/hal/common/v3_0/tests/*
>
> The tips how to reduce amount of memory for eCos you can find seeking
> through out the eCos discuss list, or just here:
>
> http://opensource.zylin.com/smallecos.html
>
> Sergei
>

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