This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: redboot on STM32f4-discovery board
- From: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- To: Oleg Uzenkov <o dot uzenkov at unicore dot co dot ua>
- Cc: eCos Discussion <ecos-discuss at sourceware dot org>
- Date: Fri, 10 Oct 2014 00:12:19 +0300 (FET)
- Subject: Re: redboot on STM32f4-discovery board
- Authentication-results: sourceware.org; auth=none
- References: <542D110B dot 9080002 at unicore dot co dot ua> <542E8B41 dot 8030905 at dallaway dot org dot uk> <543003B9 dot 20300 at siva dot com dot mk> <5436AE5C dot 6060401 at unicore dot co dot ua>
On Thu, 9 Oct 2014, Oleg Uzenkov wrote:
> But, without Flash Image System I do not see how to use redboot to
> load and store and run images.
Even for builds (CYGOPT_REDBOOT_FIS == 0) you can manage FLASH using
absolute FLASH addresses and FIS sub-commands: erase and write.
When you make RedBoot work smoothly on your target, then you can try to
load images directly to FLASH if you enable
cdl_option CYGBLD_REDBOOT_LOAD_INTO_FLASH {
user_value 1
};
eCos is designed with XIP (eXecute In Place) in mind and you can use
RedBoot 'go' command to execute ROM image from specified place of FLASH.
For simple applications it would be enough just to shift *rom* ORIGIN
address and *rom_vectors* address in `target.ld' file and re-link ROM
application, then with the option above it is possible to load and run
such ROM image as
load -m <protocol>
go
I call that it worked on my target (load-into-flash-and-go). However,
you need to inspect and may be fix HAL startup files for such "FLASH"
builds.
Sergei
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss