On 2017-09-11 07:15, Vincent Prince wrote: > Hi Stefan, > > It was probably a Windows bug as it is almost working now.
Yeah with Windows the multiple re-enumeration is sometimes a bit strange, it leads to rather long running driver search on first connect. > I was wondering why sdp command is expecting a jump ? > Is it necessary to jump after USB transfer, or we should download > anything we want and jump if asked ? You don't have to jump, you can also go back to the console using Ctrl+C. The jump just allows you to remotely continue booting with a specific script... -- Stefan > > Regards, > Vincent > > > 2017-09-08 18:37 GMT+02:00 Stefan Agner <ste...@agner.ch>: >> Hi Vincent, >> >> On 2017-09-08 01:27, Vincent Prince wrote: >>> Hi everyone, >>> >>> I managed to get SDP protocol to work with on my custom i.MX6 board, >>> so big thanks to Stefan for your work! >>> >>> I'm now trying to load swupdate ramdisk with u-boot sdp command, >>> without success. >>> Is it a possible use case ? >> >> Yes it should work, we use the U-Boot sdp command to download a squashfs >> based ramdisk in our Toradex Easy Installer: >> http://developer.toradex.com/software/toradex-easy-installer >> >>> >>> Here my steps: >>> >>> In u-boot: >>> => sdp 0 >>> >>> On Host, >>> $ imx_usb >>> >>> config file <C:\Users\vpr\IMXUSBLOADER2\delivery\\imx_usb.conf> >>> vid=0x15a2 pid=0x0061 file_name=mx6_usb_rom.conf -> vid=0x0525 >>> pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf >>> vid=0x0525 pid=0xa4a5 file_name=mx6_usb_uboot.conf >>> config file <C:\Users\vpr\IMXUSBLOADER2\delivery\\mx6_usb_uboot.conf> >>> parse C:\Users\vpr\IMXUSBLOADER2\delivery\\mx6_usb_uboot.conf >>> Trying to open device vid=0x0525 pid=0xa4a5......................... >>> Could not open device vid=0x0525 pid=0xa4a5 >> >> Is VID/PID showing up in Device Manager? >> >> We did saw some problems with certain USB host implementation, so it >> might be a device dependency... I would also try a different >> machine/maybe Linux machine... >> >>> >>> VID/PID in imx_usb.conf are correctly detected, and correct >>> configuration file is launched (mx6_usb_uboot.conf), >>> it contains: >>> >>> mx6_usb_sdp_uboot >>> hid,1024,0x10000000,1G,0x00907000,0x31000 >>> test.txt:load 0x12100000 >>> >>> My imx_usb.conf is the following: >>> >>> #vid:pid, config_file >>> 0x15a2:0x0061, mx6_usb_rom.conf, 0x0525:0xb4a4, mx6_usb_sdp_spl.conf >>> 0x0525:0xa4a5, mx6_usb_uboot.conf >> >> Yeah assuming you use the Toradex branch of imx_loader currently this >> should work. >> >> Our script looks like this: >> mx6_usb_sdp_uboot >> #hid/bulk,[old_header,]max packet size, {ram start, ram size}(repeat >> valid ram areas) >> hid,1024,0x10000000,1G,0x00907000,0x31000 >> #Load complete FIT image to $ramdisk_addr_r >> tezi.itb:load 0x12100000 >> #Load script to $loadaddr and jump to it >> boot-sdp.scr:load 0x12000000,jump 0x12000000 >> >> -- >> Stefan >> >> >>> >>> Am I missing something, >>> Thanks, >>> Vincent >>> >>> 2017-09-01 22:09 GMT+02:00 Stefan Agner <ste...@agner.ch>: >>>> >>>> >>>> On September 1, 2017 12:25:44 PM PDT, Fabio Estevam <feste...@gmail.com> >>>> wrote: >>>>>On Fri, Sep 1, 2017 at 3:54 PM, Fabio Estevam <feste...@gmail.com> >>>>>wrote: >>>>> >>>>>> I have tested this method and it works, thanks. >>>>>> >>>>>> Do you plan to usptream this method? >>>>> >>>>>Or I can also put your patch as part of my series that adds SDP >>>>>support for imx6qsabresd if you prefer. >>>> >>>> Let me do a separate, I guess it could be controversial... >>>> >>>> -- >>>> Stefan >>>> -- >>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>> _______________________________________________ >>>> U-Boot mailing list >>>> U-Boot@lists.denx.de >>>> https://lists.denx.de/listinfo/u-boot _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot