From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27666 invoked by alias); 15 Apr 2011 09:56:56 -0000 Received: (qmail 27653 invoked by uid 22791); 15 Apr 2011 09:56:55 -0000 X-SWARE-Spam-Status: No, hits=-1.8 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; Fri, 15 Apr 2011 09:56:49 +0000 Received: from c-3ed8e155.355-1-64736c10.cust.bredbandsbolaget.se ([85.225.216.62]:44747 helo=[192.168.0.196]) by tirion.supremecenter202.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QAflf-0005mX-Ss for ecos-discuss@ecos.sourceware.org; Fri, 15 Apr 2011 09:56:48 +0000 Message-ID: <4DA8165A.7070709@siva.com.mk> Date: Fri, 15 Apr 2011 09:56:00 -0000 From: Ilija Kocho User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8 ThunderBrowse/3.3.5 MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org References: <4D41EB2B.5080504@siva.com.mk> <4D9F6B61.705@siva.com.mk> <4DA49538.60100@siva.com.mk> <4DA5C749.2040706@siva.com.mk> <4DA6D20B.7080908@siva.com.mk> <4DA6F1FA.7050907@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] Kinetis TWR-K60N512-KIT questions X-SW-Source: 2011-04/txt/msg00060.txt.bz2 Hi Drasko Thanks for your encouraging words. On 14.04.2011 17:04, Drasko DRASKOVIC wrote: > On Thu, Apr 14, 2011 at 3:09 PM, Ilija Kocho wrote: >> On 14.04.2011 13:11, Drasko DRASKOVIC wrote: >>> Hi Ilija, >>> for my curiosity, what is the footprint of this port ? >>> >>> If I am not mistaken, K60 have only 128KB of on-chip SRAM. Can it fit ? >> You are not mistaken regarding K60, only for eCos 128KiB RAM is not >> "only", it's "a lot" - "puna kapa". > Wow, > this is great. I have been looking lately at these SoCs and I like > eCos, but so fat I have been running it only on SoCs wit lot of > external RAM. The images I was makeing have been ~1.5MB with my > application. How much of this is for eCos itself? How much is code and how much data? I guess/speculate your experience is with general purpose OSses like Linux. In eCos-like environments, unlike Linux, code is typically executed in FLASH so you need RAM only for data (including stacks, etc). > I am interested in haveing RedBoot, USB stack and TCP/IP stack. It > would be impressive to me if this port can fit this all in K60 ! Can > it ? What can it currently do ? RedBoot is not an environment for running an application. You can use it during development for loading code and debugging, but finally you burn your (eCos) application image in FLASH. Currently available K60 has 512 KiB FLASH + 128 KiB RAM, announced are 1 MiB FLASH. What it can do depends on your application requirements. For example (Note: this may be extreme) on system with 32KiB RAM you can have lwIP TCP/IP and run elementary HTTP server. Code would occupy less than 64 KiB FLASH. Adding USB would add some memory but not much. > Speaking of which, do what would be the crucial advantages for you of > eCos ove Freescales MQX that comes with K60 ? I can't speak for MQX technical merits as I haven't tried it. I can say only what I like at eCos: - Excellent modular structure; - Source code configurabulity: again due to structure but also configtool/ecosconfig; - Unix like I/O, POSIX compatibility - not every RTOS has it; - Well (could be better) documented (particularly kernel and system modules); - Free as freedom. This is like roll-your-own, only you are not alone. (Note: Freescale gives MQX free of charge but you are allowed to use it only on their chips) - Community that helps and (very important for me) allows you to participate (unlikely in proprietary SW world). Speaking of Kinetis we have one apparent disadvantage regarding MQX - we're lagging little-bit. This is the main reason why I decided for early release of our port. Ethernet, SPI, USB are still on our ToDo list, but what you have on Bugzilla has everything you need to start working: HAL - basic system initialization and system clock; HAL - diagnostic serial support - polled; Serial device driver - interrupt driven. > Thanks for your help, for your answers and impressive work ! You are welcome. Regards 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