| Message ID | CAOMZO5BnXsz+C=TROs2j7LpPgJTut0No_EL_jmgyaamEetVicA@mail.gmail.com |
|---|---|
| State | Changes Requested |
| Delegated to: | Stefano Babic |
| Headers | show |
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
--- 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