public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Oleg Uzenkov <o.uzenkov@unicore.co.ua>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] redboot on STM3240G-EVAL board
Date: Thu, 09 Oct 2014 14:08:00 -0000	[thread overview]
Message-ID: <543696C4.2040201@unicore.co.ua> (raw)
In-Reply-To: <alpine.DEB.2.00.1410091628430.5392@sg-laptop>

Thank you very much, Sergei!

the way you described works just fine:

   RedBoot> load -m x
   RedBoot> fis create app
   RedBoot> fis load app
   RedBoot> go

the app gets executed correctly! Huray!

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?

Oleg



> On Thu, 9 Oct 2014, Oleg Uzenkov wrote:
>
>> 4. Build app.elf now for RAM startup.
> First, check that application runs as expected in GDB (reset board)
>
>    <cross>-gdb -q -nx app.elf
>    (gdb) target remote <serial_device>
>    (gdb) load
>    (gdb) continue
>
> If you see the expected output, then try the below as
>
>> 5. Transfer app.elf to redboot via serial xmodem
>> I transfer it to external ram first.
>>
>> RedBoot> load -r -m xmodem -b 0x64010000
> Do not use -r(aw), and -b(ase) switches if you load *ELF* images. If you
> use serial port, load ELFs as
>
>    RedBoot> load -m x
>
>> 6. Create fis entry for the app
>>
>> RedBoot> fis create -b 0x64010000 -f 0x08040000 app
> Again, no need to force base address, if the previous command was
> `load' (load of ELF). Just type
>
>    RedBoot> fis create <name>
>
> Thus, do not use odd switches if you load and save ELFs on FIS, do
>
>    RedBoot> load -m x
>    RedBoot> fis create <name>
>    RedBoot> fis load <name>
>    RedBoot> go
>
> Also I suggest to use standard eCos tests (RAM builds) as the first
> eCos applications, i.e. `make tests' and play with them (load and go).
>
> 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

  reply	other threads:[~2014-10-09 14:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  8:47 [ECOS] redboot on STM32f4-discovery board Oleg Uzenkov
2014-10-03 11:40 ` [ECOS] " John Dallaway
2014-10-04 14:27   ` "Ilija Kocho [Илија Кочо]"
2014-10-05  8:32     ` Oleg Uzenkov
2014-10-05  9:56       ` "Ilija Kocho [Илија Кочо]"
2014-10-09 15:48     ` [ECOS] " Oleg Uzenkov
2014-10-09 18:44       ` [ECOS] " John Dallaway
2014-10-09 21:12       ` [ECOS] " Sergei Gavrikov
2014-10-13 11:59         ` Oleg Uzenkov
2014-10-13 15:10           ` Sergei Gavrikov
2014-10-09 11:33   ` [ECOS] redboot on STM3240G-EVAL board Oleg Uzenkov
2014-10-09 12:36     ` Edgar Grimberg
2014-10-09 13:42       ` Oleg Uzenkov
2014-10-09 13:45     ` Sergei Gavrikov
2014-10-09 14:08       ` Oleg Uzenkov [this message]
2014-10-09 14:35         ` Sergei Gavrikov
2014-10-10  5:52           ` Oleg Uzenkov
2014-10-10  7:55             ` Sergei Gavrikov
2014-10-10  8:52               ` Oleg Uzenkov
2014-10-10 15:58                 ` Sergei Gavrikov
2014-10-15 11:50                   ` Oleg Uzenkov
2014-10-15 14:45                     ` Sergei Gavrikov
2014-10-16  8:08                       ` Oleg Uzenkov
2014-10-16 15:01                         ` Sergei Gavrikov
2014-10-17  9:15                           ` Oleg Uzenkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543696C4.2040201@unicore.co.ua \
    --to=o.uzenkov@unicore.co.ua \
    --cc=ecos-discuss@sourceware.org \
    --cc=sergei.gavrikov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).