public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting Wandboard through USB
Date: Mon, 01 Jun 2015 02:15:15 +0300	[thread overview]
Message-ID: <556B9603.3080507@mail.bg> (raw)
In-Reply-To: <556B912B.3090409@mail.bg>

Hi guys,

Here's a proposal how to avoid changing the host boot software for the
SPL case:

- Power on
- Boot ROM announces usb device (0x15a2:0x0054 or 0x15a2:0x0054 or
0x15a2:0x0063)
- Host software uploads SPL over OTG
- Board initializes DDR
- Board initializes USB-OTG and announces again as a usb device with
slightly different PID (0x15a2:0x0055 or 0x15a2:0x0056 or
0x15a2:0x0064) or a special PID (0x15a2:0xffff), thus needs to
implement FSL boot protocol
- Both imx-usb-loader and mfgtool already have easy mechanism to detect
boards' by vid-pid and to sequence actions based on it. So basically
we'll just need an additional config for the host boot programs, which
need to feed the 2nd boot stage (one more file for imx-usb-loader, and
one more config section for the mfgtool), but otherwise it will be
quite straight-forward.

Overall, from the PC host this boot sequence will look like 2 boot
sequences for 2 separate usb devices (1 for SPL, 1 for u-boot.img).

Probably the most important question is "how easy is to implement the
FSL boot protocol in the remaining OCRAM free space". What do you think?

Regards,
Nikolay

  reply	other threads:[~2015-05-31 23:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  9:46 [U-Boot] Booting Wandboard through USB Vincent Stehlé
2015-05-30 16:49 ` Tom Rini
2015-05-30 17:24   ` Vincent Stehlé
2015-05-30 20:09     ` Eric Nelson
2015-05-30 20:38       ` Tom Rini
2015-05-31 22:54       ` Nikolay Dimitrov
2015-05-31 23:15         ` Nikolay Dimitrov [this message]
2015-06-01  8:10           ` Stefano Babic
2015-06-01 16:03             ` Tim Harvey
2015-06-01 16:28               ` Nikolay Dimitrov
2015-06-01 16:38                 ` Tim Harvey
2015-06-02 14:25                   ` Tom Rini
2015-06-02 15:00                     ` Tim Harvey
2015-06-01 16:08             ` Nikolay Dimitrov
2015-05-30 17:41   ` Eric Nelson
2015-05-30 19:25     ` Tom Rini
2015-05-30 19:53       ` Eric Nelson
2015-07-24  0:59     ` Fabio Estevam
2015-05-30 16:49 ` Fabio Estevam
  -- strict thread matches above, loose matches on Subject: below --
2017-07-27  9:05 Vincent Prince
2017-07-27 20:54 ` Wolfgang Denk
2017-08-05 12:22 ` Fabio Estevam
2017-08-05 13:44   ` Vincent Prince
2017-08-05 15:46     ` 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=556B9603.3080507@mail.bg \
    --to=picmaster@mail.bg \
    --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