Someone from NVIDIA may need to give an answer since I don’t know about the internal workings of SDKM, but as a general theme, SDKM downloads content when the content is (A) missing, or (B) a version with a different checksum than needed is found. The metadata about that content is generally here:
Linux_for_Tegra/bootloader/tegraparser_v2 is actually part of the “driver package”, and if you were to recursively delete both the “
~/.nvsdkm” content and the particular “
Linux_for_Tegra/” content, then SDKM would download this again and start fresh.
If you do not flash, then I would expect much of that content to remain missing until you actually flash. You can expect that the version of
tegraparser_v2 would always be correct once put in place. I have not experienced this being deleted after a flash, but in cases where I’ve run SDKM without flashing that content will remain missing.
You could manually unpack the “driver package” and “sample root filesystem” (along with correctly using
sudo for the rootfs, then running the “
sudo ./apply_binaries.sh” command from “
Linux_for_Tegra/”), and this would also provide “
If you are somehow trying to mix and match incompatible releases, then beware that content from one release is likely incompatible with another release and behavior might be undefined. Should SDKM be installed using the “
.deb” package system, then I would expect this to not be a problem. If there is some sort of manual process for installing content, then it is possible you are running into some odd behavior.