[U-Boot] [PATCH v2 3/3] usb: gadget: f_sdp: Allow SPL to load and boot FIT via SDP
Sjoerd Simons
sjoerd.simons at collabora.co.uk
Wed Jun 5 10:00:52 UTC 2019
On Wed, 2019-06-05 at 11:40 +0200, Lukasz Majewski wrote:
> Hi Fabio, Sjoerd
>
> > On Tue, Jun 4, 2019 at 5:41 PM Sjoerd Simons
> > <sjoerd.simons at collabora.co.uk> wrote:
> >
> > > Small steps right; Ooi what imx_usb_loader configuration/commands
> > > are you using to test this? (I find its config rather tricky to
> > > grasp).
> >
> > I simply run:
> >
> > sudo ./imx_usb SPL
> >
> > and then
> >
> > sudo ./imx_usb u-boot-dtb.img
> >
> > I suggest you to try U-Boot 2019.01 on a mx6sabreauto first.
> >
>
> Tested-by: Lukasz Majewski <lukma at denx.de>
>
> Test HW: i.MX6Q Display5 factory setup.
>
>
>
> However, one thing puzzles me - the VID / PID used.When I run uuu
> (mfgtools: SHA1: 13d187304f4faa473d2141409419c5b6f052addb):
>
> I see that "Build in config" has following VID/PID:
> SDPU: SPL 0x0525 0xb4a4 [0x0000..0x04ff] [1]
> SDPV: SPL1 0x0525 0xb4a4 [0x0500..0x9998]
> SDPU: SPL 0x0525 0xb4a4 [0x9999..0x9999]
>
> But to make the SDPU command working I had to adjust it to be similar
> to sabreauto (CONFIG_USB_GADGET_VENDOR_NUM=0x0525
> CONFIG_USB_GADGET_PRODUCT_NUM=0xa4a5). Those match to "FB"
> (fastboot?).
>
> Is this a bug or just the "Build in config" information is outdated?
> With VID/PID set as for [1] (and as we use SDPU command, not FB), the
> uuu doesn't connect to loaded SPL.
So u-boot for the spl does (arch/arm/mach-imx/spl.c):
```
int g_dnl_bind_fixup(struct usb_device_descriptor *dev, const char *name)
{
put_unaligned(CONFIG_USB_GADGET_PRODUCT_NUM + 0xfff, &dev->idProduct);
``
Iotw with CONFIG_USB_GADGET_PRODUCT_NUM=0xa4a5 in the config when in
the SPL the product will be 0xb4a4, which uuu recognizes.
Once in the main u-boot image in principle you shoudl be able to use
`FB:`, however it doesn't seem `FB: ucmd` is supported for mainline u-
boot so...
--
Sjoerd Simons
Collabora Ltd.
More information about the U-Boot
mailing list