Skip to contentSkip to conversation

warp: Add a README file

PATCH New Fabio Estevam 4 participants 8 messages Mar 2, 2015 – Mar 13, 2015

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 warp: Add a README file

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

---
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
board/warp/README new file +56 -0
new file mode 100644
index 0000000..d315140
@@ -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
Signature · 1 line
1.9.1
#1 lore raw

PATCH v2 1/1 warp: Add a README file

Quoted 45 lines · Fabio Estevam

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

---
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
board/warp/README new file +27 -0
new file mode 100644
index 0000000..d315140
@@ -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.
+

board/warp/README line 37

Quoted 10 lines
board/warp/README new file +10 -0
+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?

Quoted 21 lines
board/warp/README new file +18 -1
+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

Signature · 3 lines
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
#2 lore raw

PATCH v2 1/1 warp: Add a README file

Hi Otavio,

Quoted 6 lines · Otavio Salvador

board/warp/README line 37

Quoted 4 lines
board/warp/README new file +4 -0
+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.

#3 lore raw

PATCH v2 1/1 warp: Add a README file

Quoted 15 lines · Fabio Estevam

Hi Otavio,

Quoted 6 lines · Otavio Salvador

board/warp/README line 37

Quoted 4 lines
board/warp/README new file +4 -0
+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

Quoted 7 lines

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.

Signature · 3 lines
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
#4 lore raw

PATCH v2 1/1 warp: Add a README file

Hi Otavio,

Quoted 1 line · Otavio Salvador

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.

#5 lore raw

PATCH v2 1/1 warp: Add a README file

Quoted 11 lines · Fabio Estevam

Hi Otavio,

Quoted 1 line · Otavio Salvador

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.

Signature · 3 lines
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
#6 lore raw

PATCH v2 1/1 warp: Add a README file

Quoted 7 lines · Otavio Salvador
Quoted 6 lines · Fabio Estevam

Hi Otavio,

Quoted 1 line · Otavio Salvador

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

Quoted 7 lines
Quoted 5 lines

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.

Signature · 3 lines
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
#7 lore raw

PATCH v2 1/1 warp: Add a README file

In reply to Fabio Estevam
Quoted 4 lines · Fabio Estevam

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

---

Applied to u-boot-imx, thanks !

Best regards,
Stefano Babic

Signature · 5 lines
=====================================================================
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
=====================================================================