From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lukasz Majewski Date: Wed, 5 Jun 2019 11:40:37 +0200 Subject: [U-Boot] [PATCH v2 3/3] usb: gadget: f_sdp: Allow SPL to load and boot FIT via SDP In-Reply-To: References: <20190604195629.27049-1-sjoerd.simons@collabora.co.uk> <20190604195629.27049-4-sjoerd.simons@collabora.co.uk> Message-ID: <20190605114037.46558a06@jawa> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Fabio, Sjoerd > On Tue, Jun 4, 2019 at 5:41 PM Sjoerd Simons > 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 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. To make it working (on host): cat << EOF > display5_recovery.lst uuu_version 1.2.135 SDP: boot -f /srv/tftp/SPL SDPU: write -f /srv/tftp/u-boot-dtb.img -addr 0x10000000 SDPU: jump -addr 0x10000000 SDPU: done EOF sudo ./uuu/uuu display5_recovery.lst > U-Boot 2019.01 is prior to the DM / fit conversion and loading SPL + > u-boot.img with the method above works fine. > > > One of the next things I will need to look at is actually secure > > boot.. That said why does imx_usb_loader if the board isn't > > locked? > > Not sure what you mean by locked. > > We have been using imx_usb_loader for a long time. After DM / fit > comvesion the IVT piece is not added into the final .img. > > From the main Makefile: > > ifdef CONFIG_SPL_LOAD_FIT > MKIMAGEFLAGS_u-boot.img = -f auto -A $(ARCH) -T firmware -C none -O > u-boot \ -a $(CONFIG_SYS_TEXT_BASE) -e $(CONFIG_SYS_UBOOT_START) \ > -n "U-Boot $(UBOOTRELEASE) for $(BOARD) board" -E \ > $(patsubst %,-b arch/$(ARCH)/dts/%.dtb,$(subst ",,$(CONFIG_OF_LIST))) > else > MKIMAGEFLAGS_u-boot.img = -A $(ARCH) -T firmware -C none -O u-boot \ > -a $(CONFIG_SYS_TEXT_BASE) -e $(CONFIG_SYS_UBOOT_START) \ > -n "U-Boot $(UBOOTRELEASE) for $(BOARD) board" > MKIMAGEFLAGS_u-boot-ivt.img = -A $(ARCH) -T firmware_ivt -C none -O > u-boot \ -a $(CONFIG_SYS_TEXT_BASE) -e $(CONFIG_SYS_UBOOT_START) \ > -n "U-Boot $(UBOOTRELEASE) for $(BOARD) board" > u-boot-ivt.img: MKIMAGEOUTPUT = u-boot-ivt.img.log > CLEAN_FILES += u-boot-ivt.img.log u-boot-dtb.imx.log SPL.log > u-boot.imx.log endif > > we can see that the ivt is not added for the CONFIG_SPL_LOAD_FIT > case. > > I tried to change this logic, but so far was not able to make it work. Best regards, Lukasz Majewski -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: