-
Notifications
You must be signed in to change notification settings - Fork 59
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
hello_world failed after upgrading to optee_os 3.8 for compiling rust TAs #21
Comments
Thanks for the report. I'm not sure the root cause in your case. I can see from the log showing that the TA has been crated and the session opened successfully.
To help you debug this issue, the problem should be in invoking command in the secure world. Maybe there're some differences for the invoking command API in the newer version. |
Hi @mssun , Thanks for the reply! I dug in recently, and I think this is because the optee changes the TA entry point since a73b5878c8. They removed the TA entry point from Thanks, |
Hi @mssun , I've fixed the entry pointer problem. I have to add a few linking arguments and change the linker script according to Thanks, |
Sure, I'm happy to take any PR. Thanks. |
I believe this PR can be also closed because of recent PR about OPTEE update. |
Hi,
Thanks for the great work! If I understand correctly, the optee used in the skd is 3.4, but we are supposed to test the TAs under
optee 3.8
as the instructions specifies. However, after I replaced the optee withoptee 3.8
(copied and pasted fromoptee-qemuv8-3.8.0
), I got atranslation fault
when I test the TA.We are developing a board adopting
optee 3.8
. It will be really helpful if you can give us any advice on how to move fromoptee_os 3.4
to3.8
so that we can use your scheme.PS: If I compile TAs with
optee_os 3.4
and test TAs withoptee 3.8
, it works well.Thanks,
Mingyuan
The error looks like following:
The text was updated successfully, but these errors were encountered: