From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29965 invoked by alias); 11 Jan 2013 07:55:37 -0000 Received: (qmail 29955 invoked by uid 22791); 11 Jan 2013 07:55:35 -0000 X-SWARE-Spam-Status: No, hits=-2.5 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; Fri, 11 Jan 2013 07:55:31 +0000 Received: from [195.189.206.101] (port=33671 helo=[192.168.209.11]) by tirion.supremecenter202.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1TtZSb-0003EK-H0; Fri, 11 Jan 2013 07:55:29 +0000 Message-ID: <50EFC56F.4040506@siva.com.mk> Date: Fri, 11 Jan 2013 07:55:00 -0000 From: Ilija Kocho User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Lukas Riezler CC: ecos-discuss@sourceware.org References: <20130111005517.19900@gmx.net> In-Reply-To: <20130111005517.19900@gmx.net> Content-Type: text/plain; charset=UTF-8 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/msg00014.txt.bz2 Hello Lukas Actually RedBoot works on top of eCos so before eCos is ported you can't run RedBoot. 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. In most cases, all you need to make in order get first eCos "Hello World!" on serial line are: 1. Clocking 2. Diagnostic (HAL) serial support. Once you have reached this point, you can start with device drivers (serial, Ethernet, etc). Regarding peripheral drivers: Before you start coding, do some research through eCos source tree, it is possible that your chip has some peripherals that are already supported for other architectures, then you can probably use the same drivers (with or without some tweaks). Usually the manufacturers combine same peripherals with different architectures. For instance LPC17xx uses drivers from LPC2xxx. Have fun! Ilija On 11.01.2013 01:55, Lukas Riezler wrote: > Hello everyone! > > First I have to say, that I'm quite new in microcontroller theme (and my english is not so good). > But I'm interested to get ecos run on my IAR-EvalBoard with CortexM3 (FM3). > I've read a lot of stuff but though I have some elementary questions: > > - is it a requirement to work with RedBoot or is it also possible to port ecos without using RedBoot? > - I know that RedBoot is based on the ecos-HAL. Does it mean, if I port RedBoot to my target, that I can use later the same HAL-Code for ecos? > > With kind regards, > Lukas R. > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss