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

[U-Boot] [PATCH v2] 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>
---
Changes since v1:
- Use Boundary Device's tree for imx_usb_loader
- Pass u-boot.imx as an argument of imx_usb

 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..d315140
--- /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_usb_loader: https://github.com/boundarydevices/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_loader folder.
+
+Load u-boot.imx via USB:
+
+$ sudo ./imx_usb 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
+
+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 v2] warp: Add a README file

[Otavio Salvador]

On Mon, Mar 2, 2015 at 12:57 PM, 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>
> ---
> Changes since v1:
> - Use Boundary Device's tree for imx_usb_loader
> - Pass u-boot.imx as an argument of imx_usb
>
>  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..d315140
> --- /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_usb_loader: https://github.com/boundarydevices/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_loader folder.
> +
> +Load u-boot.imx via USB:
> +
> +$ sudo ./imx_usb 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

Isn't the new binary overwriting it?

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



-- 
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 v2] warp: Add a README file

[Fabio Estevam]

Hi Otavio,

On Mon, Mar 2, 2015 at 2:36 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>> +Use the default environment variables:
>> +
>> +=> env default -f -a
>> +=> save
>
> Isn't the new binary overwriting it?

Let's say we are not using DFU and we want to flash u-boot.imx in the
SD card of mx6qsabresd, for example. In this case, we simply do:

dd if=u-boot.imx of=/dev/mmcblk0 bs=1k seek=1

and the new u-boot.imx is flashed in the SD card, and the env vars are
not touched.

Same happens with DFU, so that's why I include the ' env default -f
-a' in the instructions.

Not sure if I understand the issue you are trying to describe.

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

[Otavio Salvador]

On Mon, Mar 2, 2015 at 2:53 PM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Otavio,
>
> On Mon, Mar 2, 2015 at 2:36 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>>> +Use the default environment variables:
>>> +
>>> +=> env default -f -a
>>> +=> save
>>
>> Isn't the new binary overwriting it?
>
> Let's say we are not using DFU and we want to flash u-boot.imx in the
> SD card of mx6qsabresd, for example. In this case, we simply do:
>
> dd if=u-boot.imx of=/dev/mmcblk0 bs=1k seek=1
>
> and the new u-boot.imx is flashed in the SD card, and the env vars are
> not touched.
>
> Same happens with DFU, so that's why I include the ' env default -f
> -a' in the instructions.
>
> Not sure if I understand the issue you are trying to describe.

Well this README is covering WaRP so we ought to cover WaRP specifics there.

-- 
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 v2] warp: Add a README file

[Fabio Estevam]

Hi Otavio,

On Mon, Mar 2, 2015 at 3:12 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:

> Well this README is covering WaRP so we ought to cover WaRP specifics there.

What is the exact part of the README that has problems?

Sorry, I am not able to get your point.

Please be specific.

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

[Otavio Salvador]

On Mon, Mar 2, 2015 at 3:14 PM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Otavio,
>
> On Mon, Mar 2, 2015 at 3:12 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>
>> Well this README is covering WaRP so we ought to cover WaRP specifics there.
>
> What is the exact part of the README that has problems?
>
> Sorry, I am not able to get your point.
>
> Please be specific.

Sorry; now it is clear. You need the env to DFU to work.

-- 
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 v2] warp: Add a README file

[Otavio Salvador]

On Mon, Mar 2, 2015 at 3:22 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Mon, Mar 2, 2015 at 3:14 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Otavio,
>>
>> On Mon, Mar 2, 2015 at 3:12 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>>
>>> Well this README is covering WaRP so we ought to cover WaRP specifics there.
>>
>> What is the exact part of the README that has problems?
>>
>> Sorry, I am not able to get your point.
>>
>> Please be specific.
>
> Sorry; now it is clear. You need the env to DFU to work.

Acked-by: Otavio Salvador <otavio@ossystems.com.br>

-- 
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 v2] warp: Add a README file

[Stefano Babic]

On 02/03/2015 16:57, Fabio Estevam wrote:
> Provide instructions on how to upgrade U-boot in the eMMC.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---

Applied to u-boot-imx, thanks !

Best regards,
Stefano Babic




-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================