From: "Richard Rauch" <rrauch@itrgmbh.de>
To: "'Jürgen Lambrecht'" <J.Lambrecht@televic.com>,
ecos-devel@sourceware.org
Subject: AW: Port to Atmel ARM9 Microcontroller SAM9G45
Date: Thu, 04 Mar 2010 09:38:00 -0000 [thread overview]
Message-ID: <B94D1C2A4766468D9AE763D0129C3ED2@DESKTOPITRGMBH> (raw)
In-Reply-To: <4B8F5EB7.4090402@televic.com>
Dear Jürgen,
in my opinion eCos has some advantages:
- small footprint
- good realtime behaviour
- very short interrupt latency times, minimal overhead for task context
switching
- available for small microcontrollers (arm7,cortex m3)
I have less experience with linux systems, but i think, linux has some
advantages, when the application works with a graphical user interface.
I have been working with eCos for about 10 years already and I have made
very good experiences.
I have made already a port for AT91RM9200 for some high performance
products, but developed some low level products, based on ARM7 controllers,
too.
So eCos is suitable for a wide product range. Have a look to www.vipa.de, a
lot of the products there (PLCs, communication modules, I/O-Modules) are
based on eCos.
Richard
Richard Rauch
email: rrauch@itrgmbh.de
_______________________________________________
ITR GmbH
Informationstechnologie Rauch
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
web: http://www.itrgmbh.de
email: info@itrgmbh.de
Geschaeftsfuehrer: Richard Rauch
Handelsregister: Nuernberg HR B 21676
USt-Id Nr. : DE228051873
_______________________________________________
-----Ursprüngliche Nachricht-----
Von: ecos-devel-owner@ecos.sourceware.org
[mailto:ecos-devel-owner@ecos.sourceware.org] Im Auftrag von Jürgen
Lambrecht
Gesendet: Donnerstag, 4. März 2010 08:18
An: Richard Rauch; ecos-devel@sourceware.org
Betreff: Re: Port to Atmel ARM9 Microcontroller SAM9G4
On 20:59, Richard Rauch wrote:
>
> Dear community,
>
> I want to announce a development project. It is an eCos port to the
> Atmel's
> ARM9 microcontroller family, in particular a port to the SAM9G45.
> It is planned to contribute the result of the project to the eCos
> repository.
>
> I would be very glad to get some response, whether the planned port is
> of common interest!
>
>
Dear Richard,
I am interested, as we also use Atmel ARM processors.
Hey I wonder: why don't you use Linux on such a powerfull ARM9?
We also still use eCos, but more and more I have to defend it against using
Linux instead. Maybe you can help me defending eCos ;-).
Success with it,
Jürgen
---
Jürgen Lambrecht
R&D Engineer
Televic Transport Systems
Tel: +32 (0)51 303045
Fax: +32 (0)51 310670
http://www.televic.com
Televic NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium Company number
0402.757.955 - RPR Kortrijk
next prev parent reply other threads:[~2010-03-04 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 21:12 Port to Atmel ARM9 Microcontroller SAM9G4 Richard Rauch
2010-03-04 7:18 ` Jürgen Lambrecht
2010-03-04 9:38 ` Richard Rauch [this message]
2010-03-07 17:33 ` Port to Atmel ARM9 Microcontroller SAM9G45 Stanislav Meduna
2011-01-17 11:57 ` Mapping of ARM Architecture to Repository Richard Rauch
2011-01-17 16:22 ` John Dallaway
2010-03-04 8:36 ` Port to Atmel ARM9 Microcontroller SAM9G4 John Dallaway
2010-03-04 9:44 ` AW: Port to Atmel ARM9 Microcontroller SAM9G45 Richard Rauch
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=B94D1C2A4766468D9AE763D0129C3ED2@DESKTOPITRGMBH \
--to=rrauch@itrgmbh.de \
--cc=J.Lambrecht@televic.com \
--cc=ecos-devel@sourceware.org \
/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).