I am currently trying my best to compare a filesystem with TensorRT to one without TensorRT for the Nvidia Tx2
My purpose in doing this is to try to get TensorRT onto a Yocto Linux filesystem, by comparing the filesystem with and without TensorRT I’m hoping to drop in the TensorRT components.
I’m doing this by creating a directory that contains all the contents of a TensorRT filesystem (including all the proper symlinks, etc.) and one that has a full filesystem but does not contain TensorRT.
My current method is:
Run Jetpack 3.3 JetPack-L4T-3.3-linux-x64_b39.run with all packages installed. Then run
sudo ./flash.sh --no-flash jetson-tx2 mmcblk0p1
sudo ./apply_binaries.sh -r /media/user/ec2ba5f0-8539-4a0b-bcdf-1ac661eefcf3
sudo cp -arv /media/user/ec2ba5f0-8539-4a0b-bcdf-1ac661eefcf3 /media/user/08c63454-0ee5-4dac-acd1-68c4734fbccc/with_TensorRT
Remove all Nvidia files and rerun JetPack-L4T-3.3-linux-x64_b39.run without installing TensorRT and Multimedia API Package. Run the same flashing process, this time pointing to a without_TensorRT directory.
sudo ./flash.sh --no-flash jetson-tx2 mmcblk0p1
sudo ./apply_binaries.sh -r /media/user/ec2ba5f0-8539-4a0b-bcdf-1ac661eefcf3
sudo cp -arv /media/user/ec2ba5f0-8539-4a0b-bcdf-1ac661eefcf3 /media/user/08c63454-0ee5-4dac-acd1-68c4734fbccc/without_TensorRT
Perhaps worth noting is that the apply_binaries script produces a linking error as part of its output:
failed to create symbolic link ‘/media/user/ec2ba5f0-8539-4a0b-bcdf-1ac661eefcf3/lib/modules/4.4.38-tegra/build’: File exists
That may or may not be useful information.
Will this approach give me a representative filesystem that I can compare and use to inform my Yocto build, or am I missing something?
Will a similar approach still work if I switch to JetPack 4.0?
What additional information can I provide to add information/make this easier to answer?