u-boot bootm vs booti signed and unsigned question

[jmandawg]

Hi all,

 

I can't find any documentation (i prob just don't know where to look), so just a quick question:

 

I have a Mi Box S, and i can run Armbian fine on it, it uses "booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}" to load the kernel images, i'm assuming they are all unsigned.  

But i would also like to run unsigned app images (openElec/emuElec/etc) which use "bootm <kernel_addr>" but those return an error:

 

aml log : Sig Check 1467

 

So my question is are you guys doing any "magic" to get it to load, or does "booti" not do a signature check where as "bootm" does?

 

Thanks.