Please execute the command to get information:
$ cat /etc/nv_tegra_release
# R35 (release), REVISION: 1.0, GCID: 31346300, BOARD: t186ref, EABI: aarch64, DATE: Thu Aug 25 18:41:45 UTC 2022
If you see R34, the release is developer preview, and please upgrade to at least >= r35.1
Please execute the command:
$ cat /etc/nv_boot_control.conf
And check the information:
[Orin developer kit]
[Orin 32GB module]
Please refer to this page: Jetson/General debug - eLinux.org
We have quick solutions for some known issues. Please check
Jetson/L4T - eLinux.org
A known issue for ubuntu 20.04 host is the USB autosuspend function is enabled on it by default. This leads to Jetson recovery mode gets suspended before flash. To bypass this error, need to:
- Disable autosuspend on host PC with below command:
echo -1 > /sys/module/usbcore/parameters/autosuspend
- Plug out the USB cable, put jetson back into recovery mode again and plug the usb cable back.
If USB timeout is still there after above commands, please file a topic to forum and let moderator help check.
Please download test-launch.c of 1.16.2:
gst-rtsp-server/examples/test-launch.c at 1.16.2 · GStreamer/gst-rtsp-server · GitHub
And refer to steps in Jetson Nano FAQ
A: Please refer to Jetson Nano FAQ
A: Please refer to Jetson Nano FAQ
nvoverlaysink is deprecated on Jetpack 5 releases. Please use nv3dsink, nveglglessink, or nvdrmvideosink.
Please refer to the UEFI source
edk2-nvidia/Platform/NVIDIA/NVIDIA.common.dsc.inc at main · NVIDIA/edk2-nvidia · GitHub
This 5 seconds is for user to interrupt and enter UEFI menu. It could be customized setting to 0 to disable.
Please rebuild the UEFI source with the link above. After you rebuild it, there would be a debug version of binary. Please replace the old “uefi_jetson.bin” file in your BSP folder and then reflash the board. It will enable full log in UEFI.
If you are syncing rel-35.2.1 and as below error. Then it is not fatal. Those files are not needed for Orin compilation. You could just ignore it.
→ Fatal: remote error: access denied or repository not exported: /device/hardware/nvidia/platform/t23x/prometheus-dts
Flashing over USBSS is not supported at present.
Yes, they are compatible, and some customer validated that.
The CVM power at SC7 is ~300mW. The CVM+CVB total power is close to 1.1W.
The Orignial default RTC source is set as RTC1 (Orin_RTC), which can not keep time if power off. So a patch to set default RTC to RTC0 (PSEQ_RTC) is needed.
Yes, the 10G ethernet PHY support P/N correction automatically. To make the trace smooth, we swap P and N.
MOD_TEMP_SHDN_EN_N is not used on commercial module. It is for Auto/industrial module to gate buffers of temp_therm and soc_pwr_req. Suggest to short to GND to keep the messaging consistent across all modules: floating = TEMP_THERM and SOC_PWR_REQ gated, GND= un-gated.
There is no explicit pin on Orin that indicates an internal SW reset has occurred. Internal SW reset does not propagate to the IO pin. One way to set an indicator is to use the internal watchdog timer and use WDT_RESET_OUTA (GP63) or WDT_RESET_OUTB (GP21) as the indicator. Both signals are available on the CVM connector.
Please refer to below post to modify necessary software change in device tree and pinmux.
$ cat /sys/devices/virtual/dmi/id/bios_version
$ cat /sys/devices/virtual/dmi/id/bios_date
The GPU, CV power rails might be turned off at idle by run time power management. The temperature cannot be read from GPU, CV thermal sensors when the power is off. Attempts to read a sensor with the power off will return error code -256000.
Please reference detail steps from: Problem installing Intel d435 camera - #5 by carolyuu
Please go to the page: https://developer.nvidia.com/embedded/jetson-linux-r3521
Please note it can be used for either Jetpack 5 version, not specific to r35.2.1
Please refer to this post
The example is for Orin Nano and applicable to AGX Orin, Orin NX. Please ensure correct device tree file is modified.
Please reference detail steps from: What is the best way to control the jetson Orin GUI remotely? - #5 by KevinFFF
please refer to this post
It’s an known issue, but it would not affect the functionality of UEFI.
Auto Boot Time-out means the timeout for waiting user’s interrupt to enter UEFI menu.
It may be caused from that you run reboot command before
nv-l4t-bootloader-config.service gets ready.
You could refer to https://forums.developer.nvidia.com/t/reset-timing-of-boot-retry-count/277168/7 for the logic of retry count.
For flashing eMMC/SD card with flash.sh, the default setting of WSL2 will work fine.
However, if you are trying to use initrd flash to flash NVMe/USB, please refer to the following post to re-build the Linux kernel with a customized kernel config, as the default kernel of WSL2 shipped by Microsoft lacks some functionalities that are required for initrd flash to work.
For rel-35, need to follow below post