[U-Boot] [PATCH] doc: README.mxs: Add instruction to install 'libssl-dev'

[U-Boot] [PATCH] doc: README.mxs: Add instruction to install 'libssl-dev'

[Fabio Estevam]

From: Fabio Estevam <fabio.estevam@freescale.com>

Building the mx28evk target on a host PC without the 'libssl-dev' package, 
results in the following build error:

mxsimage.c:18:25: fatal error: openssl/evp.h: No such file or directory

Add an entry about the need of installing this package.

Also, remove the 'elftosb' text, since now we have the new 'mxsimage' method.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 doc/README.mxs | 37 +++----------------------------------
 1 file changed, 3 insertions(+), 34 deletions(-)

diff --git a/doc/README.mxs b/doc/README.mxs
index 5d9e72f..265cebd 100644
--- a/doc/README.mxs
+++ b/doc/README.mxs
@@ -27,41 +27,10 @@ Contents
 1) Prerequisites
 ----------------
 
-To make a MXS based board bootable, some tools are necessary. The first one is
-the "elftosb" tool distributed by Freescale Semiconductor. The other one is the
-"mxsboot" tool found in U-Boot source tree.
+To make a MXS based board bootable, it is necessary to install the following
+package on the host PC. On a Debian-based distribution it would be:
 
-Firstly, obtain the elftosb archive from the following location:
-
-	ftp://ftp.denx.de/pub/tools/elftosb-10.12.01.tar.gz
-
-We use a $VER variable here to denote the current version. At the time of
-writing of this document, that is "10.12.01". To obtain the file from command
-line, use:
-
-	$ VER="10.12.01"
-	$ wget ftp://ftp.denx.de/pub/tools/elftosb-${VER}.tar.gz
-
-Extract the file:
-
-	$ tar xzf elftosb-${VER}.tar.gz
-
-Compile the file. We need to manually tell the linker to use also libm:
-
-	$ cd elftosb-${VER}/
-	$ make LIBS="-lstdc++ -lm" elftosb
-
-Optionally, remove debugging symbols from elftosb:
-
-	$ strip bld/linux/elftosb
-
-Finally, install the "elftosb" binary. The "install" target is missing, so just
-copy the binary by hand:
-
-	$ sudo cp bld/linux/elftosb /usr/local/bin/
-
-Make sure the "elftosb" binary can be found in your $PATH, in this case this
-means "/usr/local/bin/" has to be in your $PATH.
+sudo apt-get install libssl-dev
 
 2) Compiling U-Boot for a MXS based board
 -------------------------------------------
-- 
1.8.1.2

[U-Boot] [PATCH] doc: README.mxs: Add instruction to install 'libssl-dev'

[Fabio Estevam]

On Sat, Sep 14, 2013 at 7:21 PM, Fabio Estevam <festevam@gmail.com> wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Building the mx28evk target on a host PC without the 'libssl-dev' package,
> results in the following build error:
>
> mxsimage.c:18:25: fatal error: openssl/evp.h: No such file or directory
>
> Add an entry about the need of installing this package.
>
> Also, remove the 'elftosb' text, since now we have the new 'mxsimage' method.

Ops, looks like we cannot remove elftosb yet.

When I try "make u-boot.sb":

make[1]: Entering directory `/home/fabio/denx/u-boot/arch/arm/cpu/arm926ejs/mxs'
sed "s at OBJTREE@/home/fabio/denx/u-boot at g"
/home/fabio/denx/u-boot/arch/arm/cpu/arm926ejs/mxs/u-boot-imx28.bd >
/home/fabio/denx/u-boot/u-boot.bd
elftosb -zf imx28 -c /home/fabio/denx/u-boot/u-boot.bd -o
/home/fabio/denx/u-boot/u-boot.sb
make[1]: elftosb: Command not found

[U-Boot] [PATCH] doc: README.mxs: Add instruction to install 'libssl-dev'

[Marek Vasut]

Dear Fabio Estevam,

> On Sat, Sep 14, 2013 at 7:21 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > From: Fabio Estevam <fabio.estevam@freescale.com>
> > 
> > Building the mx28evk target on a host PC without the 'libssl-dev'
> > package, results in the following build error:
> > 
> > mxsimage.c:18:25: fatal error: openssl/evp.h: No such file or directory
> > 
> > Add an entry about the need of installing this package.
> > 
> > Also, remove the 'elftosb' text, since now we have the new 'mxsimage'
> > method.
> 
> Ops, looks like we cannot remove elftosb yet.
> 
> When I try "make u-boot.sb":
> 
> make[1]: Entering directory
> `/home/fabio/denx/u-boot/arch/arm/cpu/arm926ejs/mxs' sed
> "s at OBJTREE@/home/fabio/denx/u-boot at g"
> /home/fabio/denx/u-boot/arch/arm/cpu/arm926ejs/mxs/u-boot-imx28.bd >
> /home/fabio/denx/u-boot/u-boot.bd
> elftosb -zf imx28 -c /home/fabio/denx/u-boot/u-boot.bd -o
> /home/fabio/denx/u-boot/u-boot.sb
> make[1]: elftosb: Command not found

