public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Chris Holgate <chris@zynaptic.com>
To: Stanislav Meduna <stano@meduna.org>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] How to write a complicated bootloader?
Date: Sat, 11 Jul 2009 15:02:00 -0000	[thread overview]
Message-ID: <4A58A988.8090405@zynaptic.com> (raw)
In-Reply-To: <4A58816D.1030703@meduna.org>

Stanislav Meduna wrote:
> Andrew Lunn wrote:
> 
>> If your flash is big enough, which it probably is if you
>> are using jffs2, it might make sense to have two eCos
>> applications, plus redboot.
> 
> Okay, that's what I also thought of as one of the possibilities.

An alternative which I'm using for my current project is to make the
bootloader as dumb as possible - just capable of verifying a new
firmware image in a local SPI flash and then copying it over to the main
flash area when requested.  That way the new firmware can be transferred
to the device under control of the application (using the fully featured
driver).  My particular SPI bootloader is coded 'on the metal' for the
STM32, but I'm sure it wouldn't be too hard to get Redboot to provide
the same functionality.

Chris.

-- 
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:[~2009-07-11 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  9:18 Stanislav Meduna
2009-07-11  9:36 ` Andrew Lunn
2009-07-11 11:33 ` Gary Thomas
2009-07-11 12:11   ` Stanislav Meduna
2009-07-11 15:02     ` Chris Holgate [this message]

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=4A58A988.8090405@zynaptic.com \
    --to=chris@zynaptic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=stano@meduna.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).