This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RedBoot ROM resource management after loading RAM eCos application.

From: Andrew Lunn <andrew at lunn dot ch>
To: Chuck McManis <cmcmanis at mcmanis dot com>
Cc: ecos-discuss at ecos dot sourceware dot org, Andrew Lunn <andrew at lunn dot ch>
Date: Tue, 21 Feb 2006 21:14:46 +0100
Subject: Re: [ECOS] RedBoot ROM resource management after loading RAM eCos application.
References: <1140478128.24719.ezmlm@ecos.sourceware.org> <001a01c63677$690fa940$6501a8c0@bulbasaur> <20060221131231.GM27143@lunn.ch> <6.1.0.6.0.20060221111831.01ea2580@66.125.189.29>

> Then another thing that came up is that Redboot seems to prefer the serial 
> port for doing diagnostics. Redboot does open up a diagnostics console on 
> ethernet as well (port 9000 by default) and one can connect GDB through 
> that port. If I wanted to have by ethernet driver "pretend" it was two 
> ethernet devices such that Redboot could continue to use one for its 
> diagnostic use and I could use it for my application. Where would I plug 
> that in? 

There is no need for you to do anything. The layers above the ethernet
driver already do all that is needed.

        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

References:
- RedBoot ROM resource management after loading RAM eCos application.
  - From: Reginald Deschrijver
- Re: RedBoot ROM resource management after loading RAM eCos application.
  - From: Andrew Lunn
- Re: RedBoot ROM resource management after loading RAM eCos application.
  - From: Chuck McManis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]