Why does tegrastats show only NVJPG0 on DRIVE AGX Thor?

Autonomous Vehicles DRIVE AGX Thor DRIVE AGX Thor General
1

Software Version
DRIVE OS 7.0.3
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Thor Developer Kit (940-63960-0010-000)
DRIVE AGX Thor Developer Kit (940-63960-0012-000)
other

Host Machine Version
native Ubuntu Linux 24.04 Host installed with DRIVE OS Docker Containers
other

Issue Description:
We are using DRIVE AGX Thor with DRIVE OS 7.0.3. Our understanding is that DRIVE Thor has two JPEG encoder instances. However, sudo tegrastats --readall reports only NVJPG0:

09-15-2026 21:22:28 RAM 17785/60085MB (lfb 11x4MB) CPU [0%@2599,0%@2600,0%@2599,0%@2600,0%@2599,0%@2600,0%@2599,0%@2600,0%@2600,0%@2599,0%@2599,0%@2600,0%@2599,0%@2601] EMC_FREQ @4266 GR3D_FREQ 0%@[1574,1574,1574] NVENC0 0%@1565 NVENC1 0%@1565 NVDEC0 0%@1565 NVDEC1 0%@1565 NVJPG0 0%@1565 VIC 0%@999 OFA 0%@1565 PVA0_FREQ [0%,0%]@1098 APE 300 cpu@41.843C tj@41.843C soc012@41.531C gpu@41.343C soc345@41.5C

Could you please clarify the following?

  1. Does DRIVE AGX Thor have two independent JPEG encoder instances?

  2. If so, why does tegrastats display only NVJPG0 rather than both NVJPG0 and NVJPG1?

  3. Do JPEG encoding and decoding share the same NVJPG hardware engine? If not, why does tegrastats not report separate encoder and decoder instances, similar to NVENC0/1 and NVDEC0/1?

  4. Is this a known limitation or bug in DRIVE OS 7.0.3? Does DRIVE OS 7.2.5 expose both JPEG encoder instances in tegrastats?

3

I notice same output in DOS 7.2.5 as well. Let me check internally on this.

4

Dear @yungchen.sun.802 ,
It is a bug with tegrastats tool. There are 2 NVJPG engines.

5

Good catch on checking the output across DRIVE OS versions, that helped me narrow the issue down.