From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL Dfu update
Date: Wed, 30 Oct 2013 07:32:54 -0700 [thread overview]
Message-ID: <52711896.6010900@boundarydevices.com> (raw)
In-Reply-To: <52711686.1070409@denx.de>
On 10/30/2013 07:24 AM, Stefano Babic wrote:
> Hi Otavio,
>
> On 30/10/2013 15:19, Otavio Salvador wrote:
>
>>> OMAP4/3 can boot over the otg, so you can send MLO and let it wait for the
>>> second stage boot. We have already SPL USBETH in u-boot but in production
>>> otg flashing can be very useful. Think SPL as a differently configured U-BOOT
>>> doesn't change the problem but yes it's a nice idea.
>>
>> But you'd usually want to have an 'upgrade mode' which allows DFU to
>> run. In this case, this could be done using complete U-Boot instead of
>> SPL, no? In case customer needs a slim version of it, it could be
>> accomplished using a specific config and having:
>>
>> SPL
>> Update mode U-Boot (normal U-Boot with less features)
>> Complete U-Boot (interactive and like)
>>
>> or am I missing something?
>
>
> Right, I agree completely with you.
>
> That's the reason I do not understand why we have to push DFU into SPL.
> Maybe we both are missing something.
>
If I understand Tom's comment, I think the question surrounds
a "bare metal" use case, when a full U-Boot isn't available in
the normal place.
In the case of our i.MX boards that boot to SPI-NOR, it would be
nice to simply load an SPL image over the i.MX downloader
and have immediate access to DFU so we can use it to
program the SPI-NOR.
Regards,
Eric
next prev parent reply other threads:[~2013-10-30 14:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 8:28 [U-Boot] SPL Dfu update Michael Trimarchi
2013-10-30 8:38 ` Michael Trimarchi
2013-10-30 12:58 ` Lukasz Majewski
2013-10-30 13:15 ` Michael Trimarchi
2013-10-30 13:28 ` Stefano Babic
2013-10-30 13:29 ` Michael Trimarchi
2013-10-30 13:44 ` Tom Rini
2013-10-30 13:52 ` Michael Trimarchi
2013-10-30 14:19 ` Otavio Salvador
2013-10-30 14:24 ` Stefano Babic
2013-10-30 14:32 ` Eric Nelson [this message]
2013-10-30 15:58 ` Michael Trimarchi
2013-10-30 20:01 ` Wolfgang Denk
2013-10-30 20:08 ` Eric Nelson
2013-10-30 14:34 ` Michael Trimarchi
2013-10-30 19:33 ` Tom Rini
2013-10-30 19:43 ` Michael Trimarchi
2013-10-30 19:47 ` Tom Rini
2013-10-30 19:58 ` Michael Trimarchi
2013-10-30 20:04 ` Tom Rini
2013-10-30 20:03 ` Wolfgang Denk
2013-10-30 20:06 ` Michael Trimarchi
2013-10-30 19:36 ` Tom Rini
2013-10-30 19:58 ` Wolfgang Denk
2013-10-30 20:01 ` Michael Trimarchi
2013-10-30 20:11 ` Wolfgang Denk
2013-10-30 20:35 ` Michael Trimarchi
2013-10-30 20:53 ` Otavio Salvador
2013-10-30 21:37 ` Michael Trimarchi
2013-10-31 13:20 ` Tom Rini
2013-11-08 22:09 ` Michael Trimarchi
2013-10-30 20:07 ` Tom Rini
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=52711896.6010900@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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