From: Christian Jaeger <christian@jaeger.mine.nu>
To: Rob Duncan <rob.duncan@designmagnitude.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] eCos on STR9 ?
Date: Tue, 12 Aug 2008 15:15:00 -0000 [thread overview]
Message-ID: <48A1A8ED.30303@jaeger.mine.nu> (raw)
In-Reply-To: <be72a610808120802g12c9fe68p3974572f8eed08d3@mail.gmail.com>
Rob Duncan wrote:
> I did a port of eCos to the STR912FW a year or so ago. It took me
> about two weeks to get a basic system working. It was my first port,
> and I cut a few corners along the way, but it ended up working well.
> I didn't have a JTAG debugger so I was reduced to bringing up the
> startup code and serial console by using a combination of LEDs, coffee
> and late nights. I'm no longer involved with the company so I don't
> know the current status of the port, but I don't believe the source is
> available.
Thanks for giving notice.
I do have a working JTAG adapter (with openocd). So it *might* be
simpler, although I don't know yet all the details of the memory layout
(nor how to define it for the compilation of the program), and of course
I don't know how the eCos startup sequence works etc.
I'm currently trying to get FreeRTOS running (which isn't exactly as
easy as advertised either if you don't have Windows and the IAR tools
since the Demo is assuming those), I'll take whichever route gives me
light at the end of the tunnel first. It seems I have to delve into the
thumb vs. 32bit code transition/linking business and linking etc stuff
anyway by myself.
Christian.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-08-12 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 11:36 Christian Jaeger
2008-08-12 12:19 ` Andrew Lunn
2008-08-12 15:03 ` Rob Duncan
2008-08-12 15:15 ` Christian Jaeger [this message]
2009-06-16 16:38 ` jerzy dyrda
2009-06-17 5:13 ` Andrew Lunn
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=48A1A8ED.30303@jaeger.mine.nu \
--to=christian@jaeger.mine.nu \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rob.duncan@designmagnitude.com \
/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).