public inbox for
 help / color / mirror / Atom feed
From: Ilija Kocho <>
To: Tomas Frydrych <>
Subject: Re: Adding Kinetis boards
Date: Thu, 15 Dec 2011 18:04:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Tomas

It may be just enough to add a new target entry in ecos.db.
I am not familiar with Kwikstik I only know that it is based on same
chip as TWR-K40. Can you please point the differences between boards
with respect to: HAL, devices, etc.


On 15.12.2011 17:57, Tomas Frydrych wrote:
> Hi,
> I am looking at adding the Kwikstik to the current Kinetis boards, and I
> am wondering what would be the best way to approach this.
> Currently there are two Kinetis boards, the TWR-K40X256 and TWR-K60N512,
> with the directory structure something like this:
> kinetis/var/...     - Generic Kinetis code
> kinetis/twr_k40x256 - K40 and twr-k40 code
> kinetis/twr_k60x256 - K60 and twr-k60 code
> Kwikstik is based on the same MCU as the twr-k40x256, so it needs the
> same MCU-specific code as the twr-k40x256 board, which I think is all,
> or nearly all of the code currently under the twr_k40x256 directory.
> I initially thought I'd just clone twr_k40x256 into a new kwikstik
> directory, but that's probably not the best approach for
> maintainability. I am thinking it might be better to split out the
> generic K40 code so it can be shared between distinct boards, but I am
> not sure where to split this to: should there be a separate k40x256
> subdirectory and a corresponding package that the twr_k40x256 requires?
> Or is there a better way of approaching this altogether?
> Many thanks in advance,
> Tomas

  reply	other threads:[~2011-12-15 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 16:57 Tomas Frydrych
2011-12-15 18:04 ` Ilija Kocho [this message]
2011-12-15 19:55   ` Tomas Frydrych
2011-12-16  8:39     ` Ilija Kocho
2011-12-19 21:33       ` Tomas Frydrych

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).