From: "\"Ilija Kocho [Илија Кочо]\"" <ilijak@siva.com.mk>
To: Oleg Uzenkov <o.uzenkov@unicore.co.ua>
Cc: John Dallaway <john@dallaway.org.uk>,
eCos Discussion <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] Re: redboot on STM32f4-discovery board
Date: Sat, 04 Oct 2014 14:27:00 -0000 [thread overview]
Message-ID: <543003B9.20300@siva.com.mk> (raw)
In-Reply-To: <542E8B41.8030905@dallaway.org.uk>
On 03.10.2014 13:40, John Dallaway wrote:
> Hi Oleg
>
> On 02/10/14 09:47, Oleg Uzenkov wrote:
>
>> I am working with eCos on STM32f4-discovery board.
>>
>> I would like to build a redboot loader that could choose and load
>> binaries (eCos+app) stored in internal flash at power on.
>>
>> The eCos port for STM32f4-discovery has got a redboot option under
>> Packages list in Templates. However it seems to be very minimalistic and
>> also not functional. Also there is no specific configuration file like
>> redboot_ROM.ecm.
>>
>> Please, could you give me directions as to making a functional redboot
>> loader for STM32f4-discovery board.
>>
>> Would it make sense to build redboot for stm32x0g_eval board (redboot
>> seems to be working) and adapt it for STM32f4-discovery board?
>>
>> I would appreciate any input on this.
> To be clear, there is no support for RedBoot in the STM32F4-Discovery
> platform HAL at present. The STM32F4-Discovery board offers only 128KiB
> of contiguous on-chip RAM, so loading applications into RAM prior to
> execution would limit the size of your applications quite considerably.
> RedBoot would also consume some of the available RAM for its own data
> structures.
>
> If you are still interested in using RedBoot to load and launch your
> applications, you will need to add the following to the
> STM32F4-Discovery platform HAL package:
>
> a) CDL items and memory layout files for RAM startup
> b) CDL items for behaving as a ROM monitor and for working with a ROM
> monitor
> c) RedBoot-specific CDL items and data structures
>
> You will find examples of all the above in the STM32x0G_EVAL platform
> HAL package, but keep in mind that the STM32x0G_EVAL boards feature
> external RAM. The naming of memory regions and startup types is
> therefore different. The STM32x0G_EVAL "ROMINT" and "SRAM" startup types
> are broadly equivalent to the STM32F4-Discovery "ROM" and (proposed)
> "RAM" startup types respectively.
In addition, for example of RedBoot on a platform with only internal RAM
you can look at Kinetis.
Ilija
>
> I hope this helps...
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
>
--
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-04 14:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 8:47 [ECOS] " Oleg Uzenkov
2014-10-03 11:40 ` [ECOS] " John Dallaway
2014-10-04 14:27 ` "Ilija Kocho [Илија Кочо]" [this message]
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
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
2014-10-10 17:22 [ECOS] Re: redboot on STM32f4-discovery board 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=543003B9.20300@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@sourceware.org \
--cc=john@dallaway.org.uk \
--cc=o.uzenkov@unicore.co.ua \
/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).