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] small custom bootloader to start an app stored in flash
Date: Fri, 24 Oct 2014 09:13:00 -0000 [thread overview]
Message-ID: <544A183B.6090206@unicore.co.ua> (raw)
In-Reply-To: <alpine.DEB.2.00.1410241058110.4666@sg-pc.belvok.com>
Thanks,
I will give it a try with ROM builds.
> On Fri, 24 Oct 2014, Oleg Uzenkov wrote:
>
>> Redboot is a great piece of software. It is just I found that when you
>> enable some important features like FIS support, Redboot reserves
>> extra space in RAM memory.
>> The size of this reserved extra space in RAM equals to the size of the
>> largest section size in Flash. In case of stm32f407 it is 128KB.
>> Internal RAM is 128KB. As John Dallaway pointed out there is very
>> little sense in using Redboot without enough of external RAM on
>> stm32f4 devices. For example for Kinetis it is a different story, the
>> flash sections are uniform and quite small.
>>
>> For small systems external RAM chip significantly adds up to the cost
>> of a device.
>
> I understand John's point and agree with him. But, he told about using
> debug infrastructure of RedBoot (debugging eCos applications in RAM).
> But, RedBoot is *debug* and *bootstrap* environment for eCos. I pointed
> on another side of RedBoot, *bootstrap*. You can quite run eCos [ROM]
> builds from FIS.
FIS support requires 128KB of ram on stm32.
> Those [ROM] applications may utilize all RAM (128K +
> 64K) on your target. On start ROM application just does overlay RedBoot
> memory. You saw that yesterday with Rainer's approach (exec). If you
> cannot manage run [ROM] applications with RedBoot command 'go', just
> implement one new command for RedBoot, e.g. 'xip' (as RedBoot already
> uses 'exec' name to run Linux kernel).
As far as I understand, 'go' command should work in theory as it sets
program counter (pc) to the address of Entry point (not sure about stack
pointer).
To make a jump we need to set stack pointer and program counter. And
this can be implemented inside a new 'xip' command.
> RedBoot will let you to use
> FLASH I/O, load any images, use start scripts, etc., etc. Of course it
> is my opinion only.
>
> 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
next prev parent reply other threads:[~2014-10-24 9:13 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
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 [this message]
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=544A183B.6090206@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).