From: Andrew Lunn <andrew@lunn.ch>
To: "C. Adam Lamb" <alamb@ilxlightwave.com>
Cc: ecos-devel@sourceware.org
Subject: Re: Intention to Port eCos to STR9
Date: Wed, 14 Jun 2006 21:09:00 -0000 [thread overview]
Message-ID: <20060614210942.GA15848@lunn.ch> (raw)
In-Reply-To: <00c001c68fef$94598bd0$63000a0a@corp.ilxlightwave.com>
On Wed, Jun 14, 2006 at 02:17:37PM -0600, C. Adam Lamb wrote:
> Hi Gang,
>
> I?m currently looking into porting eCos to the STR912 processor.? The
> processor is on the bleeding edge (it just came out), so I?m still waiting
> for my eval board.
>
> My first goal in this message is to both let everyone know that I should be
> starting to work on this soon and see if anyone else might be working on
> this as well?
>
> Second goal is to have someone with some eCos experience make sure my
> porting approach isn?t too far off.?
O.K. First tip. Try not to have tunnel vision on the STR912. Try
taking a look at all the STR7 and STR9 devices. Work out what is
common and what is different. Try to make your port as generic as
possible. So if for example the UART is the same for all devices, just
write a STR UART driver, not a STR912 UART driver. Same goes for SPI,
FLASH controller, etc. If a peripheral for the STR9xx is different
from the STR7xx write an STR9xx driver. And lastly, if the STR912 has
something unque, write an STR912 unique driver. Same goes for the
HAL. Try to split it up into a varient HAL for STR9xx and a specific
HAL STR912. Maybe it is even possible to have a three layer HAL, with
STR at the top. The different between the STR7 and STR9 will be the
MMU setup. So maybe it is possible to put the MMU code into the STR9xx
HAL package and have most of the code in the STR HAL package.
The advantage of doing it like this is it makes it easier for others
to do ports to other members of the STR family building on what you
have done. I made a mistake here with the AT91SAM family. I did a port
to the AT91SAM7S and later found out that the AT91SAM7X is 99% the
same. I then ended up with a naming mess since the AT91SAM7S package
now also supports the AT91SAM7X devices. And i guess sometime in the
future the AT91SAM9 is going to be supported by the AT91SAM7S
package. Ugly.
> I will be using the all of the GNU tools for building and debugging.?
That is normal. Using anything else for compiling is virtually
impossible. You do have more flexibility with debugging, but i still
recommend gdb. You can add a GUI on top if you like, eg Insight, DDD,
etc.
> I intend to purchase either Signum System?s JTAG Jet with Trace or the PEEDI
> JTAG Emulator if I can?t get my company to pony up for the slightly more
> expensive device from Signum.? Both of those devices claim to be compatible
> with the GNU debuggers.? Anyone with experience with either of those
> devices??
I've had good experiance with PEEDI with the AT91SAM7S development
board. You need an up to date version of gdb. The version on the eCos
website as part of the ARM toolchain is too old for breakpoints to
work properly.
Andrew
next prev parent reply other threads:[~2006-06-14 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 20:17 C. Adam Lamb
2006-06-14 21:09 ` Andrew Lunn [this message]
2006-06-14 21:15 ` Re[2]: " Evgeny Belyanco
2006-06-14 21:33 ` Andrew Lunn
2006-06-15 8:54 ` Ilija Koco
2006-06-15 14:55 ` C. Adam Lamb
2006-06-15 15:12 ` Andrew Lunn
2006-06-15 21:56 ` Joakim Langlet
2006-06-15 22:11 ` C. Adam Lamb
2006-08-28 10:29 ` fabio
2008-07-28 6:48 ` Mohd_Arif
2006-06-16 9:44 ` Ilija Koco
2006-06-16 14:47 ` Porting " C. Adam Lamb
2006-06-17 9:47 ` Ilija Koco
2006-06-17 9:59 ` Ilija Koco
2006-08-27 15:51 ` Intention to Port " Evgeny Belyanco
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=20060614210942.GA15848@lunn.ch \
--to=andrew@lunn.ch \
--cc=alamb@ilxlightwave.com \
--cc=ecos-devel@sourceware.org \
/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).