[U-Boot] MKIMAGE u-boot.imx build error

[U-Boot] MKIMAGE u-boot.imx build error

[Kucharczyk, David]

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

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.

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.

[U-Boot] MKIMAGE u-boot.imx build error

[Simon Glass]

Hi David,

On 27 October 2014 12:18, Kucharczyk, David <DKucharczyk@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] MKIMAGE u-boot.imx build error

[DaveKucharczyk]

Simon, thank you for your help.

Simon Glass-3 wrote
> BTW best not to have this in your sig when sending to a public mailing
> list.

I have no control of over my company's email signature so I switched my
subscription to use gmail.

Simon Glass-3 wrote
> 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. 

I was able to build using V=1 and noticed the entry point,
CONFIG_SYS_TEXT_BASE, wasn't defined in include/configs/mx53_xxx.h file. We
previously had it defined in /board/freescale/mx53_xxx/config.mk. Now
everything builds without error. 

But?I do not get serial output. I really need a small victory and see some
life out of the board. 

Here?s what I think is necessary to get serial output to console? 

1.	At minimum the uart setup in /board/freescale/mx53_xxx/mx53_xxx.c
2.	Version, boot device and DCD setup in
/board/freescale/mx53_xxx/imximage.cfg
3.	Minor changes to build successfully in /include/configs/mx53_xxx.h

I?ve ported flash_header.S to imximage.cfg.
I?ve moved our old /board/freescale/mx53_xxx/mx53_xxx.c to the new u-boot
directory, setup the pads using the new nomenclature and modified the
library includes to use the new ones. 
I?ve moved include/configs/mx53_xxx.h file to the new u-boot directory and
made the necessary edits to build successfully. 

I?ve triple checked the pads and flash header. I dd the resulting,
non-padded, u-boot.imx image to sd card by ?dd if=u-boot.imx of=/dev/sdd
seek=2 && sync?, but I get no life.

I?m stuck at the moment and hoping someone has some advice as to what I may
be missing or doing wrong. 

Best,
Dave



--
View this message in context: http://u-boot.10912.n7.nabble.com/MKIMAGE-u-boot-imx-build-error-tp193606p193874.html
Sent from the U-Boot mailing list archive at Nabble.com.

[U-Boot] MKIMAGE u-boot.imx build error

[Fabio Estevam]

On Wed, Oct 29, 2014 at 11:52 AM, DaveKucharczyk
<david.kucharczyk@gmail.com> wrote:

> I?ve triple checked the pads and flash header. I dd the resulting,
> non-padded, u-boot.imx image to sd card by ?dd if=u-boot.imx of=/dev/sdd
> seek=2 && sync?, but I get no life.

This command is not correct. You missed the bs=512 part.

It should be:

dd if=u-boot.imx of=/dev/sdX bs=512 seek=2; sync

[U-Boot] MKIMAGE u-boot.imx build error

[DaveKucharczyk]

Fabio Estevam-2 wrote
> This command is not correct. You missed the bs=512 part.
> 
> It should be:
> 
> dd if=u-boot.imx of=/dev/sdX bs=512 seek=2; sync

Sorry, I forgot the block size in my original email. Yes, I do include
bs=512. That is not the problem. 

I'm going through all the README's again, maybe I can spot something in
there.  




--
View this message in context: http://u-boot.10912.n7.nabble.com/MKIMAGE-u-boot-imx-build-error-tp193606p193882.html
Sent from the U-Boot mailing list archive at Nabble.com.

[U-Boot] MKIMAGE u-boot.imx build error

[Fabio Estevam]

On Wed, Oct 29, 2014 at 12:34 PM, DaveKucharczyk
<david.kucharczyk@gmail.com> wrote:
> Fabio Estevam-2 wrote
>> This command is not correct. You missed the bs=512 part.
>>
>> It should be:
>>
>> dd if=u-boot.imx of=/dev/sdX bs=512 seek=2; sync
>
> Sorry, I forgot the block size in my original email. Yes, I do include
> bs=512. That is not the problem.
>
> I'm going through all the README's again, maybe I can spot something in
> there.

Or maybe you can post your changes here in patch format so that we can
try to find some problems.

[U-Boot] MKIMAGE u-boot.imx build error

[Stefano Babic]

Hi Dave,

On 29/10/2014 14:52, DaveKucharczyk wrote:

> I was able to build using V=1 and noticed the entry point,
> CONFIG_SYS_TEXT_BASE, wasn't defined in include/configs/mx53_xxx.h file. We
> previously had it defined in /board/freescale/mx53_xxx/config.mk. Now
> everything builds without error. 
> 
> But?I do not get serial output. I really need a small victory and see some
> life out of the board. 
> 
> Here?s what I think is necessary to get serial output to console? 
> 
> 1.	At minimum the uart setup in /board/freescale/mx53_xxx/mx53_xxx.c
> 2.	Version, boot device and DCD setup in
> /board/freescale/mx53_xxx/imximage.cfg
> 3.	Minor changes to build successfully in /include/configs/mx53_xxx.h

Well, you made a lot of changes. I think you use 2009.08 from Freescale
tree, and there are a lot of differences with mainline tree.

Maybe it is worth if you check your code with the boars already
supported by U-Boot mainline having the i.MX53 SOC (Freescale's
mx53-loco, -ard, and -smd for example).

> 
> I?ve ported flash_header.S to imximage.cfg.
> I?ve moved our old /board/freescale/mx53_xxx/mx53_xxx.c to the new u-boot
> directory, setup the pads using the new nomenclature and modified the
> library includes to use the new ones. 
> I?ve moved include/configs/mx53_xxx.h file to the new u-boot directory and
> made the necessary edits to build successfully. 
> 
> I?ve triple checked the pads and flash header. I dd the resulting,
> non-padded, u-boot.imx image to sd card by ?dd if=u-boot.imx of=/dev/sdd
> seek=2 && sync?, but I get no life.
> 

Try to add a #define DEBUG in the code, for example to understand if
something is alive before the relocation.

> I?m stuck at the moment and hoping someone has some advice as to what I may
> be missing or doing wrong. 

I am afraid that it is too difficult, because it depends on your custom
hardware. Next step should be to attach a JTAG debugger to see what is
happening.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
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
=====================================================================