On Mon, Mar 2, 2015 at 10:20 AM, Fabio Estevam <fabio.este...@freescale.com> wrote: > Provide instructions on how to upgrade U-boot in the eMMC. > > Signed-off-by: Fabio Estevam <fabio.este...@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 mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
