public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Frank Pagliughi <fpagliughi@mindspring.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: gmail <jjdebarros@gmail.com>,
	ecos-discuss@ecos.sourceware.org,  "Austin,
	Brian" <Brian.Austin@cirrus.com>
Subject: Re: [ECOS] Re: eCos 3.0 and TS2750
Date: Tue, 02 Aug 2011 14:29:00 -0000	[thread overview]
Message-ID: <4E3809AC.3080209@mindspring.com> (raw)
In-Reply-To: <4E37A1CC.3010702@dallaway.org.uk>

On 08/02/2011 03:05 AM, John Dallaway wrote:
> JJ
>
> gmail wrote:
>
>> On 8/1/2011 3:58 PM, Gary Thomas wrote:
>>> On 2011-08-01 16:36, gmail wrote:
> [ snip ]
>
>>>> I've got cygwin on an XP box and have installed eCos 3.0, but cannot
>>>> find any package for the TS7250 or the ARM9-EP9302 processor.
>>>>
>>>> The s/w that came with the board appears to have the redboot source
>>>> but I think it is a eCos 2.x version.
>>>>
>>>> Is there an existing package for this board or is there a way to
>>>> 'import' it from the 2.x source?
>>>>
>>>> Thanks for any pointers in getting going in the right direction!
>>> This board is not part of the public tree.
>>> You should be able to get the original sources from Technologic Systems
>>>
>> I believe the source for the redboot is on the CD supplied from
>> Technologic Systems, but I believe that it is for eCos 2.x tree.
>>
>> Can I just copy that over to the eCos 3.0 tree that I've installed or
>> does it need to be 'Imported' via the config tool?
> As a starting point, you should be able to copy the directories
> containing the additional eCos HAL and driver packages from your TS7250
> repository to an eCos 3.0 or eCos CVS repository and then copy the
> relevant "package" and "target" declarations from the ecos.db file in
> the root of your TS7250 repository to the eCos 3.0 or eCos CVS ecos.db file.
>
> Note that there is also a patch providing full eCos support (not just
> RedBoot) for a number of EP93xx parts:
>
>    http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000739
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
>

 From what I could tell, the original Technologic boards (TS7200, etc) 
were based pretty closely on the Cirrus eval boards. Technologic started 
their version Redboot using the Cirrus modifications to eCos 2.x from 
about 2005. Cirrus updated their code for a while and released it 
publicly on their web site, but I believe that Technologic stayed with 
the original fork.  A few years back, Brian Austin at Cirrus claimed 
that the company was going to release the code to the public repository, 
but no more was heard from them.

http://sourceware.org/ml/ecos-discuss/2009-04/msg00189.html
http://sourceware.org/ml/ecos-discuss/2009-05/msg00066.html

Frank

-- 
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:[~2011-08-02 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 22:36 [ECOS] " gmail
2011-08-01 22:58 ` Gary Thomas
2011-08-01 23:52   ` gmail
2011-08-02  7:06     ` [ECOS] " John Dallaway
2011-08-02 14:29       ` Frank Pagliughi [this message]
2011-08-02 23:26       ` gmail
2011-08-03  7:38         ` John Dallaway
2011-08-04 18:31           ` gmail

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=4E3809AC.3080209@mindspring.com \
    --to=fpagliughi@mindspring.com \
    --cc=Brian.Austin@cirrus.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jjdebarros@gmail.com \
    --cc=john@dallaway.org.uk \
    /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).