From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: gianluca <gianlucarenzi@eurek.it>, barebox@lists.infradead.org
Subject: Re: Barebox as first and second stage bootloader
Date: Wed, 26 Feb 2020 15:28:18 +0100 [thread overview]
Message-ID: <122509ae-f030-4f8a-0cae-eb2c2e31dbe9@pengutronix.de> (raw)
In-Reply-To: <4f2b01e0-ad01-d130-5c8e-9c3acac58770@eurek.it>
Hello,
On 2/26/20 12:57 PM, gianluca wrote:
> Hello,
> I was wondering if it possible to program Barebox (2020.01 or later) as first and second stage bootloader using the STM32 Programmer CLI tool.
FSBL is not supported at the moment. We use TF-A for that.
> I have the stm32mp157 evk-dk2 and I would like to have a working bootloader (running from SDRAM) via USB programming.
>
> I do not know how the OTP Fuses are set for trusted boot or simple SPL.
Not sure how this relates to booting over USB? You shouldn't need any
fuses burnt (but you can probably burn some to stop fallback to DFU)
> I suppose they are TF-A for first stage bootloader and SPL for the second one.
>
> The images built by Barebox (start_stm32mp157c_dk2.pblb[.stm32] and barebox-stm32mp157c-dk2.img) are suitable to be used as first stage bootloader running from internal SRAM and the .img as the second stage bootloader running from external SDRAM DDR???
No, they aren't. The current barebox implementation doesn't set up SDRAM and doesn't install
a secure monitor.
USB on the STM32MP1 is not yet complete. I posted some basic patches for the PHY, but we still
need host USB driver adjustments and a gadget driver for the DWC2.
> Is there somebody who is working with STM32 Cube Programmer or DFU-Utils to obtain this boot??
I don't think so. We will want to have a solution for this eventually though. Probably some
wrapper script that uses DFU to talk to BootROM, then to vendor TF-A, then to barebox.
As I understood, that's what the STM32CubeProgrammer is doing and it's shipped with
a FSBL and SSBL already for bootstrapping a system. Have you tried using that to
flash barebox?
Cheers
Ahmad
>
> Regards,
> Gianluca Renzi
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-02-26 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 11:57 gianluca
2020-02-26 14:28 ` Ahmad Fatoum [this message]
2020-02-26 14:46 ` gianluca
2020-02-26 15:08 ` Ahmad Fatoum
2020-02-26 15:30 ` gianluca
2020-02-26 15:46 ` Ahmad Fatoum
[not found] ` <2b5d2afe-c71e-34b9-efa5-57aaa5f28445@eurek.it>
2020-02-27 11:51 ` Ahmad Fatoum
2020-02-28 7:50 ` gianluca
2020-02-28 8:28 ` gianluca
2020-03-03 6:58 ` Ahmad Fatoum
[not found] ` <fb81fdd3-b674-ce0b-e472-ec8e606e4131@eurek.it>
2020-03-03 7:03 ` Ahmad Fatoum
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=122509ae-f030-4f8a-0cae-eb2c2e31dbe9@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=gianlucarenzi@eurek.it \
/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