public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@redhat.com>
To: Shaun Jackman <shaunj@gray-interfaces.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] CS8900A
Date: Thu, 31 Aug 2000 09:14:00 -0000	[thread overview]
Message-ID: <XFMail.20000831101431.gthomas@redhat.com> (raw)
In-Reply-To: <007b01c01363$9d64e8a0$6801a8c0@gray.internal>

If you have eCos running on this board, RedBoot is just a step away.
Implementing RedBoot will get you (amonst other things):
  * Network downloading and debugging
  * FLASH image and configuration support

If this interests you, please feel free to contact me.  I'd be happy
to help.

On 31-Aug-2000 Shaun Jackman wrote:
> For development purposes we use a bunch of gibberish ESAs (MACs).
> 0x000102030405 is my personal favourite.
> (so if you get some internet trafic from said ESA, drop me an e-mail because
> something's gone terribly wrong)   ; )
> For production purposes, like others have said, you'll need to get an EUI
> from the IEEE.
> 
> On another (somewhat related) note...
> I have an EB40 (w/ AT91R40807, esentially identical to the 40400 with 136KB
> of internal memory instead of 4K) with a RT8019 etherchip (NE2k (NS8390)
> clone).
> There's a known issue with the packaged Angel monitor. I can't connect at
> faster than 9600, and debugging is *DEAD* slow. (read: over two minutes to
> get a 1k memory dump)
> My preferred plan is to get a Jeeni, but they're a little pricey (although
> right now I would shell out the bucks) and there's no stock!
> So, is there another monitor I could flash into it that isn't broken? (gdb
> stub, Cygmon, RedBoot, ...)
> If there isn't one ported already, and I actually find some time to start
> porting, which should I use? Where do I get the source? What's required to
> complete the port? A "RTF-FAQ reply" would be appreciated when acompanied
> with an URL.
> I have TCP/IP (over ethernet) working on my board. Would it be reasonable to
> consider using this for debugging rather than serial?
> 
> Cheers,
> Shaun
> 
> ----- Original Message -----
> From: Carl van Schaik <carl@leg.uct.ac.za>
> To: Ecos Mailing List <ecos-discuss@sourceware.cygnus.com>
> Sent: Thursday, 2000 August 31 06.10
> Subject: [ECOS] CS8900A
> 
> 
>> Hi
>>
>> I have just got ecos running on my own design board using the AT91M40400
>> ARM processor. I have included  CS8900A ethernet chip and I was wondering
>> if anyone knows how to find it's MAC address. We need to add it to the
>> dhcp server before it is allowed to use the network here.
>>
>> thanks
>>
>> Carl van Schaik   <carl@leg.uct.ac.za>
>> -----------------------------------------------------
>> Dept. Electrical Engineering, UCT
>>
>> 621 Menzies Building
>> University of Cape Town
>> Rondebosch
>> Western Cape
>> 7700
>> South Africa
>>
>> Tel: +27 21 650-3467
>> Fax: +27 21 650-3465
>>
>>
> 

  reply	other threads:[~2000-08-31  9:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-31  4:21 Carl van Schaik
2000-08-31  4:26 ` [ECOS] CS8900A] Andrew Lunn
2000-08-31  4:37   ` Gary Thomas
2000-08-31  4:40 ` [ECOS] CS8900A Gary Thomas
2000-08-31  8:54 ` Shaun Jackman
2000-08-31  9:14   ` Gary Thomas [this message]
2000-09-02  1:26 Carl van Schaik

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=XFMail.20000831101431.gthomas@redhat.com \
    --to=gthomas@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=shaunj@gray-interfaces.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).