From: Antony Pavlov <antonynpavlov@gmail.com>
To: Kai Che <Kai.Che@mixed-mode.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Barebox support for Arm Cortex-M0 Boards
Date: Tue, 12 Feb 2019 17:50:45 +0300 [thread overview]
Message-ID: <20190212175045.d8af82f1a3fdc47c21957d72@gmail.com> (raw)
In-Reply-To: <1549976247670.75244@mixed-mode.de>
On Tue, 12 Feb 2019 12:57:26 +0000
Kai Che <Kai.Che@mixed-mode.de> wrote:
Hi!
> does barebox support any kind of Arm-Cortex M0 Boards? e.g. STM32F0 or similiar?
At the moment barebox does not support ARM-Cortex.
I suppose there is no problem to port barebox to STM32.
However STM32F0 definitely is not a preferred STM32 target chip for porting.
Barebox is intended to be a BOOTLOADER. Barebox is intended to load something into RAM.
STM32F098VC is an advanced STMF0 family chip in terms of RAM and ROM size.
STM32F098VC has 256 KB of flash ROM and 32 KB of SRAM.
I suppose that barebox can be linked to put code into flash ROM (e.g. see ROMKERNEL
option for blackfin linux kernel port) and 32 KB of RAM can be enough for data
but IMHO 32 KB is not enough for comfort and useful work.
AFAIR It is possible to run risc-v barebox (both code and data) inside 192 KB RAM memory
space in a VERY VERY MINIMAL configuration, just demo.
Barebox can be really useful on linux-capable STM32 chips and board, e.g.
STM32F429 DISCO board (https://www.st.com/en/evaluation-tools/32f429idiscovery.html)
> I couldn't find any mention of such a board in the board support section of the documentation.
>
> I hope I didn't overlook something.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-02-12 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 12:57 Kai Che
2019-02-12 13:34 ` Roland Hieber
2019-02-12 13:47 ` Oleksij Rempel
2019-02-12 14:50 ` Antony Pavlov [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=20190212175045.d8af82f1a3fdc47c21957d72@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=Kai.Che@mixed-mode.de \
--cc=barebox@lists.infradead.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