Hi Otavio,
On Mon, Mar 2, 2015 at 11:52 AM, Otavio Salvador otavio@ossystems.com.br wrote:
+Required software on the host PC:
+- imx_loader: https://github.com/warpboard/imx_usb_loader
I see no reason to link WaRP's fork. The Boundary Devices upstream code offers a more up to date bases and I think we should give them the credit for the tool. Mind to change it?
No problem for me to link Boundary Device's tree, but then we would need to create a mx6sl_usb_work.conf in this tree, so that the LOADADDR could be adapted for mx6sl. Then we also need to pass mx6sl_usb_work.conf in the imx_usb command line.
Eric,
What do you think?
+Load u-boot.imx via USB:
+$ sudo ./imx_usb
$ sudo ./imx_usb <path to u-boot.imx>
It worked for me without the extra arg, but I can pass the arg in this Howto to make it clearer.
+Then U-boot should start and its messages will appear in the console program.
+Use the default environment variables:
+=> env default -f -a +=> save
I think this is not needed as the environment will be rewritten when the U-Boot is overridden.
I tested it and the env ins not overwritten, so we need to explicitly overwrite the envs in order to have the correct dfu_alt_info variable for DFU to work.
Regards,
Fabio Estevam