public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Christoph Obermair <cober@cosy.sbg.ac.at>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ecos and ks32c50100
Date: Tue, 31 Jul 2001 07:59:00 -0000	[thread overview]
Message-ID: <20010731100053.A11514@visi.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0107311224460.25175-100000@bock.cosy.sbg.ac.at>

On Tue, Jul 31, 2001 at 12:47:14PM +0200, Christoph Obermair wrote:

> i am working with a ks32c50100-custom-board at the moment. my aim is to
> run a tcp/ip-stack and one or two other small applications on it. the
> board has 128k ram and 512k flash-rom.
>
> i think ecos could be a good solution for my little project.
> 
> so, i've already read some mails in the archive of this list concerning
> ecos on a ks32c50100-board, but none of them was really helpful. is there
> already an existing port?

I'll package up the Ethernet driver and the HAL and put them on
my ftp site today.  I'll send a URL to the list once it's there.

> i read something about a port for the snds100. if this port exists, can i
> use it for my custom-board without any further changes?

You might have to change the routines that deal with the PHY.

The HAL should work as is.  Except: my HAL package only
impliments the RAM-startup model (code is in RAM) and it
assumes that memory has already been configured with RAM
starting at 0.  If you want to run with ROM at 0, it will need
some changes.  At one point I had hacked up the ARM platform
support routines to support that, but I gave up on it for two
reasons:

 1) Running with ROM at 0 prevented me from being able to burn
    flash in my app.

 2) Maintaining a set of parallel, non-standard ARM startup
    code was a pain.

> i saw that there are two tcp/ip-implementaions: the one from
> ecos and another one from tristan gingold. why are there two
> different stacks?

IIRC, Tristan Gingold's stack came out before the "official"
eCos stack.

> besides, do i have enough memory at all to run a tcp/ip-stack
> an my board???


128K of RAM is going to be pretty tight if you want to do
TCP/IP and you're executing out of RAM.  If you're executing
out of ROM, then you should be able to squeek by OK, but the
HAL will need to be modified for that.

Enabling the 8K cache will alleviate most of the slowdown you
would otherwise see running with text in ROM.

-- 
Grant Edwards
grante@visi.com

  parent reply	other threads:[~2001-07-31  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  3:47 Christoph Obermair
2001-07-31  7:21 ` Jonathan Larmour
2001-07-31  7:59 ` Grant Edwards [this message]
2001-07-31 10:16   ` Grant Edwards
2001-08-02  2:13     ` Christoph Obermair
2001-08-02 10:31       ` Jonathan Larmour

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=20010731100053.A11514@visi.com \
    --to=grante@visi.com \
    --cc=cober@cosy.sbg.ac.at \
    --cc=ecos-discuss@sources.redhat.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).