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: Wed, 15 Oct 2014 14:50:32 +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> <5437742F dot 7020908 at unicore dot co dot ua> <alpine dot DEB dot 2 dot 00 dot 1410100906150 dot 1839 at sg-pc dot belvok dot com> <54379E39 dot 4070804 at unicore dot co dot ua> <alpine dot DEB dot 2 dot 00 dot 1410101654110 dot 7877 at sg-laptop>
Hi Everyone,
For binaries you have to know the first LMA address (rom_vectors
address) to specify that address on a command line.
For binary image
load -m x -r -b <LMA>
fis create -b <LMA> <name>
Please, let me know what do you think of this:
1) I have built app.elf and app.bin for *RAM* startup
(SECTION_rom_vectors: LMA == 0x64008000 )
(memory layout is mlt_cortexm_stm32x0g_eval_ram.ldi)
2) I can successfuly run app.elf under redboot (i.e. >load -m x; >go)
3) When I load app.bin like this:
>load -m x -r -b 0x64008000
>go 0x64008000
or
>go
I get rubbish ($T080f:00800064;0d:e8cf1b64;)
(i also tried to create fis and load and run image from fis, same
result, i.e. >fis create -b 0x64008000 app; >fis load app; >go)
any ideas where I am wrong?
Did anyone manage to execute .bin file from Redboot?
Thanks.
Oleg
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss