public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] eCos Port of Infineon TricCore
@ 2009-09-11 15:57 roman.rycerz
  2009-09-11 17:46 ` Fabian Scheler
  0 siblings, 1 reply; 2+ messages in thread
From: roman.rycerz @ 2009-09-11 15:57 UTC (permalink / raw)
  To: ecos-discuss



Hi

does anyone know the status of the ecos port to tricore ????


r2




Roman F. Rycerz

Continental Automotive Systems
21440 W Lake Cook Road
Deer Park, IL 60010
email: Roman.Rycerz@continental-corporation.com
www.contiautomotive.com


-- 
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] eCos Port of Infineon TricCore
  2009-09-11 15:57 [ECOS] eCos Port of Infineon TricCore roman.rycerz
@ 2009-09-11 17:46 ` Fabian Scheler
  0 siblings, 0 replies; 2+ messages in thread
From: Fabian Scheler @ 2009-09-11 17:46 UTC (permalink / raw)
  To: roman.rycerz; +Cc: ecos-discuss

Hi Roman,

well, the TriCore port done by Thomas Klöber still is not part of the
regular eCos repository. The main reason is the discrepancy between
the C- and C++-API of the eCos kernel: handles that are implemented as
integers are passed to C++ kernel routines and interpreted as
pointers. This is problematic with the TriCore processor as it uses
different registers for data and addresses, thus the handle is always
looked up in the wrong register. No one wanted to put up my suggestion
to define cyg_handle_t as pointer to a cyg_addrword intstead of
cyg_addrword, I have no other suggestion to solve that problem.

We recently used the port to develop a control system for an
electronic highstriker-system
(http://www4.informatik.uni-erlangen.de//Lehre/SS09/V_EZL/Uebung/hau_den_lukas.shtml
- sorry, german only), but we observed some issues regarding
interrupts and context switches (some times a thread that should be
scheduled was not scheduled any more ...). However, we did not have
time to track these issues down.

If Thomas doesn't have any objections and you are interested I could
give read access to our repository containing also the TriCore port.

Ciao, Fabian

2009/9/11  <roman.rycerz@continental-corporation.com>:
>
>
> Hi
>
> does anyone know the status of the ecos port to tricore ????
>
>
> r2
>
>
>
>
> Roman F. Rycerz
>
> Continental Automotive Systems
> 21440 W Lake Cook Road
> Deer Park, IL 60010
> email: Roman.Rycerz@continental-corporation.com
> www.contiautomotive.com
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

--
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:[~2009-09-11 17:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-09-11 15:57 [ECOS] eCos Port of Infineon TricCore roman.rycerz
2009-09-11 17:46 ` Fabian Scheler

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).