Hi David, On 27 October 2014 12:18, Kucharczyk, David <dkucharc...@veeder.com> wrote: > Hi, I am in the middle of upgrading u-boot-2009.08 to u-boot-2014.07. Our > resident u-boot expert is on vacation and I'm running into some issues. After > working through a ton of compile errors I think I'm getting close. > > Our system is based on the Freescale iMX53. > > I am able to build and run on a mx53loco development board just fine, but for > some reason I'm getting the below error when building for our custom board, > which is similar to the development board. > > I've compared the development board files to our files and I can't pinpoint > why mkimage is giving a problem. > > > LD u-boot > OBJCOPY u-boot.bin > CFGS board/freescale/mx53_gogo/imximage.cfg.cfgtmp > MKIMAGE u-boot.imx > Usage: /home/dk/linux-upgrade/bootloader/u-boot-2014.07/tools/mkimage -l image > -l ==> list image header information > /home/dk/linux-upgrade/bootloader/u-boot-2014.07/tools/mkimage [-x] -A > arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] > image > -A ==> set architecture to 'arch' > -O ==> set operating system to 'os' > -T ==> set image type to 'type' > -C ==> set compression type 'comp' > -a ==> set load address to 'addr' (hex) > -e ==> set entry point to 'ep' (hex) > -n ==> set image name to 'name' > -d ==> use image data from 'datafile' > -x ==> set XIP (execute in place) > /home/dk/linux-upgrade/bootloader/u-boot-2014.07/tools/mkimage [-D > dtc_options] [-f fit-image.its|-F] fit-image > -D => set options for device tree compiler > -f => input filename for FIT source > Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined) > /home/dk/linux-upgrade/bootloader/u-boot-2014.07/tools/mkimage -V ==> > print version information and exit > make[1]: *** [u-boot.imx] Error 1 > make: *** [u-boot.imx] Error 2 > gogo build failed
There are only 3 places in mkimage.c which call usage() so you should be able to track which one it is. Probably building with V=1 will show you the mkimage command line you are using. > > If I set #define CONFIG_FIT_SIGNATURE in the config file then I get a ton of > other build errors so I'm not sure if that's the correct path to take. > Besides, the development board doesn't have CONFIG_FIT_SIGNATURE defined in > its config file. This is for verified boot which you probably don't need. You will need openssl for this. Regards, Simon > > Any help would be greatly appreciated. > > Thanks, > Dave > > Please be advised that this email may contain confidential information. If > you are not the intended recipient, please notify us by email by replying to > the sender and delete this message. The sender disclaims that the content of > this email constitutes an offer to enter into, or the acceptance of, any > agreement; provided that the foregoing does not invalidate the binding effect > of any digital or other electronic reproduction of a manual signature that is > included in any attachment. BTW best not to have this in your sig when sending to a public mailing list. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
