public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] sam7s64 support and general eCos questions
@ 2006-12-17  1:50 Brent Picasso
  2006-12-17  4:03 ` Andrew Lunn
  0 siblings, 1 reply; 3+ messages in thread
From: Brent Picasso @ 2006-12-17  1:50 UTC (permalink / raw)
  To: ecos-discuss

Hello all,

After quite a bit of research I started flailing my arms so I decided to post my questions here. 

I'm working with an Olimex development board provisioned with a sam7s64 processor ( http://www.olimex.com/dev/sam7-p64.html). I'm using their ARM-USB-OCD with their GCCFD distrubtion of GCC (v 4.0.2)

First with some general questions:



- What is the typical memory overhead required by the eCos kernel? elsewhere I've seen that it may be around 60K. 

- Can I launch my eCos application without redboot? i.e. can I simply
burn my eCos application to flash and expect it to boostrap and launch from flash?


And second, some problems I encountered attempting to compile an eCos application:

I've downloaded the latest from CVS, and configured the kernel in a fairly standard way that should be easily reproduced:

- For the Atmel AT91SAM7S-EK evaluation board
- default package configuration
- Selected the at91sam7s64 variant under the Atmel AT91SAM7 HAL
- Selected (or rather, kept) ROM startup and address in flash the image should live (0x00100000)
- For the conflicts that were presented I accepted the default suggestions.

The build executes fine- however, when I attempt to compile a simple 'do nothing' void main() app I receive the following error:

I've configued a simple 'do nothing' void main() app- when I compile I receive the following:

bash-3.2$ arm-elf-gcc -g -I/ecos-c/projects/cfi/cfi_install/include hello.c -L/ecos-c/projects/cfi/cfi_install/lib -Ttarget.ld -nostdlib/ecos-c/gccfd/gnuarm/bin/../lib/gcc/arm-elf/4.0.2/../../../../arm-elf/bin/ld: address 0x2048bc of a.out section .bss is not within region ram

Correspondingly, when I run the 'make test' against my configured eCos kernel I receive:

make -r -C hal/common/current tests
make[1]: Entering directory `/ecos-c/projects/cfi/cfi_build/hal/common/current'
arm-elf-gcc -L/ecos-c/projects/cfi/cfi_install/lib -Ttarget.ld -o /ecos-c/projects/cfi/cfi_install/tests/hal/common/current/tests/context tests/context.o -mcpu=arm7tdmi -Wl,--gc-sections -Wl,-static -g -nostdlib/ecos-c/gccfd/gnuarm/bin/../lib/gcc/arm-elf/4.0.2/../../../../arm-elf/bin/ld: address 0x2067dc of /ecos-c/projects/cfi/cfi_install/tests/hal/common/current/tests/context section .bss is not within region ram
collect2: ld returned 1 exit status
make[1]: *** [/ecos-c/projects/cfi/cfi_install/tests/hal/common/current/tests/context] Error 1
make[1]: Leaving directory `/ecos-c/projects/cfi/cfi_build/hal/common/current'
make: *** [tests] Error 2

Thank you for any help!

Brent Picasso





__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS] sam7s64 support and general eCos questions
  2006-12-17  1:50 [ECOS] sam7s64 support and general eCos questions Brent Picasso
@ 2006-12-17  4:03 ` Andrew Lunn
  0 siblings, 0 replies; 3+ messages in thread
From: Andrew Lunn @ 2006-12-17  4:03 UTC (permalink / raw)
  To: Brent Picasso; +Cc: ecos-discuss

On Sat, Dec 16, 2006 at 05:50:25PM -0800, Brent Picasso wrote:
> Hello all,
> 
> After quite a bit of research I started flailing my arms so I decided to post my questions here. 
> 
> I'm working with an Olimex development board provisioned with a sam7s64 processor ( http://www.olimex.com/dev/sam7-p64.html). I'm using their ARM-USB-OCD with their GCCFD distrubtion of GCC (v 4.0.2)
> 
> First with some general questions:
> 
> 
> 
> - What is the typical memory overhead required by the eCos kernel? elsewhere I've seen that it may be around 60K. 
> 
> - Can I launch my eCos application without redboot? i.e. can I simply
> burn my eCos application to flash and expect it to boostrap and launch from flash?
> 
> 
> And second, some problems I encountered attempting to compile an eCos application:
> 
> I've downloaded the latest from CVS, and configured the kernel in a fairly standard way that should be easily reproduced:
> 
> - For the Atmel AT91SAM7S-EK evaluation board
> - default package configuration
> - Selected the at91sam7s64 variant under the Atmel AT91SAM7 HAL
> - Selected (or rather, kept) ROM startup and address in flash the image should live (0x00100000)
> - For the conflicts that were presented I accepted the default suggestions.
> 
> The build executes fine- however, when I attempt to compile a simple 'do nothing' void main() app I receive the following error:
> 
> I've configued a simple 'do nothing' void main() app- when I compile I receive the following:
> 
> bash-3.2$ arm-elf-gcc -g -I/ecos-c/projects/cfi/cfi_install/include hello.c -L/ecos-c/projects/cfi/cfi_install/lib -Ttarget.ld -nostdlib/ecos-c/gccfd/gnuarm/bin/../lib/gcc/arm-elf/4.0.2/../../../../arm-elf/bin/ld: address 0x2048bc of a.out section .bss is not within region ram

