[U-Boot] [PATCH] warp: Add a README file

[U-Boot] [PATCH] warp: Add a README file

[Fabio Estevam]

Provide instructions on how to upgrade U-boot in the eMMC.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 board/warp/README | 56 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 board/warp/README

diff --git a/board/warp/README b/board/warp/README
new file mode 100644
index 0000000..da77542
--- /dev/null
+++ b/board/warp/README
@@ -0,0 +1,56 @@
+How to Update U-boot on Warp board
+----------------------------------
+
+Required software on the host PC:
+
+- imx_loader: https://github.com/warpboard/imx_usb_loader
+
+- dfu-util: http://dfu-util.sourceforge.net/releases/
+
+Build U-boot for Warp:
+
+$ make mrproper
+$ make warp_config
+$ make
+
+This will generate the U-boot binary called u-boot.imx.
+
+Put warp board in USB download mode
+
+Connect a USB to serial adapter between the host PC and warp
+
+Connect a USB cable between the OTG warp port and the host PC
+
+Open a terminal program such as minicom
+
+Copy u-boot.imx to the imx_usb folder.
+
+Load u-boot.imx via USB:
+
+$ sudo ./imx_usb
+
+Then U-boot should start and its messages will appear in the console program.
+
+Use the default environment variables:
+
+=> env default -f -a
+=> save
+
+Run the DFU command:
+=> dfu 0 mmc 0
+
+Transfer u-boot.imx that will be flashed into the eMMC:
+
+$ sudo dfu-util -D u-boot.imx -a boot
+
+Then on the U-boot prompt the following message should be seen after a succesful
+upgrade:
+
+#DOWNLOAD ... OK
+Ctrl+C to exit ...
+
+Remove power from the warp board.
+
+Put warp board into normal boot mode
+
+Power up the board and the new updated U-boot should boot from eMMC
-- 
1.9.1

[U-Boot] [PATCH] warp: Add a README file

[Otavio Salvador]

On Mon, Mar 2, 2015 at 10:20 AM, Fabio Estevam
<fabio.estevam@freescale.com> wrote:
> Provide instructions on how to upgrade U-boot in the eMMC.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>

> ---
>  board/warp/README | 56 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 56 insertions(+)
>  create mode 100644 board/warp/README
>
> diff --git a/board/warp/README b/board/warp/README
> new file mode 100644
> index 0000000..da77542
> --- /dev/null
> +++ b/board/warp/README
> @@ -0,0 +1,56 @@
> +How to Update U-boot on Warp board
> +----------------------------------
> +
> +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?

> +- dfu-util: http://dfu-util.sourceforge.net/releases/
> +
> +Build U-boot for Warp:
> +
> +$ make mrproper
> +$ make warp_config
> +$ make
> +
> +This will generate the U-boot binary called u-boot.imx.
> +
> +Put warp board in USB download mode
> +
> +Connect a USB to serial adapter between the host PC and warp
> +
> +Connect a USB cable between the OTG warp port and the host PC
> +
> +Open a terminal program such as minicom
> +
> +Copy u-boot.imx to the imx_usb folder.
> +
> +Load u-boot.imx via USB:
> +
> +$ sudo ./imx_usb

$ sudo ./imx_usb <path to u-boot.imx>

> +
> +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.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[U-Boot] [PATCH] warp: Add a README file

[Fabio Estevam]

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

[U-Boot] [PATCH] warp: Add a README file

[Eric Nelson]

Hi Fabio,

On 03/02/2015 08:33 AM, Fabio Estevam wrote:
> 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?
> 
It's probably best to use ours, but we're okay either way.

I wasn't aware that Warp had forked imx_usb_loader, but a quick
read shows that it's behind by a couple of (minor) updates.

As for the mx6sl_usb_work.conf file, we'll certainly allow
the Warp-specific version to be stored in our repository
as long as it's named for the Warp

i.e.:
	mx6sl_usb_work-warp.conf

If somebody want to push a pull request, we'll be happy
to stash it there.

Regards,


Eric

[U-Boot] [PATCH] warp: Add a README file

[Fabio Estevam]

Hi Eric,

On Mon, Mar 2, 2015 at 12:48 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:

> It's probably best to use ours, but we're okay either way.
>
> I wasn't aware that Warp had forked imx_usb_loader, but a quick
> read shows that it's behind by a couple of (minor) updates.
>
> As for the mx6sl_usb_work.conf file, we'll certainly allow
> the Warp-specific version to be stored in our repository
> as long as it's named for the Warp
>
> i.e.:
>         mx6sl_usb_work-warp.conf
>
> If somebody want to push a pull request, we'll be happy
> to stash it there.

I have just tested top of tree imx_usb_loader from Boundary Device and
it can load U-boot on mx6sl without any change.

Thanks,

Fabio Estevam

[U-Boot] [PATCH] warp: Add a README file

[Eric Nelson]

On 03/02/2015 08:52 AM, Fabio Estevam wrote:
> Hi Eric,
> 
> On Mon, Mar 2, 2015 at 12:48 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
> 
>> It's probably best to use ours, but we're okay either way.
>>
>> I wasn't aware that Warp had forked imx_usb_loader, but a quick
>> read shows that it's behind by a couple of (minor) updates.
>>
>> As for the mx6sl_usb_work.conf file, we'll certainly allow
>> the Warp-specific version to be stored in our repository
>> as long as it's named for the Warp
>>
>> i.e.:
>>         mx6sl_usb_work-warp.conf
>>
>> If somebody want to push a pull request, we'll be happy
>> to stash it there.
> 
> I have just tested top of tree imx_usb_loader from Boundary Device and
> it can load U-boot on mx6sl without any change.
> 

Cool. Glad to hear it.