AnsweredAssumed Answered

Secure Boot: [Authenticate Data] of CSF file for u-boot iMX6

Question asked by satyadamarla on Jun 20, 2016
Latest reply on Jun 27, 2016 by satyadamarla

Hello Guys,


I have trouble with getting the signed u-boot to run. I successfully programmed the Fuse strictly according to the iMX6 Secure Boot guidelines. I doubt its the Authenticate Data from the CSF file thats the issue. The output of the build is as follows:


tools/mkimage -n  imxcfg.imx -T imximage \

  -e 0x17800000 -d u-boot.bin u-boot.imx

Image Type:   Freescale IMX Boot Image

Image Ver:    2 (i.MX53/6 compatible)

Mode:                 DCD

Secure Boot Mode:     ON

CSF Data Address:     1784a000

U-Boot Data Size:     332800 Bytes = 325.00 kB = 0.32 MB

U-Boot Load Address:  177fac00

U-Boot Entry Point:   17800000

arm-linux-objcopy -O srec u-boot u-boot.srec


But actually the sizes are different


-rw-r--r--   1 ds ds 120K Jun 20 08:38

-rwxr-xr-x   1 ds ds 1.6M Jun 20 08:38 u-boot

-rw-r--r--   1 ds ds 294K Jun 20 08:38 u-boot.bin

-rw-r--r--   1 ds ds 4.9K Jun 20 08:38 imxcfg.imx

-rw-r--r--   1 ds ds 314K Jun 20 08:38 u-boot.imx

-rw-r--r--   1 ds ds 881K Jun 20 08:38 u-boot.srec

-rw-r--r--   1 ds ds  44K Jun 20 08:38

-rw-r--r--   1 ds ds   56 Jun 20 08:38


The authenticate data of the CSF file is as follows:


Verification index = 2

Blocks = 0x17800000 0x000 0x4A000 "u-boot.imx"


I think the first parameter is the load address on the RAM which is 17800000. The second is the offset which I checked and the IVT starts from 0x0, i.e.n there is no offset. And the third parameter is length of the image which is obviously the 1784A000-17800000=4A000. The last one is the unsigned image location.


In spite of taking care, my signed image is not working. Can anyone guide me or identify the mistake I have made?