We’re certainly not in Kansas anymore!
You will probably want to provide this information from both host and Jetson:
ifconfig
route
On some newer systems you might not have all of that, and might substitute (I prefer the old command formatting though):
ip -s addr
ip route
PS: I too am not in Kansas! I did pass through though.
On using the sdkmanager on an Orin Nano in auto mode INSTALLATION FAILED attached are the logs.
Oh … what to do?
Thanks
cg
SDKM_logs_JetPack_5.1.1_(rev._1)_Linux_for_Jetson_Orin_Nano_modules_2023-05-02_13-57-39.zip (88.4 KB)
What is the environment of this host machine? Is it a non-VM ubuntu host?
Also, are you trying to flash the sdcard case?
The log ends in a weird situation that no error got printed.
14:02:54.624 - Info: exec_command: /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.sh
sudo ./nvsdkmanager_flash.sh --storage mmcblk1p1 --nv-auto-config --username flash
user entered mmcblk1p1 --nv-auto-config --username flash
*** Checking ONLINE mode … OK.
*** Checking target board connection … 1 connections found.
*** Reading ECID … FUSELEVEL=fuselevel_production hwchipid=0x23 bootauth=NS
*** Reading EEPROM … “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py” --chip 0x23 --applet “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin” --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --bins “mb2_applet applet_t234.bin” --skipuid --cmd “dump eeprom cvm cvm.bin; reboot recovery”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0689 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0700 ] File rcm_state open failed
[ 0.0700 ] ERROR: failed to read rcm_state
[ 0.0700 ]
[ 0.0712 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0714 ] Assuming zero filled SBK key
[ 0.0704 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
So this is a bit strange. sdkmanager makes up a series of log files that contain bits and pieces of the events, however as far as I’m able to determine are not what I see within the terminal window of the sdkmanager.
If I capture a screen grab it does not contain the entire screen contents but only a small piece shown below
14:02:55 INFO: Flash Jetson Linux - flash: [ 0.0700 ] File rcm_state open failed
14:02:55 ERROR: Flash Jetson Linux - flash: [ 0.0700 ] ERROR: failed to read rcm_state
14:02:55 INFO: Flash Jetson Linux - flash: [ 0.0700 ]
14:02:55 INFO: Flash Jetson Linux - flash: [ 0.0712 ] tegrasign_v3.py --key None --getmode mode.txt
14:02:55 INFO: Flash Jetson Linux - flash: [ 0.0714 ] Assuming zero filled SBK key
14:02:55 INFO: Flash Jetson Linux - flash: [ 0.0704 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
14:02:55 ERROR: Flash Jetson Linux - flash: Traceback (most recent call last):
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py”, line 1383, in
14:02:55 ERROR: Flash Jetson Linux - flash: tegraflash_run_commands()
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py”, line 1217, in tegraflash_run_commands
14:02:55 ERROR: Flash Jetson Linux - flash: interpreter.onecmd(command)
14:02:55 ERROR: Flash Jetson Linux - flash: File “/usr/lib/python3.6/cmd.py”, line 217, in onecmd
14:02:55 ERROR: Flash Jetson Linux - flash: return func(arg)
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py”, line 855, in do_dump
14:02:55 ERROR: Flash Jetson Linux - flash: self.chip_inst.tegraflash_dump(exports, args)
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py”, line 2387, in tegraflash_dump
14:02:55 ERROR: Flash Jetson Linux - flash: self.tegraflash_preprocess_configs()
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py”, line 361, in tegraflash_preprocess_configs
14:02:55 ERROR: Flash Jetson Linux - flash: values[config])
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py”, line 3290, in run_dtc_tool
14:02:55 ERROR: Flash Jetson Linux - flash: run_command(command, False)
14:02:55 ERROR: Flash Jetson Linux - flash: File “/home/flash/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py”, line 277, in run_command
14:02:55 ERROR: Flash Jetson Linux - flash: process = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.STDOUT, shell=use_shell, env=cmd_environ)
14:02:55 ERROR: Flash Jetson Linux - flash: File “/usr/lib/python3.6/subprocess.py”, line 729, in init
14:02:55 ERROR: Flash Jetson Linux - flash: restore_signals, start_new_session)
14:02:55 ERROR: Flash Jetson Linux - flash: File “/usr/lib/python3.6/subprocess.py”, line 1364, in _execute_child
14:02:55 ERROR: Flash Jetson Linux - flash: raise child_exception_type(errno_num, err_msg, err_filename)
14:02:55 ERROR: Flash Jetson Linux - flash: FileNotFoundError: [Errno 2] No such file or directory: ‘dtc’: ‘dtc’
14:02:55 ERROR: Flash Jetson Linux - flash: — Error: Reading board information failed.
14:02:55 ERROR: Flash Jetson Linux - flash: *** ERROR: Parsing boardid failed
14:02:55 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
14:02:55 INFO: Flash Jetson Linux - flash: [host] [ 376.00 KB used. Disk Avail: 1169.35 GB ]
14:02:55 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 0s ]
14:02:55 ERROR: Flash Jetson Linux - flash: command terminated with error
14:02:55 SUMMARY: Flash Jetson Linux - flash: No such file or directory
14:02:55 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta) - target: Depends on failed component
14:02:55 SUMMARY: Multimedia API - target: Depends on failed component
14:02:55 SUMMARY: TensorRT on Target - target: Depends on failed component
14:02:55 SUMMARY: TensorRT Runtime - target: Depends on failed component
14:02:55 SUMMARY: VPI on Target - target: Depends on failed component
14:02:55 SUMMARY: VPI Runtime - target: Depends on failed component
14:02:55 SUMMARY: CUDA Toolkit for L4T - target: Depends on failed component
14:02:55 SUMMARY: CUDA Runtime - target: Depends on failed component
14:02:55 SUMMARY: cuDNN on Target - target: Depends on failed component
14:02:55 SUMMARY: CuDNN Runtime - target: Depends on failed component
14:02:55 SUMMARY: OpenCV - target: Depends on failed component
14:02:55 SUMMARY: OpenCV Runtime - target: Depends on failed component
14:02:55 SUMMARY: DeepStream - target: Depends on failed component
14:02:55 SUMMARY: DateTime Target Setup - target: Depends on failed component
My impression looking at the complete log is that the repositories that the sdkmanager relies upon are incomplete.
below is a “ERROR” filtered terminal output
14:00:25 ERROR: VPI on Host - host: E: The repository ‘https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease’ is not signed.
14:00:25 ERROR: VPI on Host - host: E: The repository ‘http://ppa.launchpad.net/george-edison55/cmake-3.x/ubuntu bionic Release’ does not have a Release file.
14:00:25 ERROR: VPI on Host - host: Error: safe apt install failed: sudo apt-get update , exit code: 100, retry number: 1
14:00:39 ERROR: VPI on Host - host: Err:5 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease
14:00:41 ERROR: VPI on Host - host: Err:33 http://ppa.launchpad.net/george-edison55/cmake-3.x/ubuntu bionic Release
14:00:42 ERROR: VPI on Host - host: Err:19 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease
14:00:50 ERROR: VPI on Host - host: W: GPG error: https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
14:00:50 ERROR: VPI on Host - host: E: The repository ‘https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease’ is no longer signed.
14:00:50 ERROR: VPI on Host - host: E: The repository ‘http://ppa.launchpad.net/george-edison55/cmake-3.x/ubuntu bionic Release’ does not have a Release file.
14:00:50 ERROR: VPI on Host - host: W: GPG error: https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 075721F6A224060A
14:00:50 ERROR: VPI on Host - host: E: The repository ‘https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease’ is not signed.
14:00:50 ERROR: VPI on Host - host: Error: safe apt install failed: sudo apt-get update , exit code: 100, retry number: 2
14:01:10 ERROR: VPI on Host - host: Err:3 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease
14:01:12 ERROR: VPI on Host - host: Err:18 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease
14:01:14 ERROR: VPI on Host - host: Err:36 http://ppa.launchpad.net/george-edison55/cmake-3.x/ubuntu bionic Release
14:01:20 ERROR: VPI on Host - host: W: GPG error: https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
14:01:20 ERROR: VPI on Host - host: E: The repository ‘https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease’ is no longer signed.
14:01:20 ERROR: VPI on Host - host: W: GPG
The host is a, long in the tooth, Ubuntu 16.04 box, “yes I know it needs an update to 22.04”.
I had selected the 256 GB memory M2 memory card as the target, although the sdkmanager seems to have it’s own mind about what gets its attention.
Is there any documentation that covers a manual method for adding all the goodies?
There must be a set of updates to the os that need to be performed. such as adding
iface eth0 inet dhcp
to /etc/network/interfaces
Do you have such a list of things to do?
It has been my experience with the Jetson Nano that it worked “out of the box” without much, if any, effort. This is certainly not the case with the Orin. Somebody dropped the ball and it is making a lot of unnecessary work for you support guys.
I can certainly understand that the view of a Linux purist might be, “toughen up, you’re playing with the big boys now”. However, I’ve been using linux for almost 30 years now since Slackware 0.98, so my expectations may be colored.
It’s obvious that the sdkmanager will eventually be a great tool, but it’s not there yet.
Regards,
cg
Regards,
Hi,
-
There is a “EXPORT LOGS” button on sdkmanager and you can use that to dump full logs. I think you already knew that because you sent me a zip file few days ago.
-
Actually sdkmanager does not support jp5 on ubuntu 16.04 anymore. As you can see this page,
→
So an upgrade is needed here.
-
I am actually a little confused. What happened to your Orin Nano device now? I mean… you said “This is certainly not the case with the Orin.”
But according to your previous log from serial console, your device is still able to login, which means it still able to boot. -
Actually, jetson nano and Orin nano all need the help of sdkmanager (to reflash) if system goes wrong.
If you totally no need the help from sdkmanager for jetson nano in the past few years, then you are really a lucky guy. We’ve help handled many forum topic regarding to flash no matter what platforms…
Howdy:
Well there is some good news as I’m running 18.04.
So, AFASIK the Orin is running. Well at least it seems normal from a desktop Linux perspective. I don’t believe that it has any of the Nvidia goodies.
I tried running “sudo unminimize”. No joy. Log file attached.
It seems my little Orin is really making it difficult at every turn.
Looking through some of the forum posts it seems that many prefer to use the command line to load the various tool sets. Am I mistaken?
“Not the case with the Orin” - I think I was referring to the fact that it is necessary to enable dhcp manually. That is a first. Never had to do that before on countless embedded Linux systems going back to the beginning some 30 years ago.
I really would like to see the sdkmanager running happily, however when I look at the logs it seems it frequently encounters missing libraries and gives up. It is especially frustrating to see the terminal log filled with errors but no apparent corresponding copy of the log in the zip files. If I try and do a screen capture I’m only able to copy a small portion of whats in the terminal window into a text file. What is the file name of the what’s in the terminal window? I took a look at every single log but did not find anything similar.
What do you suggest?
cg
unminimize.log (12.4 KB)
The attached file is a result of running sudo apt update.
A very clear example of the granite wall that not even a goat could climb.
cg
aptupdate.log (11 KB)
Hi,
I am really confused here. Sorry that I am not a native English speaker so I don’t quite understand some points here.
So, AFASIK the Orin is running. Well at least it seems normal from a desktop Linux perspective. I don’t believe that it has any of the Nvidia goodies.
- What is missing on your Orin? Could you directly tell me what do you need on your Orin and it didn’t happen there? apt-get update hits error?
Looking through some of the forum posts it seems that many prefer to use the command line to load the various tool sets. Am I mistaken?
-
If you are talking about “flash orin” requires a command. Then it is same as what sdkmanager is doing. Sdkm is just a GUI tool wrap up those commands into so that for someone who is new to jetson, they don’t need to directly run commands to flash. Even if you think sdkmanager is not good and you want to directly run the commands, those flash tools are downloaded by sdkmanager too.
-
What is the situation on sdkmanager after you run it in 18.04? If it fails again, do you have any log to provide?
Host should be Ubuntu 18.04 or 20.04; 22.04 will fail. You might be able to get away with command line flash on a 16.04 host PC, and definitely can use command line flash via a 22.04 host PC, but you’ll save yourself a lot of effort if you have an 18.04 or 20.04 host PC. If you have time and don’t mind that it might fail, you could attempt command line flash from 16.04 (I wouldn’t recommend it though).
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.