public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: Lukas Riezler <lukas.riezler@gmx.net>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Starting port for Fujitsu-FM3
Date: Wed, 13 Mar 2013 18:31:00 -0000	[thread overview]
Message-ID: <5140C5DF.6040404@siva.com.mk> (raw)
In-Reply-To: <trinity-fb6cd4f8-06e9-42dd-b9ed-4ae12d3e83ba-1363185114778@3capp-gmx-bs07>

On 13.03.2013 15:31, Lukas Riezler wrote:
> Hi all,
>
> after reading a lot of stuff about ecos
> and studying the existing HAL of Cortex-M (architecture) --> stm32 (variant) --> stm3210e_Evalboard (platform),
> now the time has come to start porting ecos to a Fujitsu-FM3 (variant) --> MB9B506R (platform).

Have you checked what for device drivers? Some drivers may be ready on
some other architecture. Pay a visit to other Fujitsu ports. If you find
drivers for your device, do not copy. Let targets and architecture share
device drivers, that's the one of the main reasons why devices are
decoupled from HAL. LPC17xx, for example uses drivers from LPC2xxx.


>
> I use Eclipse-CDT with gcc (which comes with ecos) and JLINK-GDB-Server from Segger for debugging.

You could make use of eCos Gnu Tools 4.6.3 test release, ref:
http://ecos.sourceware.org/ml/ecos-discuss/2012-06/msg00047.html

>
> Do you have any additional tips which I should know before I'll start my intention?

Have fun

Ilija


-- 
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:[~2013-03-13 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 14:32 Lukas Riezler
2013-03-13 18:31 ` Ilija Kocho [this message]

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=5140C5DF.6040404@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@sourceware.org \
    --cc=lukas.riezler@gmx.net \
    /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).