-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OP-TEE 4.1.0 fails to boot on zynqmp(ZCU102) #6631
Comments
Hi friend,
You may use The |
thank you for your reply. After processing, the output is as follows:
I will try this configuration. |
Yes it should be it. You may also run |
Thank you very much jforissier!It works. |
Good! Then you must have a variant of the ZCU102 board that does not support Cryptographic Extensions. |
Sorry for my two cents: I think runtime detection might be better option to handle such cases (this info can be obtained from I'll experiment with that during the weekend :) |
@jforissier hm, I've just checked, so either sw implementation or implementation that uses crypto extensions are compiled it, not both (I guess because of size constraints); so switching in runtime is not an option, as I thought before. Maybe just a check of CPU capabilities, and if CE are not listed in |
Correct, but we could also have a CFG option to include both implementations and select the best at runtime. Perhaps easier said than done.
That would at least be a bit more user-friendly, yes :) |
Add runtime check for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for Crypto Extensions if CFG_CRYPTO_WITH_CE=y. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Link: OP-TEE#6631 Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Reviewed-by: Jerome Forissier <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Reviewed-by: Jerome Forissier <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Reviewed-by: Jerome Forissier <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: OP-TEE#6631 Acked-by: Etienne Carriere <[email protected]> Reviewed-by: Jerome Forissier <[email protected]> Acked-by: Jens Wiklander <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
Add runtime check during boot for supported ARMv8 Crypto Extensions. Core will panic if configuration enables an ARMv8 CE feature that the hardware does not support. Link: #6631 Acked-by: Etienne Carriere <[email protected]> Reviewed-by: Jerome Forissier <[email protected]> Acked-by: Jens Wiklander <[email protected]> Signed-off-by: Igor Opaniuk <[email protected]>
I am compiling OPTEE, my compilation command is as follows:
After the compilation is over, get the following 2 files in Zynqmp/Directory:
BOOT.bin zynqmp-zcu102.ub
Then I replaced the corresponding files in 2021.1-zcu102-release.tar.xz with the above two files, then copied it to the SD card, and finally use the SD card to boot ZCU102.
Got the following error:
It seems that it got crash when"
crypto_rng_init() -> key_from_data() -> hash_final() -> crypto_hash_final() -> sha256_done()
call chains is executed.This code is located in OPTEE OS.what's wrong with it?
The text was updated successfully, but these errors were encountered: