This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: redboot on STM3240G-EVAL 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: Wed, 15 Oct 2014 17:45:05 +0300 (FET)
- 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> <543E5F88 dot 2050002 at unicore dot co dot ua>
On Wed, 15 Oct 2014, Oleg Uzenkov wrote:
> > 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
RedBoot 'load' command does stat info about 'Entry point'. For example
on my ARM target
RedBoot> load -m y
Entry point: 0x81008040, address range: 0x81008000-0x81013890
xyzModem - CRC mode, 627(SOH)/0(STX)/0(CAN) packets, 2 retries
RedBoot>
Load address 0x81008000 and entry point (LMA of .text) is 0x81008040.
If I load a binary, I got something likes this
RedBoot> load -m y -r -b 0x81008000
CRaw file loaded 0x81008000-0x8101388f, assumed entry at 0x81008000
xyzModem - CRC mode, 372(SOH)/0(STX)/0(CAN) packets, 3 retries
RedBoot>
RedBoot has no clue where start from (it can guess only, 'assumed
entry')
>From your old message
http://ecos.sourceware.org/ml/ecos-discuss/2014-10/msg00007.html
I see that after loading PC register will be set to 0x64008110, so try
RedBoot> go 0x64008110
> I get rubbish ($T080f:00800064;0d:e8cf1b64;)
Connect GDB to get it.
> (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?
See/try above.
>
> Did anyone manage to execute .bin file from Redboot?
It should work.
HTH
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