It has run out of RAM.

The AT91SAM764 has 16Kbytes of RAM. This is too small for eCos
really. The AT91SAM7s256 is much more suitable with 64KBytes of
RAM. Even so, you still have to be careful with RAM usage, make sure
your configure your stacks to be as small as possible. The default 4K
normally wastes space.

         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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS] sam7s64 support and general eCos questions
@ 2006-12-17  4:46 Brent Picasso
  0 siblings, 0 replies; 3+ messages in thread
From: Brent Picasso @ 2006-12-17  4:46 UTC (permalink / raw)
  To: ecos-discuss

Thank you. I was suspecting as much.

Seems like the overhead is
more than this processor can offer. If anyone has an application using
eCos on the Sam7S64 I'd like to see it!

Off to look for alternatives, possibly FreeRTOS.

Best Regards,
Brent

----- Original Message ----
From: Andrew Lunn <andrew@lunn.ch>
To: Brent Picasso <brentpicasso@yahoo.com>
Cc: ecos-discuss@ecos.sourceware.org
Sent: Saturday, December 16, 2006 8:03:20 PM
Subject: Re: [ECOS] sam7s64 support and general eCos questions

On Sat, Dec 16, 2006 at 05:50:25PM -0800, Brent Picasso wrote:
> Hello all,
> 
> After quite a bit of research I started flailing my arms so I decided to post my questions here. 
> 
> I'm working with an Olimex development board provisioned with a sam7s64 processor ( http://www.olimex.com/dev/sam7-p64.html). I'm using their ARM-USB-OCD with their GCCFD distrubtion of GCC (v 4.0.2)
> 
> First with some general questions:
> 
> 
> 
> - What is the typical memory overhead required by the eCos kernel? elsewhere I've seen that it may be around 60K. 
> 
> - Can I launch my eCos application without redboot? i.e. can I simply
> burn my eCos application to flash and expect it to boostrap and launch from flash?
> 
> 
> And second, some problems I encountered attempting to compile an eCos application:
> 
> I've downloaded the latest from CVS, and configured the kernel in a fairly standard way that should be easily reproduced:
> 
> - For the Atmel AT91SAM7S-EK evaluation board
> - default package configuration
> - Selected the at91sam7s64 variant under the Atmel AT91SAM7 HAL
> - Selected (or rather, kept) ROM startup and address in flash the image should live (0x00100000)
> - For the conflicts that were presented I accepted the default suggestions.
> 
> The build executes fine- however, when I attempt to compile a simple 'do nothing' void main() app I receive the following error:
> 
> I've configued a simple 'do nothing' void main() app- when I compile I receive the following:
> 
> bash-3.2$ arm-elf-gcc -g -I/ecos-c/projects/cfi/cfi_install/include hello.c -L/ecos-c/projects/cfi/cfi_install/lib -Ttarget.ld -nostdlib/ecos-c/gccfd/gnuarm/bin/../lib/gcc/arm-elf/4.0.2/../../../../arm-elf/bin/ld: address 0x2048bc of a.out section .bss is not within region ram

It has run out of RAM.

The AT91SAM764 has 16Kbytes of RAM. This is too small for eCos
really. The AT91SAM7s256 is much more suitable with 64KBytes of
RAM. Even so, you still have to be careful with RAM usage, make sure
your configure your stacks to be as small as possible. The default 4K
normally wastes space.

         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





__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-12-17  4:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-12-17  1:50 [ECOS] sam7s64 support and general eCos questions Brent Picasso
2006-12-17  4:03 ` Andrew Lunn
2006-12-17  4:46 Brent Picasso

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).