[U-Boot] u-boot.dtb is not generated when enabling verified boot

[Davis Roman <davis.roman84@gmail.com>]

Okay. I found my first mistake. I would help if I could spell properly!

Turns out it was:
#define CONFIG_OF_SEPARATE
and not
#define CONFIG_OF_SEPERATE

but now I'm getting an error:

  LD      test/dm/built-in.o
  CC      examples/standalone/stubs.o
  LD      examples/standalone/libstubs.o
  CC      examples/standalone/hello_world.o
  LD      examples/standalone/hello_world
  OBJCOPY examples/standalone/hello_world.srec
  OBJCOPY examples/standalone/hello_world.bin
  LDS     u-boot.lds
  LD      u-boot
  OBJCOPY u-boot-nodtb.bin

Device Tree Source is not correctly specified.
Please define 'CONFIG_DEFAULT_DEVICE_TREE'
or build with 'DEVICE_TREE=<device_tree>' argument

dts/Makefile:27: recipe for target 'arch/arm/dts/unset.dtb' failed
make[1]: *** [arch/arm/dts/unset.dtb] Error 1
Makefile:820: recipe for target 'dts/dt.dtb' failed
make: *** [dts/dt.dtb] Error 2



Do I need to provide a dts file? I got the impression that this wasn't
the case from the docs.

Thank you,

Davis

On Fri, Apr 20, 2018 at 8:00 PM, Davis Roman <davis.roman84@gmail.com> wrote:
> Hello,
>
> I'm trying to get verified-boot working using u-boot 2016.03 on an imx6.
>
> So far I've managed to figure out that I need the following additional
> config settings:
>  #define CONFIG_DM
> #define CONFIG_ENABLE_VBOOT
> #define CONFIG_RSA
> #define CONFIG_FIT
> #define CONFIG_OF_CONTROL
> #define CONFIG_FIT_SIGNATURE
> #define CONFIG_OF_SEPERATE
> #define CONFIG_OF_LIBFDT
> #define CONFIG_FIT_VERBOSE
>
> However, no matter what I do I can't seem to generate u-boot.dtb.
>
> My understanding is that u-boot automatically generates this
> u-boot.dtb for the purpose of storing
> the public key when mkimage signs the fitimage and that this process
> does not require that I provide a dts file.
>
> However, below are the files that are generated with my current
> configuration and no u-boot.dtb file is generated.
>
> Additionally, since u-boot produces a u-boot-nodtb.bin, I figured it
> was reasonable to believe that u-boot.bin contained the device tree
> however as shown below both u-boot-nodtb.bin and u-boot.bin have an
> idential hash.
>
> Is there something that I'm missing here? Any advice would be greatly
> appreciated
>
> Thank you,
>
> Davis
>
> davis at XPS-15-9560:~/Desktop/u-boot-work/uboot-imx$ ls -l *u-boot*
> -rwxrwxr-x 1 davis davis 3413272 Apr 20 23:41 u-boot
> -rwxrwxr-x 1 davis davis  506052 Apr 20 23:37 u-boot.bin
> -rw-rw-r-- 1 davis davis   39490 Apr 20 23:27 u-boot.cfg
> -rw-rw-r-- 1 davis davis  510976 Apr 20 23:37 u-boot.imx
> -rw-rw-r-- 1 davis davis    1286 Apr 20 23:37 u-boot.lds
> -rw-rw-r-- 1 davis davis  456812 Apr 20 23:41 u-boot.map
> -rwxrwxr-x 1 davis davis  506052 Apr 20 23:37 u-boot-nodtb.bin
> -rwxrwxr-x 1 davis davis 1518250 Apr 20 23:37 u-boot.srec
> -rw-rw-r-- 1 davis davis  119239 Apr 20 23:37 u-boot.sym
> davis at XPS-15-9560:~/Desktop/u-boot-work/uboot-imx$
> davis at XPS-15-9560:~/Desktop/u-boot-work/uboot-imx$ sha1sum  *u-boot*
> cf00f776da67d1081fdfb8578ce71d0a63f16c48  u-boot
> 1fa17e1e90b51fc0dce73cf3f88d03cad0664a6f  u-boot.bin
> 1d2ad68da6c9aa7915f8684c53b6c532a07d7c7b  u-boot.cfg
> 599cec8e768eebf313d6735951c02c1271475f72  u-boot.imx
> 97054bccafd82b873a0af24f8e012ff032809b29  u-boot.lds
> 547e4e8cd4e46b5f9755aee4906a5f84906e2331  u-boot.map
> 1fa17e1e90b51fc0dce73cf3f88d03cad0664a6f  u-boot-nodtb.bin
> bb5aaaa839b8f23c6c8d952e65f99efac695ae91  u-boot.srec
> 5f933891f3939802ab92c4d642af16973b60af37  u-boot.sym
> davis at XPS-15-9560:~/Desktop/u-boot-work/uboot-imx$