public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Retallack, Mark (Siemens)" <mark.retallack@siemens.com>
To: "'Transferencia de Archivos'" <transfers@phaber.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] PPP on eCos(eb40a), continued...
Date: Thu, 16 Oct 2003 07:47:00 -0000	[thread overview]
Message-ID: <F5AFBF4F39DBDD488C5B9B41D48145CC1F944B@plestcl0112.stcl.siemens.co.uk> (raw)

This is not going to be much help, But I think you are right. It sounds like
you are running out of RAM memory. Just the net component on its own without
the PPP stack is large (in embedded terms). 

How much memory have you setup the target to have? 



-----Original Message-----
From: Transferencia de Archivos [mailto:transfers@phaber.com]
Sent: Thursday 16 October 2003 05:49 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] PPP on eCos(eb40a), continued...



Again I used this lines to compile the kernel with "NET" support
> $ecosconfig new eb40a net
> $ecosconfig tree
> $make  
> 
No errors during compiling, still, compiling the examples, the same error 
appeared on all, 

../arm-elf/bin/ld: address 0x85df8 of hello section .bss is not within 
region ram 

Well, I dont know why this happened, but I suppose that the eb40a has not 
enough memory to suppor the stack, I have gotten this error before and was 
when I overpassed the ram limit of the board, therefore, why the error 
appears in a code like  a simple hello-world? 

Or that template NET is not intended to run for the eb40a? 

Thanx you all. 

Xcuze me If the questions has "obvious" answers. I'm still learning the eCos

thing.

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


Siemens Traffic Controls is a division of Siemens plc. Registered No.
727817, England. 
Registered office: Siemens House, Oldbury, Bracknell, Berkshire, RG12 8FZ. 

This communication contains information which is confidential and 
may also be privileged. It is for the exclusive use of the addressee. 
If you are not the addressee please note that any distribution, 
reproduction, copying, publication or use of this communication 
or the information in it is prohibited.  If you have received this 
communication in error, please contact us immediately and also 
delete the communication from your computer. 



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

             reply	other threads:[~2003-10-16  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16  7:47 Retallack, Mark (Siemens) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-17  7:59 Retallack, Mark (Siemens)
2003-10-16 19:06 Transferencia de Archivos
2003-10-17  8:26 ` Eric de Jong
2003-10-16  4:32 [ECOS] PPP on eCos(eb40a) Transferencia de Archivos
2003-10-16  4:48 ` [ECOS] PPP on eCos(eb40a), continued Transferencia de Archivos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F5AFBF4F39DBDD488C5B9B41D48145CC1F944B@plestcl0112.stcl.siemens.co.uk \
    --to=mark.retallack@siemens.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=transfers@phaber.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).