Tegra Linux Driver Package Release Notes R32.1
Tegra Linux Driver Package Release Notes R32.1
Table of Contents
The NVIDIA® Tegra® Linux Driver Package (L4T) 32.1 release supports development on the
NVIDIA® Jetson Nano™, Jetson AGX Xavier™, and Jetson™ TX2/TX2i Developer Kit.
This release is intended for use with NVIDIA NVIDIA Jetson Nano, Jetson AGX Xavier, and
Note: Jetson TX2/TX2i. NVIDIA does not provide support for this release on other products that
are not listed above.
Sample rootfs derived from Ubuntu operating system to Ubuntu 18.04 (arm64 distribution)
run on Jetson devices.
The board/module name, used in flashing and paths in Jetson AGX Xavier: jetson-xavier
the software.
Jetson TX2: jetson-tx2
Jetson TX2i: jetson-tx2i
Jetson Nano: p3448-000 or
jetson-nano-qspi-sd
This section provides details about issues discovered during development and QA but not
resolved in this release.
Issue Description
2515130, On Jetson Nano, depending on the SD card speed, user may observe slow loading of
258714 certain applications such as a generic file editor and image viewer.
2524344, Jetson Nano currently does not implement power-based throttling. The system may
200498151 shut down if adapter power capacity is exceeded. This will not happen if the system
is used with a validated power adapter that provides adequate power.
2496962 Low-latency audio decode requires customer to set memory and CPU speeds
accordingly.
2521704 On Jetson Nano, when a GPIO is released (e.g. using the sysfs unexport file, the
cleanup() function in the Jetson.GPIO Python module, or the gpio_free()
function in the Linux kernel), the kernel configures the pin as a special function
(SFIO) rather than as a GPIO input. In some cases, this causes Jetson to drive a signal
onto the pin. If another device is also connected to that pin, and is also driving a
signal, this causes an electrical conflict, which may damage the hardware.
This issue is particularly relevant for the pins on the 40-pin GPIO expansion header.
200431304 On Jetson AGX Xavier, user cannot ping the IP address 0.0.0.0.
200488963 Nano /dev/root device size is restricted to 14 GB when using flash.sh to write to
an SD card. User cannot create additional partitions on the root device, so any
excess space is unavailable.
Issue Description
200497890 USB device mode network feature always reports that it is active, even when the USB
cable is not plugged in. This causes Jetson's graphical interface to claim that a
network connection is active at all times.
200498221 On Jetson Nano, when connecting to both HDMI and DP displays at bootup, login
screen may only be visible on HDMI. Once logged in, the NVIDIA logo appears only on
DP and is not centered, leaving the HDMI display blank.
200499128 On Jetson TX2, OSidle power consumption is comparatively higher than in public
release 28.3.
2.2 Boot
The following boot related issues are noted in this release.
Issue Description
2510850 For Jetson AGX Xavier, Secureboot with PKC keys works only if flashing follows
immediately after signing. This is due to missing files located inside a temp
directory that is cleared if the two actions are not performed back-to-back. To work
around the problem, apply the patches described in “Failure in Secureboot with PKC
Keys.”
200471553 On Jetson AGX Xavier, changing boot device order requires reflash. The user cannot
change boot order from the command line.
200480903 On Jetson-Xavier, UFS card fails to automount on boot. User can mount UFS devices
manually or through the GUI. This was tested with ext4 and vfat formats.
200492423 On all Jetson platforms, using the new OEM configuration, a minor glitch is observed
during EULA screen presentation at first boot.
2.3 Camera
The following camera related issues are noted in this release.
Issue Description
200407802 On Jetson TX2 and Jetson AGX Xavier using the six-camera module (E3333), memory
leakage occurs in the nvargus daemon.
200459897 On Jetson AGX Xavier, blur and corruption in the form of a vertical black stripe of
pixels at one side of the image are observed with an SLVS-EC sensor.
200461442 On Jetson AGX Xavier, the Multimedia API front end sample application exhibits a
low frame rate when using the IMX185. This is a regression due to VIC frequency
dependency.
Issue Description
200476911 On Jetson AGX Xavier, users cannot use specific cameras that support the “wait until
trigger” mechanism. This mechanism is intended to trigger the sensor using an
external signal to capture a specified number of frames, then stop streaming until
triggered again.
200490050 On Jetson Nano, hardware de-noise functionality, denosiestrength, has less impact
than expected.
200490661 On TX2, the IMX390 dual sensor camera fails to capture simultaneously with both
sensors when running two separate applications to capture from CSI/GMSL.
Simultaneous capture from a single application is successful.
Issue Description
200500995 If the system date and time are not set correctly after boot, be sure the configured
NTP server is accessible from your network.
2.5 Multimedia
The following multimedia related issues are noted in this release.
Issue Description
2517881 L4T currently does not support hardware acceleration for VLC Player. To work
around this issue, enter this command to run VLC Player with software decoding:
vlc --codec=avcodec <filename>
200297610 If the user launches an argus camera with Piecewise Linear WDR sensor mode
enabled and changes the AWB mode from Auto to another setting (Incandescent,
Fluorescent, etc.), then changes AWB mode back to Auto, preview hangs.
This is a corner case and is not handled in this release.
200427796 The new gst-v4l2 decoder has an issue with 10/12-bit HEVC decode. Blueish video
observed due to interchanged U and V planes getting read for 8-bit transform. This
type of decode works correctly with the legacy OMX-based decoder.
200489184 When using DRM for display, display modes using YUV format are not supported, and
are not properly filtered out by the DRM subsystem. To avoid this issue, select RGB
modes only, or use X11, which filters out YUV modes correctly.
200490095 On Jetson Nano, raw capture at 4K resolutions using an IMX219 camera exhibits
corruption. Capture at 4K resolutions using Argus (“cooked” instead of raw) is
functional.
Issue Description
200502065 GST pipeline using camera capture with scaling/color conversion may affect
performance. NVIDIA recommends setting the nvarguscamerasrc property
maxperf=1 for better performance. For more details, see the “Camera Capture”
section of Accelerated GStreamer User Guide.
200502136 nvgstcapture-1.0 has an image encoding issue using the nvjpegenc plugin for
default YUY2 video capture format for a USB camera.
To work around the issue, use the OSS jpegenc plugin instead of nvgstcapture-
1.0 for image encoding with a USB camera. To do this, add the command line switch
--image-enc=0 to the nvgstcapture-1.0 capture command, for example:
nvgstcapture-1.0 --camsrc=0 --image-enc=0
200454955 Kernel PWM fan driver overrides fan setting applied by jetson_clocks.sh.
3.2 Camera
Camera related resolved issues are as follows:
This section describes errors in documentation that were discovered too late to be corrected.
kernel/nvidia/Documentation/devicetree/bindings/pci/nvidia,tegra19x-
pcie.txt
With this:
$(KERNEL_TOP)/Documentation/devicetree/bindings/pci/nvidia,tegra19x-
pcie.txt
In the paragraph that begins “The sample source files are available…” change the pathname
from $HOME/graphics_demos to /usr/src/hvidia/graphics_demos.
In the paragraph that begins “The sample applications may be built…” change the
pathname from $HOME/graphics_demos/README to
/usr/src/hvidia/graphics_demos/README.
After the paragraph that begins “L4T also provides…” change the pathname from:
$HOME/graphics_demos/bin
To:
/usr/src/hvidia/graphics_demos/prebuilts/bin
After the paragraph that begins “For example, to run…” change the command:
$ cd /home/nvidia/graphics_demos/prebuilts/bin/<graphics>
To:
$ cd /usr/src/nvidia/graphics_demos/prebuilts/bin/<graphics>
To:
Wayland
Delete the paragraph that begins “Before you can run Wayland graphics sample
applications…”
Before you can run the Wayland graphics sample applications, you must first stop
the X server (which is running by default) and then launch Weston either by running
the Weston binary (/usr/bin/weston) from the root user or by running the
Weston-launch binary (/ usr /bin/ weston -launch).
To ensure portability of code across product generations, the interfaces for specification of
the NVIDIA Video Decoder instance are deprecated in this release.
Linux for Tegra installs a boot-time initialization script /etc/init/nv.conf, that corrects
typical occurrences, such as with OpenGL, EGL, and X11 GLX libraries. This script runs at
boot and corrects typical occurrences.
To workaround
Reboot after installation of packages that install conflicting library symlinks.
For DP, Bootloader display polls for at most 1 msec. by default when trying to detect
whether HPD has been asserted by the sink. Different Type-C downstream devices
connected to the Type-C ports on Jetson AGX Xavier (cables, adapters, hubs, etc) may incur
different amounts of latency before they trigger the handshake process needed to drive DP
over Type-C.
Workaround: If a seamless display does not come up with the Type-C device you are using,
try increasing the HPD_TIMEOUT_MS value in tegrabl_display_dtb.c. We
recommend increasing the timeout value in 500 msec. increments. Increasing the timeout
value guarantees interoperability with a larger variety of devices, but also increases the boot
time.
After the bug is fixed, an updated GLVND package will be available for Ubuntu 18.04
(Bionic). After the update is applied, libGLESv1_CM.so will be available and OpenGLES
1.1 support will work as expected without requiring any changes to the BSP.
The product is based on a published Khronos specification. It has been submitted to, and is
expected to pass, the Khronos Conformance Process. Current conformance status can be
found at http://www.khronos.org/conformance.
The CTS test version used to run conformance for each of the APIs is:
OpenGL-ES: 3.2.5.0
OpenGL: 4.6.0.0
Vulkan: 1.1.1.2
Invoke Visual Profiler with the -vm command line option included:
The -vm option is only required if JRE is not included in CUDA Toolkit package and JRE 1.8
is not in the default path.
On Jetson AGX Xavier, the EMC frequency for CPU workload is decided by the static CPU-
EMC mapping table and the mc_all activity monitor (actmon) driver. The CPU-EMC
mapping table decides base minimum EMC frequency based on CPU frequency. The mc_all
actmon is responsible for scaling EMC frequency from the base minimum to a higher value
proportional to memory bandwidth utilization.
In this release the CPU-EMC mapping table is tuned, that is, the EMC base frequency
mapped to CPU frequency has been reduced to optimize power consumption. The tuned
CPU-EMC table does not affect performance of the GPU, NVDEC, and NVENC workloads,
as each has its own EMC scaling algorithm, but it may affect CPU workload performance,
especially when CPU load is high and bandwidth utilization is low. If any such performance
drop is observed, the CPU-EMC mapping table can be tuned in this location, based on
performance/power requirements:
<source>/hardware/nvidia/soc/t19x/kernel-dts/tegra194-soc/tegra194-soc-
base.dtsi
Patch 1:
--- a/bootloader/tegraflash_internal.py
+++ b/bootloader/tegraflash_internal.py
@@ -3184,7 +3184,8 @@ def tegraflash_generate_mem_bct(is_cold_boot_mb1_bct):
tegrabct_values['--membct_rcm'] = tegraflash_oem_encrypt_and_sign_file('mem_rcm.bct' ,True, 'MEMB')
tegrabct_values['--membct_rcm'] = tegraflash_oem_encrypt_and_sign_file(tegrabct_values['--membct_rcm'] ,False, 'MEMB')
else:
- tegrabct_values['--membct_rcm'] = tegraflas_oem_sign_file(mem_bcts[ramcode], 'MEMB')
+ shutil.copyfile(mem_bcts[ramcode], 'mem_rcm.bct')
+ tegrabct_values['--membct_rcm'] = tegraflas_oem_sign_file('mem_rcm.bct', 'MEMB')
def tegraflash_generate_mb1_bct(is_cold_boot_mb1_bct):
if bool(is_cold_boot_mb1_bct) == True:
Patch 2:
--- a/bootloader/odmsign.func
+++ b/bootloader/odmsign.func
@@ -714,6 +714,7 @@ odmsign_sbk_and_pkc_flashing ()
BCTARGS+="--mb1_cold_boot_bct mb1_cold_boot_bct_MB1.bct_sigheader.encrypt.signed ";
else
BCTARGS="--mb1_bct mb1_bct_MB1_sigheader.bct.signed ";
+ BCTARGS+="--mem_bct mem_rcm_sigheader.bct.signed ";
BCTARGS+="--mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.signed ";
fi;
BCTARGS+="--mem_bct_cold_boot mem_coldboot_sigheader.bct.signed ";
NVIDIA recommends using the gst-v4l2 plugin for development instead. See the
Accelerated GStreamer User Guide for usage information.
Known Issues
The following general system usability related issues are noted in this release.
Issue Description
2419317 Performance drop due to EMC frequency not set correctly for CPU workload. (See
EMC the Implementation Note Frequency Adjustment for CPU Workload.)
200461808 When connecting the Intel IGB PCIE card, CPU errors may occur during system idle.
200464272 System may fail to enter SC7 state when certain PCIe Network Interface Cards are
connected. (Issue was seen with two different NICs, neither of which uses the igb
driver). This issue is under investigation.
Camera
Issue Description
200297610 Preview freeze with WDR mode when AWB lock is set and user attempts to change
AWB mode to Auto.
200455493 Defog feature of argus_camera app is not supported in this release. The following
options of argus_camera app do not work:
--defog=ENABLE
--defogamount=AMOUNT
--defogquality=QUALITY
200455200 argus_userautoexposure app failed to run the sample in DOL WDR modes.
CUDA Samples
The following CUDA samples related issues are noted in this release.
Issue Description
200448615 Argus CUDA samples crash or hang for CPHY sensor IMX318, possibly due to very high
resolution of the sensor. If the resolution is set to less than 4K in EGL stream
settings, the sample passes successfully.
Multimedia
Issue Description
200387512 gstreamer based video playback using Wayland not working when Weston is started
as an NVIDIA user.
200454955 Kernel PWM fan driver overrides fan setting applied by jetson_clocks.sh.
Camera
Known Issues
The following general system usability related issues are noted in this release.
Issue Description
2183567 Type-C devices unable to drive DP due to length of delay before handshake begins.
Workaround: see Type-C Devices Unable to Drive DisplayPort.
200441525 An application to be debugged NVIDIA Developer Tools (CUDA tools, NVIDIA Nsight
Systems/Graphics) must be run as the root user, or with root permissions.
200442461 VisionWorks SFM sample fails to run; shows black image when launching
nvx_sample_sfm sample.
200447045 SC7 system suspend/resume may have intermittent resume failures in this release.
Boot
Issue Description
2305640 CBoot bootloader cannot access USB mass storage devices connected via a USB hub.
Camera
Issue Description
2258817 Incorrect ISP settings may be applied if camera module is replaced with a module
that does not support a unique identifier (fuse ID). (Workaround: manually remove
the cached .bin files in /var/nvidia/nvcam/settings.)
2199266 Temporal noise reduction may cause a slight green tint to images.
200407738 Greenish tint on displayed preview image when running the sample software
argus_userautowhitebalance.
CUDA
Issue Description
200431121 If a CUDA application calls malloc() within a CUDA kernel (device-side malloc)
while running concurrently with another CUDA or GPU-accelerated graphics
application, the application may fail.
Display
Issue Description
2284878 Cannot operate GeChic 1101 display connected through USB-C to USB-A when aut-
search mode is enabled.
200404683 Display Port (DP) monitors do not show a bootloader splash screen at boot, and may
require a hotplug after boot to display content properly.
200434425 Display driver may produce “Failed to write DPCD data” errors after a display
hotplug with certain monitors including Dell U2413 and Dell U2713.
JetPack Installer
The following JetPack Installer related issues are noted in this release.
Issue Description
2340186 After installation of CUDA 10.0 host packages, the apt package management system
may produce "Failed to fetch" messages due to the addition of the arm64
architecture to the apt package repository configuration.
Kernel
Issue Description
200443630 Hotplugging a UFS card may cause the Linux kernel to report a CPU SError.
200399574 Using USB devices that are not fully compatible with the USB Gen2 specification may
cause kernel error messages like “tegra-xusb 3610000.xhci: Cannot set link state.”
2211831 UART serial console using USB to TTL serial cable does not work.
Trademarks
NVIDIA and the NVIDIA logo, CUDA, Jetson, AGX Xavier, Nano, Tegra, and VisionWorks are trademarks or
registered trademarks of NVIDIA Corporation in the United States and other countries. Other company and
product names may be trademarks of the respective companies with which they are associated.
HDMI, the HDMI logo, and High-Definition Multimedia Interface are trademarks or registered trademarks of
HDMI Licensing LLC.
ARM, AMBA, and ARM Powered are registered trademarks of ARM Limited. Cortex, MPCore and Mali are
trademarks of ARM Limited. All other brands or product names are the property of their respective holders.
"ARM" is used to represent ARM Holdings plc; its operating company ARM Limited; and the regional subsidiaries
ARM Inc.; ARM KK; ARM Korea Limited.; ARM Taiwan Limited; ARM France SAS; ARM Consulting (Shanghai) Co.
Ltd.; ARM Germany GmbH; ARM Embedded Technologies Pvt. Ltd.; ARM Norway, AS and ARM Sweden AB.
Copyright
© 2018-2019 NVIDIA Corporation. All rights reserved.
www.nvidia.com