Flashing_log.txt (60.9 KB)
Hi all,
I have flashed the nvidia xavier nx devkit using below command.
sudo ./flash.sh -r jetson-xavier-nx-devkit mmcblk1p1
After this command the flashing done successfully but the devkit was not started properly. Also i have connected with monitor but nothing is displayed.
I have tried to access board using micro-usb with static IP but also micro usb was not detected.
During booting the board is stuck at here.
:58:30:763] Jetson UEFI firmware (version r34.1-975eef6 built on 2022-04-06T11:46:12-07:00)␍␊
[12:58:30:763] Press ESCAPE for boot options ** WARNING: Test Key is used. **␍␊
[12:58:31:739] ......␊
[12:58:42:370] EFI stub: Booting Linux Kernel...␍␊
[12:58:42:386] EFI stub: Using DTB from configuration table␍␊
[12:58:42:403] EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path␍␊
[12:58:42:434] EFI stub: Exiting boot services and installing virtual address map...␍␊
[12:58:42:707] <0xff><0xe4>I/TC: Secondary CPU 1 initializing␍␊
[12:58:42:707] I/TC: Secondary CPU 1 switching to normal world boot␍␊
[12:58:42:739] I/TC: Secondary CPU 2 initializing␍␊
[12:58:42:739] I/TC: Secondary CPU 2 switching to normal world boot␍␊
[12:58:42:755] I/TC: Secondary CPU 3 initializing␍␊
[12:58:42:771] I/TC: Secondary CPU 3 switching to normal world boot␍␊
[12:58:42:787] I/TC: Secondary CPU 4 initializing␍␊
[12:58:42:803] I/TC: Secondary CPU 4 switching to normal world boot␍␊
[12:58:42:819] I/TC: Secondary CPU 5 initializing␍␊
[12:58:42:835] I/TC: Secondary CPU 5 switching to normal world boot␍␊
[12:58:44:242] <0xff><0xe2>WARNING: clock_get_rate: clk_power_ungate on gated domain 27 for gpcclk␍␊
[12:58:44:338] rm_rail_debugfs_init: /rm/vdd_cpu: failed␍␊
[12:58:44:359] rm_rail_debugfs_init: /rm/vdd_cpu: failed␍␊
[12:58:44:359] debugfs initialized␍␊
[12:58:44:934] <0xff><0xe5>[ 25.425690] Camera-FW on t194-rce-safe started␍␊
[12:58:44:934] TCU early console enabled.␍␊
[12:58:44:982] [ 25.491700] Camera-FW on t194-rce-safe ready SHA1=e4231a10 (crt 0.758 ms, total boot 66.798 ms)␍␊
Please find attached logs for the reference. Let us know if anyone have idea about the issue.
Console_log.txt (66.4 KB)
Hi,
Have you just tried the basic case : flashed by using the sdkm?
Yes i have tried multiple times using SDKM. But not able to flash using it. Flashing got stuck after 41.38%.
Here is the errors logs of SDKM.
11:54:07 SUMMARY: Drivers for Jetson - target_image: Install completed successfully.
11:54:38 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:54:38 ERROR: TensorRT on Target - target: Checksum verification error
11:54:57 ERROR: TensorRT on Target - target: Checksum verification error
11:54:57 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:54:57 ERROR: TensorRT on Target - target: Checksum verification error
11:54:57 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:54:57 ERROR: TensorRT on Target - target: Checksum verification error
11:55:04 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:04 ERROR: TensorRT on Target - target: Checksum verification error
11:55:10 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:10 ERROR: TensorRT on Target - target: Checksum verification error
11:55:11 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:11 ERROR: TensorRT on Target - target: Checksum verification error
11:55:15 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:15 ERROR: TensorRT on Target - target: Checksum verification error
11:55:15 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:15 ERROR: TensorRT on Target - target: Checksum verification error
11:55:19 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:19 ERROR: TensorRT on Target - target: Checksum verification error
11:55:20 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:20 ERROR: TensorRT on Target - target: Checksum verification error
11:55:23 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:23 ERROR: TensorRT on Target - target: Checksum verification error
11:55:29 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:29 ERROR: TensorRT on Target - target: Checksum verification error
11:55:33 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:33 ERROR: TensorRT on Target - target: Checksum verification error
11:55:38 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:38 ERROR: TensorRT on Target - target: Checksum verification error
11:55:42 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:55:42 ERROR: TensorRT on Target - target: Checksum verification error
11:56:41 ERROR: TensorRT on Target - target: Checksum verification error
11:56:41 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:56:41 ERROR: TensorRT on Target - target: Checksum verification error
11:56:41 ERROR: TensorRT on Target - target: Download 'TensorRT on Target' failure
11:56:41 ERROR: TensorRT on Target - target: Checksum verification error
12:19:46 SUMMARY: File System and OS - target_image: Install completed successfully.
12:19:47 ERROR: CUDA on Host - host: sudo: sorry, you are not allowed to preserve the environment
12:19:54 ERROR: CUDA on Host - host: sudo: sorry, you are not allowed to preserve the environment
12:19:54 ERROR: CUDA on Host - host: command terminated with error
12:19:54 SUMMARY: CUDA on Host - host: First Error: Failed to install debian repository file [host]
12:19:54 SUMMARY: CUDA Cross Compile Package on Host - host: Depends on failed component
12:19:55 SUMMARY: VPI on Host - host: Depends on failed component
12:19:56 ERROR: NVIDIA Nsight Graphics - host: sudo: sorry, you are not allowed to preserve the environment
12:19:57 ERROR: NVIDIA Nsight Graphics - host: command terminated with error
12:19:57 SUMMARY: NVIDIA Nsight Graphics - host: Failed to query debian packages details [host]
12:19:58 ERROR: NVIDIA Nsight Systems - host: sudo: sorry, you are not allowed to preserve the environment
12:19:58 ERROR: NVIDIA Nsight Systems - host: command terminated with error
12:19:58 SUMMARY: NVIDIA Nsight Systems - host: Failed to query debian packages details [host]
12:27:15 ERROR: Can not find matching device in recovery mode.
12:27:37 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py:2598: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:27:37 ERROR: Flash Jetson Xavier NX - flash: while count is not 0 and not check_ismb2():
12:27:37 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py:2607: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:27:37 ERROR: Flash Jetson Xavier NX - flash: while count is not 0:
12:27:37 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:858: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:27:37 ERROR: Flash Jetson Xavier NX - flash: while count is not 0 and not self.check_is_mb2applet():
12:27:37 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:865: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:27:37 ERROR: Flash Jetson Xavier NX - flash: while count is not 0:
12:27:53 ERROR: Flash Jetson Xavier NX - flash: 36137 blocks
12:27:53 ERROR: Flash Jetson Xavier NX - flash: gzip: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
12:28:02 ERROR: Flash Jetson Xavier NX - flash: 52382 blocks
12:28:04 ERROR: Flash Jetson Xavier NX - flash: 20+0 records in
12:28:04 ERROR: Flash Jetson Xavier NX - flash: 20+0 records out
12:28:04 ERROR: Flash Jetson Xavier NX - flash: 20 bytes copied, 0.000593486 s, 33.7 kB/s
12:28:06 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py:2598: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:28:06 ERROR: Flash Jetson Xavier NX - flash: while count is not 0 and not check_ismb2():
12:28:06 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py:2607: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:28:06 ERROR: Flash Jetson Xavier NX - flash: while count is not 0:
12:28:06 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:858: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:28:06 ERROR: Flash Jetson Xavier NX - flash: while count is not 0 and not self.check_is_mb2applet():
12:28:06 ERROR: Flash Jetson Xavier NX - flash: /home/abhishek.lakhara/nvidia/nvidia_sdk/JetPack_5.0_DP_Linux_DP_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:865: SyntaxWarning: "is not" with a literal. Did you mean "!="?
12:28:06 ERROR: Flash Jetson Xavier NX - flash: while count is not 0:
/home/abhishek.lakhara/Downloads/nvidia/sdkm_downloads
Also find the attached image.
Hi,
Your log looks like a mess and does not look like a complete log. Could you just pause the flash process and export the full log?
Also, as my previous comment said, could you just use rel-32.x/jeptack4.x release to flash the board at this moment?
Also, is this your first time flashing any jetson with your host machine + sdkmanager? If you are a total newbie in this setup, then we need to confirm whether this host can really flash board or not.
Please find attached logs.SDKM_logs_2022-06-13_12-56-44.zip (124.7 KB)
How long does jetpack5.0 DP take in this step?
Sync’ing system.img … done.
Converting RAW image to Sparse image…
I don’t see any other error from your exported log and these two lines are indeed taking most of time before the flash start.
I got below message multiple time. Flashing was stuck at 41.58% more than 2 hours multiple times.
Hi,
I don’t really care about that “41.58%”. What I want to know is if it is always stuck in below.
Sync’ing system.img … done.
Converting RAW image to Sparse image…
Could you also flash with jetpack4.x and see if you still stuck in same place?
yes it is always stuck here.
I will try with jetpack 4.x and let you know.
Hi,
I have tried to install jetpack 4.x using sdkmanagaer.
Now board is able to boot but installation is failed. But not able to install jetpack components.
SDKM_logs_2022-06-16_15-43-22.zip (378.3 KB)
Please check above image and logs and let me know how can i install jetpack components.
Also i have tried to install jetpack using below command but not able to installed it.
sudo apt install nvidia-jetpack
The picture you posted does not match to what you said. Which one is correct?
Picture says flash jetson OS fails. But you say the board is able to boot. These two conflict.
Hi,
Board is able to boot and i am able to access it using ssh.
But the jetson SDK component not installed. Like tensorrt, cude etc.
So you’ve flashed the board correctly?
I think yes because previously board is not able to boot but now it is booted and i can access it too.
You can check logs if you get any idea.
Ok, can you select just the SDK and run sdkmanager again and dump log? I mean do not select Jetson OS anymore. We don’t need to flash OS again.
Also, please tell me which version you are using now. Because the log you shared included every jetpack version you had tried.
We need to follow same steps to install SDK component right?
I am using jetpack 4.5.
There is a click icon in the GUI which you can select to flash OS or install SDK. We only need to check the “install SDK” for now.