Hi, I am trying to use the blob enc / blob dec command available in the U-Boot source code provided by NXP on my i.MX6Q module. However, I obtain the follownig output:
=> mw.b 14000000 0 16
=> md.b 14000000 16
14000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
14000010: 00 00 00 00 00 00 ......
=> blob enc $loadaddr 0x12001000 32 0x14000000
Encapsulating data to form blob
b080000a
4000010
14000000
f0400000
12000000
32
f8400000
12001000
62
870d0000
0
0
0
0
Error in Encapsulation -3
=>
Could you explain why this error happens? Could you provide an example of this command usage which should work?
Thanks
Hi jdepedro
what uboot version is used in the case, nxp uboot-imx ?
For enabling uboot security functions one can look at configurations
descibed in
uboot-imx.git - Freescale i.MX u-boot Tree
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi igorpadykov,
thanks for your quick answer!
Yes, I am using the last NXP U-Boot release based on v2015.04 for i.MX6Q. I have enabled all the configuration options that you said:
CONFIG_SECURE_BOOT
CONFIG_SYS_FSL_SEC_COMPAT 4 /* HAB version */
CONFIG_FSL_CAAM
CONFIG_CMD_DEKBLOB
CONFIG_SYS_FSL_LE
and also
CONFIG_CMD_BLOB
which is needed in order to enable the blob command.
Could you confirm whether the usage example that I give is correct, and whether there is any error in the job descriptor which appears written? Thanks
Edit: by the way, just in case it helps to discard other problems, I have been successful using signed and signed + encrypted U-Boot images.
I have the same problem, have you found a solution?
Thanks
Generate Blob Under Linux
https://community.nxp.com/docs/DOC-335353
I used this guide with success with a linux kernel 3.15, now I upgraded to 4.1.15, and when it's enabled "Freescale CAAM-Multicore driver backend", the kernel has no errors, but at runtime it doesn't start, it freeze after a while. There are known issue on such a problem?
I had a similar problem and it was some register access during caam probe. Moving some clock enabling solve it for me.
Actually we verify on the 4.1.15. Please make sure you are using NXP official BSP.
If you are not using NXP reference, please check the system desgin including software and hardware. CMA size maybe need to be changed for your hardware.
BTW, NXP never release BSP with Linux kernel 3.15.
Hi jdepedro
please create service request for providing additional
documentation for this case.
Best regards
igor