Thx a lot i'll try that at work. So the .elf i obtain from the arm-elf-objcopy command isn't good ? What do i have to do to make the actual file i'll upload to my board ?
On 6/13/07, Andrew Lunn <[EMAIL PROTECTED]> wrote:
On Wed, Jun 13, 2007 at 05:44:00PM +0200, Alexandre wrote: > Well i tried to use the minimal and default settings. > I need thread management, serial drivers, and basic i/o management. > I use the command : arm-elf-objcopy -O ihex file.elf file.hex to make > my footprint. ihex is an ASCII format of "binary", so you cannot just look at the file size. A much better way to get an idea of the footprint is arm-elf-size. [EMAIL PROTECTED]:~/eCos/work$ ecosconfig new at91sam7xek minimalU CYGHWR_HAL_ARM_AT91SAM7, new inferred value at91sam7x256 U CYGHWR_HAL_ARM_AT91, new inferred value AT91SAM7S U CYGHWR_HAL_ARM_AT91_FIQ, new inferred value 1 [EMAIL PROTECTED]:~/eCos/work$ ecosconfig tree [EMAIL PROTECTED]:~/eCos/work$ make -s headers finished build finished [EMAIL PROTECTED]:~/eCos/work$ make -s tests headers finished build finished tests finished [EMAIL PROTECTED]:~/eCos/work$ arm-elf-size install/tests/hal/common/current/tests/basic text data bss dec hex filename 10630 552 33180 44362 ad4a install/tests/hal/common/current/tests/basic So here there is a little over 10K of code in the text segment and 0.5K of data. The bss, which goes in RAM is just under 33K. Andrew
-- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
