From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19952 invoked by alias); 15 Dec 2011 18:04:32 -0000 Received: (qmail 19938 invoked by uid 22791); 15 Dec 2011 18:04:31 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from tirion.supremecenter202.com (HELO tirion.supremecenter202.com) (209.25.195.243) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Dec 2011 18:04:18 +0000 Received: from c-98d9e155.355-1-64736c10.cust.bredbandsbolaget.se ([85.225.217.152]:53170 helo=[192.168.0.115]) by tirion.supremecenter202.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1RbFfE-0004Ga-G9; Thu, 15 Dec 2011 18:04:16 +0000 Message-ID: <4EEA3697.4090109@siva.com.mk> Date: Thu, 15 Dec 2011 18:04:00 -0000 From: Ilija Kocho User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110628 Thunderbird/5.0 MIME-Version: 1.0 To: Tomas Frydrych CC: ecos-devel@ecos.sourceware.org Subject: Re: Adding Kinetis boards References: <4EEA26E3.60707@r-finger.com> In-Reply-To: <4EEA26E3.60707@r-finger.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2011-12/txt/msg00006.txt.bz2 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. Ilija 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 > >