Hello,
I am stuck at setting up the OP-TEE on the Jetson AGX Orin.
I am following the instructions of atf_and_optee_README.txt. Now I arrived at the following section:
“Building the ATF Source Code with OP-TEE SPD
To build all source tarballs, including the atf_src.tbz2, run the nv_public_src_build.sh script.”
When I execute the nv_public_src_build.sh script, I get the following error:
~/jetson-public-srcs/Linux_for_Tegra/source$ ./nv_public_src_build.sh
nvbuild.sh not found for package ./opencv_gst_samples_src.tbz2
Skipping ./opencv_gst_samples_src.tbz2 build.
nvbuild.sh not found for package ./kernel_oot_modules_src.tbz2
Skipping ./kernel_oot_modules_src.tbz2 build.
nvbuild.sh not found for package ./argus_cam_libavencoder_src.tbz2
Skipping ./argus_cam_libavencoder_src.tbz2 build.
nvbuild.sh not found for package ./nvsci_samples_src.tbz2
Skipping ./nvsci_samples_src.tbz2 build.
nvbuild.sh not found for package ./nvsample_cudaprocess_src.tbz2
Skipping ./nvsample_cudaprocess_src.tbz2 build.
nvbuild.sh not found for package ./gstegl_src.tbz2
Skipping ./gstegl_src.tbz2 build.
nvbuild.sh not found for package ./gstjpeg_src.tbz2
Skipping ./gstjpeg_src.tbz2 build.
nvbuild.sh not found for package ./nvidia-jetson-optee-source.tbz2
Skipping ./nvidia-jetson-optee-source.tbz2 build.
nvbuild.sh not found for package ./gst-nvvidconv_src.tbz2
Skipping ./gst-nvvidconv_src.tbz2 build.
nvbuild.sh not found for package ./libgstnvcustomhelper_src.tbz2
Skipping ./libgstnvcustomhelper_src.tbz2 build.
nvbuild.sh not found for package ./gst-nvv4l2camera_src.tbz2
Skipping ./gst-nvv4l2camera_src.tbz2 build.
-rwxr-xr-x buildbrain/dip 7812 2023-11-30 19:27 nvbuild.sh
mkdir: cannot create directory ‘/home/andi/jetson-public-srcs/Linux_for_Tegra/source/nv_public_src_build.sh’: Not a directory
Can somebody help me and explain me, where is my mistake?
From the best of my knowledge, I did the previous steps correctly. I followed the guideline of the .txt file.
As far as I know this step is necessary, because I need it to flash the TEE correctly on the system.
I already tried it without that step and executed the gen_tos_part_img.py script without --monitor, but then when I flash it to the Orin it doesn’t boot anymore.
Hi KevinFFF,
I am using the devkit AGX Orin and Jetpack Version 6.0.
My problem is, that from my understanding the script nv_public_src_build.sh searches in the tar files for the nvbuild.sh script, but it is not found.
if tar -tvf "${src_file}" | grep "nvbuild.sh" ;
Does that mean I have to unpack all the tar files, then add the script from the kernel sources that I found following you linked page and then pack it again?
This sounds wrong to me…
Edit: I just made some changes, will get back to you when I am done. Thank you so far for the help!
I have skipped the part of the script nv_public_src_build.sh and instead just unpacked the atf_src.tbz2 file and adjusted the paths for the monitor etc to point to the generated files for the gen_tos_part_img.py script. When I executed it, it generated an .img file which I took and replaced in the folder ~/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader as described in the atf_and_optee_README.txt. Then I did sudo ./flash.sh jetson-agx-orin-devkit internal but and the end of the output afterwards is:
[ 778.3363 ] [................................................] 100%
[ 781.3749 ] Flashing completed
[ 781.3750 ] Coldbooting the device
[ 781.3763 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 781.3773 ] MB2 version 01.00.0000
[ 781.3790 ] Coldbooting the device
[ 781.3800 ] tegrarcm_v2 --chip 0x23 0 --reboot coldboot
[ 781.3809 ] MB2 version 01.00.0000
*** The target generic has been flashed successfully. ***
Reset the board to boot from internal eMMC.
I turned the AGX Orin off using the Power Button, turned it back on but the screen connected to it stays black, it seems like nothing happens.
Am I missing something?
The only point missing in the description would be 3. Copy all the files under ./optee/install/t<platform> to the target.
But shouldn’t it be able to boot without that or at least do any response? I can hear from the sound the device does that something is running but nothing is shown.