-
Notifications
You must be signed in to change notification settings - Fork 11
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
does build_scripts cover "tee-xxx.srec" #6
Comments
It probably can be done, but I have not tried. Most people use these scripts when porting BSP code to a new board doing some debugging. It is much easier to do that outside of Yocto. So in that case, you might not concerned about security features yet. That is the only reason why there is no build code for tee yet. |
Hi Chris,Thank you for your help. The build script is very helpful tool. Many thanks for your effort.BestJie
On Friday, November 17, 2023, 06:52:17 AM PST, Chris Brandt ***@***.***> wrote:
It probably can be done, but I have not tried. Most people use these scripts when porting BSP code to a new board doing some debugging. It is much easier to do that outside of Yocto. So in that case, you might not concerned about security features yet. That is the only reason why there is no build code for tee yet.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
RZ/G2L example, parameters may need to be adjusted: git clone https://github.com/renesas-rz/rzg_optee-os.git The patch and the lib (CFG_RZ_SCE_LIB_DIR) are in the security package. |
The build_scripts is very helpful tool. It looks like it does not cover "tee-xxx.srec". Is there any method to generate "tee-xxx.srec" outside of yocto build system?
The text was updated successfully, but these errors were encountered: