From: Ilija Kocho <ilijak@siva.com.mk>
To: Lukas Riezler <lukas.riezler@gmx.net>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Porting ecos and Eclipse
Date: Thu, 14 Feb 2013 20:12:00 -0000 [thread overview]
Message-ID: <511D452D.2080905@siva.com.mk> (raw)
In-Reply-To: <20130214173037.244090@gmx.net>
Hi Lukas
On 14.02.2013 18:30, Lukas Riezler wrote:
> Hi ecos-guys!
>
> I still try to get ecos work on my fm3-evalboard (cortex-m3). Fortunately I have a J-Tag / J-Link!
> My intention is now to work with Eclipse IDE by using the J-Link.
> For that reason I attended the Yagarto-toolchain - but I replaced the Yagarto-gcc with the gcc of the ecos-toolchain (as a precaution because of my later undertaking).
> ==> I work with gcc from ecos-toolchain and gdb from Yagarto. I'm able to debug a small example-project successfully :-)
>
> My next idea was to take parts of the ecos-HAL in a eclipse-project and tinkering till i have ported the HAL to my new target.
> Do you think this way could cause to a good end for my porting-process?
> I already started to implement my idea but there are a lot of dependencies between all the used files - so I have to add more and more files.
> So I decided to stop and ask you before I continue and perhaps become desperate ;-)
>
> Could it work like this?
Well, it worked for me. True, I use MicroEmacs (Jasspa edition) but
Eclipse shouldn't be a handicap with its makefile project support.
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
prev parent reply other threads:[~2013-02-14 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:30 Lukas Riezler
2013-02-14 20:12 ` 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=511D452D.2080905@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@ecos.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).