On Thu, Apr 25, 2019 at 07:17:21AM +0000, Peng Fan wrote:
Hi Fabio,
-----Original Message----- From: Fabio Estevam [mailto:festevam@gmail.com] Sent: 2019年4月25日 6:23 To: Peng Fan peng.fan@nxp.com Cc: Abel Vesa abel.vesa@nxp.com; Stefano Babic sbabic@denx.de; Lukasz Majewski lukma@denx.de; Michael Trimarchi michael@amarulasolutions.com; dl-uboot-imx uboot-imx@nxp.com; Jagan Teki jagan@amarulasolutions.com; Marcel Ziswiler marcel.ziswiler@toradex.com; U-Boot-Denx u-boot@lists.denx.de; Adam Ford aford173@gmail.com; Ye Li ye.li@nxp.com; Otavio Salvador otavio@ossystems.com.br; Breno Matheus Lima breno.lima@nxp.com Subject: Re: Booting MX6 via Serial Download after DM conversion
Hi Peng,
On Tue, Apr 23, 2019 at 11:18 PM Peng Fan peng.fan@nxp.com wrote:
Not try this. uuu should support SPL file being loaded, then if SPL could runs into fastboot mode to interactive with uuu, then u-boot-dtb.img could be loaded
I think.
My colleague Breno tried to load SPL + u-boot-dtb.img using the UUU tool and it also failed.
Could you please try to fix this regression?
After check, it is not U-Boot issue, it is imx_usb should update to support new u-boot-dtb.img.
With your patch, file u-boot-dtb.img u-boot-dtb.img: u-boot legacy uImage, U-Boot 2019.04-00664-gdbe9a81ff0\270, Firmware/ARM, Firmware Image (Not compressed), 490914 bytes, Thu Apr 25 07:26:46 2019, Load Address: 0x17800000, Entry Point: 0x00000000, Header CRC: 0xCBE07038, Data CRC: 0x2C710405
without your patch, file u-boot-dtb.img u-boot-dtb.img: Device Tree Blob version 17, size=1399, boot CPU=0, string block size=139, DT structure block size=1204
Actually now u-boot-dtb.img is a FIT image with a device tree wrapper. So need fix imx_usb to support both legacy and new image format.
imx_usb is doing some checking of the second binary it sends along? That sounds odd to start with, is there some specific history there? Thanks!