mxsimage is not enabled by default yet, I would like to postpone that for next 
release. But (!) it would be nice if you did start testing it so when enabled, 
it is working well.

Best regards,
Marek Vasut

[U-Boot] [PATCH] doc: README.mxs: Add instruction to install 'libssl-dev'

[Fabio Estevam]

Hi Marek,

On Sun, Sep 15, 2013 at 11:03 AM, Marek Vasut <marex@denx.de> wrote:

> mxsimage is not enabled by default yet, I would like to postpone that for next
> release. But (!) it would be nice if you did start testing it so when enabled,
> it is working well.

Ok, so the issue was that I was using the mkimage provided by Ubuntu
instead of the one provided by U-boot.

There is also a typo in the directory path (arch/arm/boot/ does not exist):

With the changes below I can build u-boot.sb via mkimage method:

--- a/doc/README.mxsimage
+++ b/doc/README.mxsimage
@@ -9,12 +9,12 @@ Usage -- producing image:
 The mxsimage tool is targeted to be a simple replacement for the elftosb2 .
 To generate an image, write an image configuration file and run:

- mkimage -A arm -O u-boot -T mxsimage -n <path to configuration file> \
+ ./tools/mkimage -A arm -O u-boot -T mxsimage -n <path to configuration file> \
          <output bootstream file>

 The output bootstream file is usually using the .sb file extension. Note
 that the example configuration files for producing bootable BootStream with
-the U-Boot bootloader can be found under arch/arm/boot/cpu/arm926ejs/mxs/
+the U-Boot bootloader can be found under arch/arm/cpu/arm926ejs/mxs/
 directory. See the following files:

  mxsimage.mx23.cfg -- This is an example configuration for i.MX23
@@ -158,7 +158,7 @@ Usage -- verifying image:
 The mxsimage can also verify and dump contents of an image. Use the following
 syntax to verify and dump contents of an image:

- mkimage -l <input bootstream file>
+ ./tools/mkimage -l <input bootstream file>

 This will output all the information from the SB image header and all the
 instructions contained in the SB image. It will also check if the various

If you agree with this change, I can send a patch.

Regards,

Fabio Estevam

[U-Boot] [PATCH] doc: README.mxs: Add instruction to install 'libssl-dev'

[Marek Vasut]

Dear Fabio Estevam,

> Hi Marek,
> 
> On Sun, Sep 15, 2013 at 11:03 AM, Marek Vasut <marex@denx.de> wrote:
> > mxsimage is not enabled by default yet, I would like to postpone that for
> > next release. But (!) it would be nice if you did start testing it so
> > when enabled, it is working well.
> 
> Ok, so the issue was that I was using the mkimage provided by Ubuntu
> instead of the one provided by U-boot.
> 
> There is also a typo in the directory path (arch/arm/boot/ does not exist):
> 
> With the changes below I can build u-boot.sb via mkimage method:
> 
> --- a/doc/README.mxsimage
> +++ b/doc/README.mxsimage
> @@ -9,12 +9,12 @@ Usage -- producing image:
>  The mxsimage tool is targeted to be a simple replacement for the elftosb2
> . To generate an image, write an image configuration file and run:
> 
> - mkimage -A arm -O u-boot -T mxsimage -n <path to configuration file> \
> + ./tools/mkimage -A arm -O u-boot -T mxsimage -n <path to configuration
> file> \ <output bootstream file>
> 
>  The output bootstream file is usually using the .sb file extension. Note
>  that the example configuration files for producing bootable BootStream
> with -the U-Boot bootloader can be found under
> arch/arm/boot/cpu/arm926ejs/mxs/ +the U-Boot bootloader can be found under
> arch/arm/cpu/arm926ejs/mxs/ directory. See the following files:
> 
>   mxsimage.mx23.cfg -- This is an example configuration for i.MX23
> @@ -158,7 +158,7 @@ Usage -- verifying image:
>  The mxsimage can also verify and dump contents of an image. Use the
> following syntax to verify and dump contents of an image:
> 
> - mkimage -l <input bootstream file>
> + ./tools/mkimage -l <input bootstream file>
> 
>  This will output all the information from the SB image header and all the
>  instructions contained in the SB image. It will also check if the various
> 
> If you agree with this change, I can send a patch.
> 
> Regards,
> 
> Fabio Estevam

WFM, thanks. You could mention that the mkimage in uboot should be used. Note 
though, that when building out of tree, the location might differ.

Best regards,
Marek Vasut