public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Joe Porthouse" <jporthouse@toptech.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Network driver problem only with larger programs...
Date: Mon, 14 Aug 2006 20:01:00 -0000	[thread overview]
Message-ID: <MDAEMON-F200608141601.AA0102963md50000000034@toptech.com> (raw)


I've been stuck here for a while, so any advice would be greatly
appreciated.

Working with my small application, I am successfully able to manually
configure the SMSC 91C111 driver from my application and everything seems to
work without a problem (ping and socket connections).

When I attempt to do the same in my much larger application, execution only
gets a few lines into my main and locks up.  The "network interface
initialization" call in my application is not even called yet.

If I ifdef out most of the code in my main (causing many functions to be
excluded from the .bin file), the lockup no longer occurs.

The "network initialization" that eCos does seems to be completing
successfully from the debug messages I see, but after a timer tick,
alarm_thread(), do_timeout() and ip_reass(), the execution gets hung up in
an illegal memory reference.

Init device '/dev/ttydiag'
Init tty channel: 288eac
Init device '/dev/haldiag'
HAL/diag SERIAL init
Network stack using 69632 bytes for misc space
                    69632 bytes for mbufs
                    139264 bytes for mbuf clusters
[cyg_net_init] Init: mbinit(0x00000000)
[cyg_net_init] Init: cyg_net_init_devs(0x00000000)
Init device 'lan91cxx_eth0'
[cyg_net_init] Init: loopattach(0x00000000)
[cyg_net_init] Init: ifinit(0x00000000)
[cyg_net_init] Init: domaininit(0x00000000)
[cyg_net_init] Init: cyg_net_add_domain(0x00288b90)
New domain internet at 0x00000000
[cyg_net_init] Init: cyg_net_add_domain(0x00288620)
New domain route at 0x00000000
[cyg_net_init] Init: call_route_init(0x00000000)
[cyg_net_init] Done
1
(something bad happens here...)

My instinct says I am exceeding some memory limit somewhere (stack, heap,
code space, my sanity).  I have increased the main() stack size from 8192 to
32,000 with no luck.  I have a total of 64MB of SDRAM with a program image
size of about 3.2 MB.  Application is run from RAM.  I am not using RedBoot,
but compiling up eCos and my application into a single binary image.

Joe Porthouse
Toptech Systems, Inc.
Longwood, FL 32750



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

             reply	other threads:[~2006-08-14 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 20:01 Joe Porthouse [this message]
2006-08-14 20:04 ` Andrew Lunn
2006-08-29 21:02   ` [ECOS] Network driver problem only with larger programs (ARM adv needed) Joe Porthouse

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=MDAEMON-F200608141601.AA0102963md50000000034@toptech.com \
    --to=jporthouse@toptech.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).