From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2949 invoked by alias); 15 Jun 2006 14:55:03 -0000 Received: (qmail 2940 invoked by uid 22791); 15 Jun 2006 14:55:02 -0000 X-Spam-Status: No, hits=-0.4 required=5.0 tests=AWL,BAYES_40,FORGED_RCVD_HELO X-Spam-Check-By: sourceware.org Received: from mail.ilxlightwave.com.167.166.216.in-addr.arpa (HELO mail.corp.ilxlightwave.com) (216.166.167.70) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 15 Jun 2006 14:54:59 +0000 Received: from alamb [10.10.0.99] by mail.corp.ilxlightwave.com with ESMTP (SMTPD32-8.13) id A4C133BF0074; Thu, 15 Jun 2006 08:54:57 -0600 From: "C. Adam Lamb" To: Subject: RE: Intention to Port eCos to STR9 Date: Thu, 15 Jun 2006 14:55:00 -0000 Message-ID: <015001c6908b$ab608080$63000a0a@corp.ilxlightwave.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: AcaQWVwzYW02Faj6SvSHMdNEMuhwBQAL+byQ In-Reply-To: <4491204D.4000103@siva.com.mk> X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2006-06/txt/msg00022.txt.bz2 Thanks for all the input! I'll summarize a few things (and correct me if I'm wrong or miss anything): 1) I should really try to make my port as generic as possible so things that apply to all STR parts will be in one file with the parts that appear to be specific to the STR912 will be in another file. I'm not exactly sure at this point how this will look (I need to start looking at some HAL code) since the STR912 doesn't have an MMU and most of the others do... 2) PEEDI appears to be a good tool with good support. I was leaning towards the JTAG Jet tool from Signum because of the trace capability (I now have the OK to buy that one, so I should be able to purchase whatever I want now)... Does anyone see any reasons not to get the Signum tool? Maybe I should just stick with PEEDI since it is proven out and they know what eCos is? 3) Look into re-using drivers from other ports. 4) The closest port to start from will be the ARM Integrator Platform that uses the ARM966E-S core since the core is the same as the STR9. Again, their might be drivers from other ports that I can pull in, but the starting point will probably be the ARM966E-S port. New Question: I have heard a few people talk about not using Redboot, and instead just using their JTAG tools to do the loading, flashing, debugging, etc. I assume that since I will have a JTAG tool I wouldn't necessarily need to use Redboot, but I am guessing it still might make life easier for a couple of reasons. First, it will be an easier way to prove out that my HAL is correct with the simpler set of code. Second, the community will like me slightly more if I do the work to provide a more complete port for the STR9... Thanks! Adam