From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8385 invoked by alias); 14 Jan 2013 21:13:10 -0000 Received: (qmail 8376 invoked by uid 22791); 14 Jan 2013 21:13:09 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED 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; Mon, 14 Jan 2013 21:13:04 +0000 Received: from c-5b1ce155.46-4-64736c11.cust.bredbandsbolaget.se ([85.225.28.91]:39534 helo=[192.168.0.110]) by tirion.supremecenter202.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TurL3-0003db-Im; Mon, 14 Jan 2013 21:13:01 +0000 Message-ID: <50F474DA.1080309@siva.com.mk> Date: Mon, 14 Jan 2013 21:13:00 -0000 From: Ilija Kocho User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Lukas Riezler CC: ecos discuss References: <20130111005517.19900@gmx.net> <50EFC56F.4040506@siva.com.mk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] RedBoot necessary for porting ecos? X-SW-Source: 2013-01/txt/msg00019.txt.bz2 Lukas On 13.01.2013 18:21, Lukas Riezler wrote: > Hi Michael & Ilja! > > Thank you very much for your answers! > > So, if I'm right now, I need to port ecos before RedBoot is able to > run...and I don't really need RedBoot for my intention. (?) > Is there any suggestion which existing ecos-port for Cortex-M I should > take to be my template? Instead of suggesting I'll try to list specifics of existing ports, I hope it will help you pick one that's closest to your system. - STM32 is the initial Cortex-M port and probably was used as model for others, contains wide span of memory configurations and probably most complete driver set, including USB but lacks Ethernet (which you can finf in Bugzilla), You already noticed STM32 support for external interrupts. - LM3S is nice example for a tiny system with very little memory. - Kinetis, A2FXXX and LPC17XX have Ethernet. - LPC 17xx is example for reusing drivers from other architecture (ARM and Cortex-M are considered separate architectures in eCos) - Kinetis and A2FXXX feature Consolidated Interrupt Priority Scheme, - Kinetis features wide range of memory models including single chip and systems with external memory. Single-chip memory models are generically supported on variant level. > > Porting eCos to Cortex-M is relatively straight-forward (compared to > > other architectures) because some essential components are > > implemented/defined on architectural level: interrupt controller, > > systick, and general memory map. > > If I take a look in the existing port for stm32, there is a also > interrupt handling header-file in the variant-layer. But these are > onley special interrupts for the peripherals - did I understand right? Yes. > Sorry for my "simple" questions - but I need to get basic knowledge > and a solid overview :-) > > I take it that you have read eCos docs. Additional information regarding porting you shall find in Massa's book. http://www.informit.com/content/images/0130354732/downloads/0130354732.pdf HTH Ilija -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss