This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: redboot on STM3240G-EVAL board
- From: Oleg Uzenkov <o dot uzenkov at unicore dot co dot ua>
- To: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- Cc: eCos Discussion <ecos-discuss at sourceware dot org>
- Date: Fri, 10 Oct 2014 08:52:47 +0300
- Subject: Re: redboot on STM3240G-EVAL 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> <5436726C dot 8000703 at unicore dot co dot ua> <alpine dot DEB dot 2 dot 00 dot 1410091628430 dot 5392 at sg-laptop> <543696C4 dot 2040201 at unicore dot co dot ua> <alpine dot DEB dot 2 dot 00 dot 1410091716530 dot 5580 at sg-laptop>
ELF files are quite large, what is the preferred format for an image
to be passed to redboot? what "load" and "fis create" command look
like?
**Roughly** speaking, you save .text segment in FLASH (adjusted to flash
block erase size), you save not ELF image! So, do not mess with
binaries. Also `load' command does not carry whole ELF image into RAM,
but .text segment with a few other segments.
The thing is:
I will need to work with files (new firmware should arrive to sdcard on
the board through ftp in a main app). I want redboot to pick a new image
up from sdcard at reset.
Extracting sections from received ELF file and transferring them to
redboot is more of a manual work.
So, I think I am kind of stuck with ELF files.
So I am thinking:
* Should I load compressed ELF file (gzip) with -d switch?
* Should I load SREC file (they are usually smaller than ELF)?
* Should I save executable sections and store them in a file. Transfer
that file to sdcard for redboot to pick it up at reset.
(nor sure how to do it actually)
* Can I actually load a .bin (image in binary format)?
Thanks.
Oleg
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