[U-Boot] Booting MX6 via Serial Download after DM conversion
Hi,
Has anyone managed to boot i.MX6 via serial download protocol after the conversion to DM?
On a mx6sabresd I can no longer boot via SDP running 2019.04:
After running 'sudo ./imx_usb SPL' I get:
U-Boot SPL 2019.04 (Apr 22 2019 - 19:45:46 -0300) Trying to boot from USB SDP SDP: initialize... SDP: handle requests..
Then I load the u-boot-dtb.img binary and the following error is seen:
$ sudo ./imx_usb u-boot-dtb.img config file </usr/etc/imx-loader.d//imx_usb.conf> vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0080 file_name=mx6_usb_work.conf vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf vid=0x066f pid=0x37ff file_name=linux_gadget.conf vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf config file </usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf> parse /usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf Trying to open device vid=0x0525 pid=0xb4a4 Interface 0 claimed HAB security state: development mode (0x56787856) == work item filename u-boot-dtb.img load_size 0 bytes load_addr 0x00000000 dcd 1 clear_dcd 0 plug 1 jump_mode 3 jump_addr 0x00000000 == end work item header not found 8400:2e77d044, 4000 do_download failed, err=-22 HAB security state: development mode (0x56787856)
With 2019.01 (prior to DM conversion) I can boot via SDP just fine.
Does anyone have any suggestions?
Thanks,
Fabio Estevam
Hi Fabio
Subject: Booting MX6 via Serial Download after DM conversion
Hi,
Has anyone managed to boot i.MX6 via serial download protocol after the conversion to DM?
Include Abel who did the conversion.
On a mx6sabresd I can no longer boot via SDP running 2019.04:
After running 'sudo ./imx_usb SPL' I get:
Honestly I am not familiar with imx_usb, we use mfgtool previously and not uuu tool. Would you share where to download imx_usb and any doc, Then we will debug this issue.
Thanks, Peng.
U-Boot SPL 2019.04 (Apr 22 2019 - 19:45:46 -0300) Trying to boot from USB SDP SDP: initialize... SDP: handle requests..
Then I load the u-boot-dtb.img binary and the following error is seen:
$ sudo ./imx_usb u-boot-dtb.img config file </usr/etc/imx-loader.d//imx_usb.conf> vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0080 file_name=mx6_usb_work.conf vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf vid=0x066f pid=0x37ff file_name=linux_gadget.conf vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf config file </usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf> parse /usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf Trying to open device vid=0x0525 pid=0xb4a4 Interface 0 claimed HAB security state: development mode (0x56787856) == work item filename u-boot-dtb.img load_size 0 bytes load_addr 0x00000000 dcd 1 clear_dcd 0 plug 1 jump_mode 3 jump_addr 0x00000000 == end work item header not found 8400:2e77d044, 4000 do_download failed, err=-22 HAB security state: development mode (0x56787856)
With 2019.01 (prior to DM conversion) I can boot via SDP just fine.
Does anyone have any suggestions?
Thanks,
Fabio Estevam
On Mon, Apr 22, 2019 at 9:00 PM Peng Fan peng.fan@nxp.com wrote:
Hi Fabio
Subject: Booting MX6 via Serial Download after DM conversion
Hi,
Has anyone managed to boot i.MX6 via serial download protocol after the conversion to DM?
I 'think' the DM conversion requires the USB Driver to be defined as UCLASS_USB_GADGET_GENERIC in order to be used as a peripheral. I have been following one of the TI boards [1] who's USB Driver has a bind tool that go through the device tree and looks to see if the "dr_mode" entry and then binds the appropriate driver (either HOST or GADGET).
I started a conversion on this, so I have a patch I can sent to people, but I haven't gotten the GADGET side working, but I have a binder function that then loads the host driver when "dr_mode" is set to host. I haven't had a lot of time to try and figure out the GADGET side of things yet. If someone wants me to send the a patch for what I have so far, I can do that, but it only supports host mode.
I am fairly certain all gadget devices are broken on i.MX6 with DM_USB enabled, so in SPL, I had to disable DM_USB in order to maintain the SDP tool compatibility in SPL.
[1] - http://git.denx.de/?p=u-boot.git;a=commitdiff;h=7d98dbcc3dc8f1b93676d0953f3b...
adam
Include Abel who did the conversion.
On a mx6sabresd I can no longer boot via SDP running 2019.04:
After running 'sudo ./imx_usb SPL' I get:
Honestly I am not familiar with imx_usb, we use mfgtool previously and not uuu tool. Would you share where to download imx_usb and any doc, Then we will debug this issue.
Thanks, Peng.
U-Boot SPL 2019.04 (Apr 22 2019 - 19:45:46 -0300) Trying to boot from USB SDP SDP: initialize... SDP: handle requests..
Then I load the u-boot-dtb.img binary and the following error is seen:
$ sudo ./imx_usb u-boot-dtb.img config file </usr/etc/imx-loader.d//imx_usb.conf> vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0080 file_name=mx6_usb_work.conf vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf vid=0x066f pid=0x37ff file_name=linux_gadget.conf vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf config file </usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf> parse /usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf Trying to open device vid=0x0525 pid=0xb4a4 Interface 0 claimed HAB security state: development mode (0x56787856) == work item filename u-boot-dtb.img load_size 0 bytes load_addr 0x00000000 dcd 1 clear_dcd 0 plug 1 jump_mode 3 jump_addr 0x00000000 == end work item header not found 8400:2e77d044, 4000 do_download failed, err=-22 HAB security state: development mode (0x56787856)
With 2019.01 (prior to DM conversion) I can boot via SDP just fine.
Does anyone have any suggestions?
Thanks,
Fabio Estevam
Hi Peng,
On Mon, Apr 22, 2019 at 11:00 PM Peng Fan peng.fan@nxp.com wrote:
Honestly I am not familiar with imx_usb, we use mfgtool previously and not uuu tool. Would you share where to download imx_usb and any doc, Then we will debug this issue.
You can get imx_usb_loader tool from https://github.com/boundarydevices/imx_usb_loader
Install it, connect the board in USB download mode and then:
sudo ./imx_usb SPL sudo ./imx_usb u-boot-dtb.img
I suggest you to try U-boot 2019.01 first, which works fine and then 2019.04, which is broken.
I could get imx usb loader to successfully load 2019.04 if I manually change the defconfig like this:
--- a/configs/mx6sabresd_defconfig +++ b/configs/mx6sabresd_defconfig @@ -12,8 +12,6 @@ CONFIG_SPL_LIBDISK_SUPPORT=y CONFIG_NR_DRAM_BANKS=1 # CONFIG_SYS_MALLOC_F is not set CONFIG_FIT=y -CONFIG_SPL_FIT_PRINT=y -CONFIG_SPL_LOAD_FIT=y CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=arch/arm/mach-imx/spl_sd.cfg" # CONFIG_CONSOLE_MUX is not set CONFIG_SYS_CONSOLE_IS_IN_ENV=y @@ -21,7 +19,6 @@ CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE=y CONFIG_SUPPORT_RAW_INITRD=y CONFIG_BOUNCE_BUFFER=y CONFIG_SPL_SEPARATE_BSS=y -CONFIG_SPL_FIT_IMAGE_TINY=y CONFIG_SPL_FS_EXT4=y CONFIG_SPL_I2C_SUPPORT=y CONFIG_SPL_OS_BOOT=y @@ -56,15 +53,10 @@ CONFIG_CMD_FS_GENERIC=y CONFIG_EFI_PARTITION=y # CONFIG_SPL_EFI_PARTITION is not set CONFIG_OF_CONTROL=y -CONFIG_SPL_OF_CONTROL=y CONFIG_DEFAULT_DEVICE_TREE="imx6q-sabresd" CONFIG_OF_LIST="imx6q-sabresd imx6qp-sabresd imx6dl-sabresd" -CONFIG_MULTI_DTB_FIT=y -CONFIG_SPL_MULTI_DTB_FIT=y -CONFIG_SPL_OF_LIST="imx6dl-sabresd imx6q-sabresd imx6qp-sabresd" CONFIG_ENV_IS_IN_MMC=y CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y -CONFIG_SPL_DM=y CONFIG_USB_FUNCTION_FASTBOOT=y CONFIG_FASTBOOT_BUF_ADDR=0x12000000 CONFIG_FASTBOOT_BUF_SIZE=0x10000000 @@ -95,6 +87,4 @@ CONFIG_USB_GADGET_PRODUCT_NUM=0xa4a5 CONFIG_CI_UDC=y CONFIG_USB_HOST_ETHER=y CONFIG_USB_ETHER_ASIX=y -CONFIG_DM_VIDEO=y -CONFIG_VIDEO_IPUV3=y # CONFIG_VIDEO_SW_CURSOR is not set
Hi Peng and Abel,
On Mon, Apr 22, 2019 at 11:00 PM Peng Fan peng.fan@nxp.com wrote:
Honestly I am not familiar with imx_usb, we use mfgtool previously and not uuu tool.
Is the UUU tool capable of loading SPL + u-boot-dtb.img generated from mainline U-Boot for mx6sabresd?
Thanks
Hi Fabio
-----Original Message----- From: Fabio Estevam [mailto:festevam@gmail.com] Sent: 2019年4月24日 10:01 To: Peng Fan peng.fan@nxp.com; Abel Vesa abel.vesa@nxp.com Cc: 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 Subject: Re: Booting MX6 via Serial Download after DM conversion
Hi Peng and Abel,
On Mon, Apr 22, 2019 at 11:00 PM Peng Fan peng.fan@nxp.com wrote:
Honestly I am not familiar with imx_usb, we use mfgtool previously and not
uuu tool.
Is the UUU tool capable of loading SPL + u-boot-dtb.img generated from mainline U-Boot for mx6sabresd?
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.
Regards, Peng.
Thanks
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?
Thanks
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?
Things become complicated, there is no enough on chip ram for SPL DM, such as regulator/pinctrl/usb.
Regards, Peng.
Thanks
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.
Regards, Peng.
Thanks
Hi Peng,
On Thu, Apr 25, 2019 at 4:17 AM Peng Fan peng.fan@nxp.com wrote:
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.
This issue also affects the UUU tool as well.
Is there a fix for UUU?
Subject: Re: Booting MX6 via Serial Download after DM conversion
Hi Peng,
On Thu, Apr 25, 2019 at 4:17 AM Peng Fan peng.fan@nxp.com wrote:
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.
This issue also affects the UUU tool as well.
Is there a fix for UUU?
NXP software not enable SPL for this board, so I think UUU might not support it. But UUU support SPL + FIT for i.MX8MM, uuu might work for this board. I do not have time to check uuu side recently. Let me check whether others have time on this.
Regards, Peng.
-----Original Message----- From: Peng Fan Sent: Thursday, April 25, 2019 8:52 AM To: Fabio Estevam festevam@gmail.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; Frank Li frank.li@nxp.com Subject: RE: Booting MX6 via Serial Download after DM conversion
Subject: Re: Booting MX6 via Serial Download after DM conversion
Hi Peng,
On Thu, Apr 25, 2019 at 4:17 AM Peng Fan peng.fan@nxp.com wrote:
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.
This issue also affects the UUU tool as well.
Is there a fix for UUU?
[Frank Li] If follow up i.MX8MM method, uuu needn't change.
NXP software not enable SPL for this board, so I think UUU might not support it. But UUU support SPL + FIT for i.MX8MM, uuu might work for this board. I do not have time to check uuu side recently. Let me check whether others have time on this.
Regards, Peng.
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!
Hi Tom,
On Mon, Apr 29, 2019 at 2:57 PM Tom Rini trini@konsulko.com wrote:
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?
My understanding is that imx_usb_loader expects to find a valid IVT entry.
After the conversion to DM, a FIT image is used on mx6sabresd_defconfig and such IVT can no longer be found, causing imx_usb_loader to fail to loading u-boot-dtb.img.
It would be nice if we can come up with a solution, as loosing the ability to load via imx_usb_loader has a negative impact for users.
On Tue, Apr 30, 2019 at 02:39:17PM -0300, Fabio Estevam wrote:
Hi Tom,
On Mon, Apr 29, 2019 at 2:57 PM Tom Rini trini@konsulko.com wrote:
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?
My understanding is that imx_usb_loader expects to find a valid IVT entry.
After the conversion to DM, a FIT image is used on mx6sabresd_defconfig and such IVT can no longer be found, causing imx_usb_loader to fail to loading u-boot-dtb.img.
It would be nice if we can come up with a solution, as loosing the ability to load via imx_usb_loader has a negative impact for users.
Right, what I'm getting at is, why does imx_usb_loader need to find a specific anything in the binary? What is that IVT used for exactly?
On Thu, Apr 25, 2019 at 3:53 AM Fabio Estevam festevam@gmail.com wrote:
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?
fyi: we did see the same issue, look like FIT is incompatible with these device boot scenarios even HAB failed (which I tried before) with LOAD_FIT and OF_LIST.
Subject: Re: Booting MX6 via Serial Download after DM conversion
On Thu, Apr 25, 2019 at 3:53 AM Fabio Estevam festevam@gmail.com wrote:
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?
fyi: we did see the same issue, look like FIT is incompatible with these device boot scenarios even HAB failed (which I tried before) with LOAD_FIT and OF_LIST.
You mean SPL FIT + HAB to verify U-Boot on i.MX6Q failed, right?
It needs some special handling to use SPL FIT HAB which is not supported in upstream or vendor tree for i.MX6.
i.MX8M do have SPL FIT HAB in vendor tree.
Regards, Peng.
participants (6)
-
Adam Ford -
Fabio Estevam -
Frank Li -
Jagan Teki -
Peng Fan -
Tom Rini