we are heavily using your Mercury ZX5 boards with your bsd-xilinx (version 1.8.2) u-boot (V2018.01). If used with default Mercury config for QSPI boot (even with some minor modifications), it works well for us. Now, we would like to add cryptography capability and encrypt our bitstream. According to Xilinx documentation, we need for this zynqaes command which is enabled with u-boot CONFIG_CMD_ZYNQ_AES define. However, if we add this define and the others below to allow u-boot to compile, this u-boot binary hangs up during boot and we cannot even reach u-boot shell.
Hi all,
we are heavily using your Mercury ZX5 boards with your bsd-xilinx (version 1.8.2) u-boot (V2018.01). If used with default Mercury config for QSPI boot (even with some minor modifications), it works well for us. Now, we would like to add cryptography capability and encrypt our bitstream. According to Xilinx documentation, we need for this zynqaes command which is enabled with u-boot CONFIG_CMD_ZYNQ_AES define. However, if we add this define and the others below to allow u-boot to compile, this u-boot binary hangs up during boot and we cannot even reach u-boot shell.
CONFIG_SHA256=y CONFIG_CMD_MD5SUM=y CONFIG_CMD_ZYNQ_RSA=y CONFIG_CMD_ZYNQ_AES=y
The only message which appears on the UART port is:
Can you advice us what is wrong or how to debug this issue? Have you tried cryptography functions with this your u-boot fork?
Thank you in advance, Michael