public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Lars Poeschel <larsi@wh2.tu-dresden.de>
To: ecos-discuss@ecos.sourceware.org
Cc: Vladimir Nikolov <vladimir.nikolov@uni-ulm.de>
Subject: Re: [ECOS] eCos port for MPC5567 (e200z6)
Date: Tue, 02 Dec 2008 22:30:00 -0000	[thread overview]
Message-ID: <200812021828.18732.larsi@wh2.tu-dresden.de> (raw)
In-Reply-To: <49356198.5020608@uni-ulm.de>

[-- Attachment #1: Type: text/plain, Size: 2322 bytes --]

Am Dienstag, 2. Dezember 2008 schrieb Vladimir Nikolov:
> >>> I've done a port to the MB91302 controller, which is a predecessor. It
> >>> shouldn't be much effort to do a MB91460 port based on that.
> >>
> >> How much time did you spend making it?
> >
> > I think in sum it was about 3 - 4 months but you can not compare this
> > because I had to do the whole port including the initial fr30
> > architecture port, mb91302 variant and a platform.
> > You now have in both cases a running archtitecture port (powerpc or fr30)
> > and a variant that is very close to what you need. So most of the porting
> > effort is already done. What you have to do hardly depends on the
> > platform you have and the drivers you need.
> > What kind of evaluation board do you have ?
>
> I still cannot decide between the "FlexDevel Starter" evaluation boards
> (with the MPC5567) http://www.tzm.de/Flexray/FlexDevel_Starter.html
> and the Fujitsu SK-91465X-100PMC (with the MB91460)
> http://mcu.emea.fujitsu.com/mcu_tool/detail/SK-91465X-100PMC.htm .
> Well, actually the MB91460 seems to have a fr60 architecture.
> Unfortunatelly, I cannot assess whether a new fr60 architecture port
> would be necessary for the latter.

No, as far as I know the fr60 is absolutely software compatible to fr50 and 
fr30. The instruction set architecture did not change as well as interrupt 
exception handling.

It seems, you are interested in Flexray. It think most of the time porting 
ecos you will spend in developing drivers.

> >> I'm thinking about how long it would take to do a MPC5567 port on my
> >> own, because this MCU is a little more powerful
> >> than the MB91460 ...
> >
> > You have to decide on your own (or ask ecoscentric if they have a
> > commercial port ready to use for you).
>
> Thats a good idea, maybe they have!
>
> > I would be glad to see another fr30 architecture,
> > with powerpc you have an architecture port that is more established and
> > tested...
>
> That is also a reason why I tend to the FlexDevel Starter Board ...

The decision is up to you. I think porting to the MB91460 will be a bit easier 
because of the simpler architecture, but if you have done the MPC5567 you 
will have a bit more fun with it. (I think I would also tend to the MPC...)

Lars

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-02 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 11:56 Vladimir Nikolov
2008-12-02 12:34 ` Lars Poeschel
2008-12-02 14:50   ` Vladimir Nikolov
2008-12-02 16:26     ` Lars Poeschel
2008-12-02 17:29       ` Vladimir Nikolov
2008-12-02 22:30         ` Lars Poeschel [this message]
2008-12-03  8:43 ` Ilija Kocho

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=200812021828.18732.larsi@wh2.tu-dresden.de \
    --to=larsi@wh2.tu-dresden.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=vladimir.nikolov@uni-ulm.de \
    /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).