From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 599 invoked by alias); 3 Oct 2014 11:40:56 -0000 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 Received: (qmail 548 invoked by uid 89); 3 Oct 2014 11:40:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: tetra.codeconfidence.com Received: from tetra.codeconfidence.com (HELO tetra.codeconfidence.com) (94.229.66.225) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 03 Oct 2014 11:40:53 +0000 Received: from cog.dallaway.org.uk (cpc1-cmbg1-0-0-cust759.5-4.cable.virginm.net [82.21.98.248]) by tetra.codeconfidence.com (Postfix) with ESMTP id CE779234C02E; Fri, 3 Oct 2014 12:40:50 +0100 (BST) Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id s93BenXv013239; Fri, 3 Oct 2014 12:40:50 +0100 Message-ID: <542E8B41.8030905@dallaway.org.uk> Date: Fri, 03 Oct 2014 11:40:00 -0000 From: John Dallaway User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.8.0 MIME-Version: 1.0 To: Oleg Uzenkov CC: eCos Discussion References: <542D110B.9080002@unicore.co.ua> In-Reply-To: <542D110B.9080002@unicore.co.ua> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [ECOS] Re: redboot on STM32f4-discovery board X-SW-Source: 2014-10/txt/msg00001.txt.bz2 Hi Oleg On 02/10/14 09:47, Oleg Uzenkov wrote: > I am working with eCos on STM32f4-discovery board. > > I would like to build a redboot loader that could choose and load > binaries (eCos+app) stored in internal flash at power on. > > The eCos port for STM32f4-discovery has got a redboot option under > Packages list in Templates. However it seems to be very minimalistic and > also not functional. Also there is no specific configuration file like > redboot_ROM.ecm. > > Please, could you give me directions as to making a functional redboot > loader for STM32f4-discovery board. > > Would it make sense to build redboot for stm32x0g_eval board (redboot > seems to be working) and adapt it for STM32f4-discovery board? > > I would appreciate any input on this. To be clear, there is no support for RedBoot in the STM32F4-Discovery platform HAL at present. The STM32F4-Discovery board offers only 128KiB of contiguous on-chip RAM, so loading applications into RAM prior to execution would limit the size of your applications quite considerably. RedBoot would also consume some of the available RAM for its own data structures. If you are still interested in using RedBoot to load and launch your applications, you will need to add the following to the STM32F4-Discovery platform HAL package: a) CDL items and memory layout files for RAM startup b) CDL items for behaving as a ROM monitor and for working with a ROM monitor c) RedBoot-specific CDL items and data structures You will find examples of all the above in the STM32x0G_EVAL platform HAL package, but keep in mind that the STM32x0G_EVAL boards feature external RAM. The naming of memory regions and startup types is therefore different. The STM32x0G_EVAL "ROMINT" and "SRAM" startup types are broadly equivalent to the STM32F4-Discovery "ROM" and (proposed) "RAM" startup types respectively. I hope this helps... John Dallaway eCos maintainer http://www.dallaway.org.uk/john -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss