It dont show connected info if I dont use Factory Recovery mode, is this normal?
So I tried install both.
And this is my host ubuntu
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal
Linux ubuntu 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
It dont show connected info if I dont use Factory Recovery mode, is this normal?
SDKM only detects the board when it is either boot into linux or it is in recovery mode.
After I run jetson orin ubuntu os, I connect orin to my host ubuntu but nothing happened.
Only if i enter Factory Recovery mode it shows usb connected
Honestly, what you are asking does not matter.
Please share me what did you see under your
/home/colin/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/kernel/
apply_binaries.sh jetson-agx-xavier-devkit.conf l4t_sign_image.sh p2972-0000-devkit-maxn.conf p3737-0000+p3701-0000-as-p3767-0000.conf
bootloader jetson-agx-xavier-ind-noecc.conf nvautoflash.sh p2972-0000-devkit-slvs-ec.conf p3737-0000+p3701-0000-as-p3767-0010.conf
build_l4t_bup.sh jetson-agx-xavier-industrial.conf nvmassflashgen.sh p2972.conf p3737-0000+p3701-0000.conf
clara-agx-xavier-devkit.conf jetson-xavier.conf nvsdkmanager_flash.sh p3449-0000+p3668-0000-qspi-sd.conf p3737-0000+p3701-0000-maxn.conf
e3900-0000+p2888-0004-b00.conf jetson-xavier-maxn.conf nv_tegra p3449-0000+p3668-0001-qspi-emmc.conf README_Autoflash.txt
flash.sh jetson-xavier-nx-devkit.conf nv_tools p3509-0000+p3668-0000-qspi.conf README_Massflash.txt
jetson-agx-orin-devkit-as-jao-40w.conf jetson-xavier-nx-devkit-emmc.conf p2822-0000+p2888-0001.conf p3509-0000+p3668-0000-qspi-sd.conf rootfs
jetson-agx-orin-devkit-as-nx-16gb.conf jetson-xavier-nx-devkit-qspi.conf p2822-0000+p2888-0004.conf p3509-0000+p3668-0001-qspi-emmc.conf source
jetson-agx-orin-devkit-as-nx-8gb.conf jetson-xavier-slvs-ec.conf p2822-0000+p2888-0008.conf p3668.conf.common source_sync.sh
jetson-agx-orin-devkit.conf kernel p2822-0000+p2888-0008-noecc.conf p3701.conf.common tools
jetson-agx-orin-devkit-maxn.conf l4t_generate_soc_bup.sh p2972-0000.conf.common p3737-0000+p3701-0000-as-p3701-0004.conf
This is not the path I want to check.
Sorry.
dtb kernel_display_supplements.tbz2 LICENSE.dtc nvidia-l4t-kernel_5.10.65-tegra-34.1.0-20220406120854_arm64.deb
dtc kernel_headers.tbz2 LICENSE.nvethernetrm nvidia-l4t-kernel-dtbs_5.10.65-tegra-34.1.0-20220406120854_arm64.deb
Image kernel_supplements.tbz2 nv-enable-hard-coded-kernel-boot-display-mode.sh nvidia-l4t-kernel-headers_5.10.65-tegra-34.1.0-20220406120854_arm64.deb
Image.gz LICENSE nvidia-l4t-display-kernel_5.10.65-tegra-34.1.0-20220406120854_arm64.deb pinmux
Could you use sdkmagner GUI to uninstall these whole folder and let it download again?
Please use the timestamp of the file to tell/make sure this file is actually re-downloaded by sdkmanager.
I mean “Image”.
What do you mean use sdkmanager to uninstall?
Can I delete the folders just with “rm” command?
Hi @EzPizzy ,
Please check what is printing out from this command on your host, Linux_for_Tegra folder.
strings kernel/Image |grep “Linux version”
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
