public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] small custom bootloader to start an app stored in flash
Date: Tue, 21 Oct 2014 11:02:00 -0000	[thread overview]
Message-ID: <54463D4B.9090000@mlbassoc.com> (raw)
In-Reply-To: <544618E5.90101@unicore.co.ua>

On 2014-10-21 02:27, Oleg Uzenkov wrote:
> Hello Everyone,
>
> I would like to make a small custom bootloader (not considering RedBoot) that would implement a simple function of checking a flag (some bytes in memory) and then jumping to one of
> the applications stored in internal flash.
>
> Something like this:
>
> internal flash memory:
>
> ------------------  0x08000000
> | bootloader  |
> |                    |
> ------------------
> |_____            |
> |flag |            |
> ------------------
> |                    |
> |                    |
> ------------------
> | app1           |
> |                    |
> ------------------
> | app2           |
> |                    |
> ------------------
> |                    |
> |                    |
> --------------
>
> Basically, if flag is true then start app1 else start app2.
>
> I suppose bootloader would be a simple eCos app with ROM startup. Applications in flash probably should also be built for ROM startup.
> When the jump is made app's .data and .bss sections should be copied into RAM...
>
> Any ideas how to make a jump to start an app? May be some sample code showing how to do it in eCos? May be someone has done it already?
>
> I would appreciate any help on this.

You've already mentioned the answer - RedBoot!

RedBoot is just another eCos application which does all the
things you are considering.  I can understand not wanting to
include RedBoot in your design (although it can be extremely
useful, especially during development), but looking through
the sources you'll find guidance on all the topics you are
looking for.

Good luck

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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-21 11:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  8:27 Oleg Uzenkov
2014-10-21 11:02 ` Gary Thomas [this message]
2014-10-21 13:25 ` Edgar Grimberg
     [not found] ` <CAPrjMDAi=cqTSQ-d-c9FF53W-c6=v0j8rzSLQfuTcBQUY43Zpw@mail.gmail.com>
2014-10-22 11:08   ` Oleg Uzenkov
2014-10-22 13:17     ` Edgar Grimberg
2014-10-22 14:40       ` Oleg Uzenkov
2014-10-23  9:55         ` Edgar Grimberg
2014-10-23 12:53           ` Edgar Grimberg
2014-10-23 15:03             ` Oleg Uzenkov
2014-10-23 19:25               ` Rainer Arndt
2014-10-23 21:21               ` Sergei Gavrikov
2014-10-24  7:44                 ` Oleg Uzenkov
2014-10-24  8:36                   ` Sergei Gavrikov
2014-10-24  9:13                     ` Oleg Uzenkov
2014-10-24  9:13                     ` Sergei Gavrikov
2014-10-22 19:01     ` Rainer Arndt
2014-10-23 11:50       ` 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=54463D4B.9090000@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).