@shcho1
What is the output of the execution of the command below at the Host PC?
df -h
Did you try uninstalling the installation made with sdkmanager, the sdkmanager, also removing downloaded folders and reinstalling it again? Did you try using other versions than DP_4.4? Did you try headless sdkmanager e.g. as in the example below?
Did you try uninstalling the installation made with sdkmanager, the sdkmanager, also removing downloaded folders and reinstalling it again?
→ Yes. First, I uninstalled the JP use sdkmanager and delete the downloaded folder.
Second, uninstall the sdkmanager.
Lsatly, I installed the sdkmanager and JP4.3 again. But it still not work.
Did you try using other versions than DP_4.4?
->Yes, I tried to install the JP 4.3. But it was failed.
Did you try headless sdkmanager e.g. as in the example below?
→ Yes, I tried to use headless sdkmanager.
But It stopped during installation.
is the df -h
showing the state after you got the headless sdkmanager or before it?
61 Gb available is a corner state which would work, if you run the headless install.
On the other hand if you previously run GUI sdkmanager it could cause shrink of the space up to 30Gb which wouldn’t be redundant for running the latter.
Could you :
once again make sure you are having at least 50gb;
run the headless sdk install
you may also try DP_4.4 instead of 3.3 Jetpack
Could you always post the uart log during flash when we are dealing with flash problem?
To be honest, I don’t like to see sdkmanager when we are debugging. Though I understand sdkmanager is a NV official tool, it has too many unrelated stuff and logs which we don’t need to check.
In my own point of view, I always use flash.sh and dump uart log to debug such problem.
