* [ECOS] MIPS
@ 2001-10-25 4:40 Marc Giraudou - Sun France - Marketing CS
0 siblings, 0 replies; 2+ messages in thread
From: Marc Giraudou - Sun France - Marketing CS @ 2001-10-25 4:40 UTC (permalink / raw)
To: ecos-discuss
Hi all,
I would like to know if someone is developping something for mips 64 bits (nec
vr4122) !!!!!
thanks a lot
Regards
Marc
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ECOS] configtool issue
@ 2005-06-27 1:32 Chris Hiszpanski
2005-06-27 7:19 ` Andrew Lunn
0 siblings, 1 reply; 2+ messages in thread
From: Chris Hiszpanski @ 2005-06-27 1:32 UTC (permalink / raw)
To: ecos-discuss
Hello,
I am new to eCos. I have installed the eCos tools on Windows XP under
Cygwin, following the install instructions presented in the documentation
(II. Installing eCos) exactly. Moving on the part III. Programming with
eCos, I run into problems, in particular when running configtool.
When I start configtool I see a flurry of messages. Here is a snippet of
what I see:
...
ecos.db, package CYGPKG_DEVS_FLASH_POWERPC_TS1000: warning
This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_DEVS_ETH_POWERPC_TS1000 warning
Version subdirectory `ts1000' does not have a CDL script
`ts1000_eth_drivers.cdl'
...
<repeated hundreds of times for various packages>
...
Is this normal?
Where do I go from here?
The documentation does not seem that it is meant to be followed
sequentially. It seems that I should next follow section VI. Configuration
and the Package Repository to create an eCos build tree for my project. Is
this true?
Following section VI, I tried ecosconfig new arm7tdmi. As expected arm7tdmi
is not a valid target. Where are the valid targets lists?
My current goal is to get eCos and its TCP/IP stack running to a pingable
state on my own hardware (see
http://www.its.caltech.edu/~hiszpans/ethphone/ethphone.html for minimal
documentation). I'm somewhat lost as how to do this. Do I need to create a
custom ecos.ecc file for my hardware? Some pointers would be helpful and
appreciated.
Cheers,
Chris
_________________________________________________________________
DonÂt just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ECOS] configtool issue
2005-06-27 1:32 [ECOS] configtool issue Chris Hiszpanski
@ 2005-06-27 7:19 ` Andrew Lunn
2005-06-27 22:35 ` [ECOS] MIPS issue neuwald
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Lunn @ 2005-06-27 7:19 UTC (permalink / raw)
To: Chris Hiszpanski; +Cc: ecos-discuss
On Mon, Jun 27, 2005 at 01:32:10AM +0000, Chris Hiszpanski wrote:
> Hello,
>
> I am new to eCos. I have installed the eCos tools on Windows XP under
> Cygwin, following the install instructions presented in the documentation
> (II. Installing eCos) exactly. Moving on the part III. Programming with
> eCos, I run into problems, in particular when running configtool.
>
> When I start configtool I see a flurry of messages. Here is a snippet of
> what I see:
> ...
> ecos.db, package CYGPKG_DEVS_FLASH_POWERPC_TS1000: warning
> This package does not have any valid version subdirectories.
> ecos.db, package CYGPKG_DEVS_ETH_POWERPC_TS1000 warning
> Version subdirectory `ts1000' does not have a CDL script
> `ts1000_eth_drivers.cdl'
> ...
> <repeated hundreds of times for various packages>
> ...
> Is this normal?
Sort of. Its a bug which appears with recent cygwin packages. See
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000095
You can get an updated version of configtool from
http://www.ecoscentric.com/devzone/configtool.shtml
> Following section VI, I tried ecosconfig new arm7tdmi. As expected arm7tdmi
> is not a valid target. Where are the valid targets lists?
ecos.db in the packages target. arm7tdmi is a processor not a
target. eCos targets are real boards, not processors, since a target
is much more than just the processor.
> My current goal is to get eCos and its TCP/IP stack running to a pingable
> state on my own hardware (see
> http://www.its.caltech.edu/~hiszpans/ethphone/ethphone.html for minimal
> documentation). I'm somewhat lost as how to do this. Do I need to create a
> custom ecos.ecc file for my hardware? Some pointers would be helpful and
> appreciated.
You need to compare your hardware with the other ARM targets and
decide which is the closet. You then need to use that as a starting
point for your port. There is information about porting eCos in
http://ecos.sourceware.org/docs-latest/ref/hal-porting-guide.html
And the book "Embedded Software Development with eCos"
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-06-28 13:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-25 4:40 [ECOS] MIPS Marc Giraudou - Sun France - Marketing CS
2005-06-27 1:32 [ECOS] configtool issue Chris Hiszpanski
2005-06-27 7:19 ` Andrew Lunn
2005-06-27 22:35 ` [ECOS] MIPS issue neuwald
2005-06-28 13:49 ` [ECOS] MIPS neuwald
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).