Orin NX 16G frequency locking failed

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

hardware: DevelopKit/Custom board

software version: JetPack5.1.3/JetPack5.1.5

Unable to lock frequency during Orin NX stress testing.

Here is my test command:

sudo nvpmodel -m 0
sudo jetson_clocks
stress-ng --cpu $(nproc) --cpu-method matrixprod --cpu-load  95 &
stress-ng --vm 6 --vm-bytes 500M --vm-method all &
./matrixMulCUBLAS --sizemult=8 &

The following is the Orin NX print after running for a few minutes:

01-01-1970 08:18:49 RAM 3047/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@266,100%@1984,100%@255,100%@882,100%@332,100%@1832,100%@816,100%@1984] EMC_FREQ 39%@3199 GR3D_FREQ 99%@[917,0] VIC_FREQ 729 APE 174 CV0@80.281C CPU@83.718C SOC2@80.281C SOC0@76.406C CV1@76.937C GPU@87.875C tj@87.875C SOC1@75.281C CV2@74.718C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13599mW/13752mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:50 RAM 3047/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@291,100%@1984,100%@257,100%@1619,100%@1578,100%@1984,100%@253,100%@1984] EMC_FREQ 39%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@80.375C CPU@83.75C SOC2@80.343C SOC0@76.468C CV1@77.062C GPU@87.625C tj@87.625C SOC1@75.218C CV2@74.75C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13593mW/13752mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:51 RAM 3046/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@273,100%@1860,100%@956,100%@1984,100%@1207,100%@1984,100%@1984,100%@449] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@80.281C CPU@83.937C SOC2@80.25C SOC0@76.343C CV1@77.125C GPU@87.656C tj@87.656C SOC1@75.218C CV2@74.875C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13750mW/13752mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:53 RAM 3044/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@1326,100%@1393,100%@2158,100%@250,100%@1026,100%@1984,100%@248,100%@1984] EMC_FREQ 39%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@80.312C CPU@83.656C SOC2@80.375C SOC0@76.343C CV1@76.968C GPU@87.687C tj@87.687C SOC1@75.25C CV2@74.656C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13599mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:54 RAM 3046/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@1078,100%@1984,100%@1984,100%@254,100%@1984,100%@1384,100%@1152,100%@254] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@80.281C CPU@83.906C SOC2@80.5C SOC0@76.343C CV1@76.906C GPU@87.718C tj@87.718C SOC1@75.375C CV2@74.781C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13599mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:55 RAM 3047/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@565,100%@1984,100%@1273,100%@724,100%@1984,100%@246,100%@1984,100%@299] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[917,0] VIC_FREQ 729 APE 174 CV0@79.937C CPU@83.718C SOC2@80.437C SOC0@76.312C CV1@76.875C GPU@87.656C tj@87.656C SOC1@75.343C CV2@74.687C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13744mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:56 RAM 3049/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@279,100%@481,100%@612,100%@1984,100%@1003,100%@328,100%@1984,100%@448] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[917,0] VIC_FREQ 729 APE 174 CV0@80.062C CPU@83.718C SOC2@80.375C SOC0@76.468C CV1@76.968C GPU@87.593C tj@87.593C SOC1@75.281C CV2@74.812C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13744mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:57 RAM 3046/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@733,100%@348,100%@1984,100%@252,100%@1984,100%@256,100%@1984,100%@745] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[917,0] VIC_FREQ 729 APE 174 CV0@80.531C CPU@83.812C SOC2@80.468C SOC0@76.343C CV1@77.031C GPU@87.656C tj@87.656C SOC1@75.281C CV2@74.843C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13750mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:58 RAM 3047/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@1984,100%@333,100%@1984,100%@259,100%@1984,100%@259,100%@1984,100%@257] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@80.125C CPU@83.75C SOC2@80.437C SOC0@76.343C CV1@77.093C GPU@87.75C tj@87.75C SOC1@75.281C CV2@74.781C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13599mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:18:59 RAM 3045/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@1984,100%@258,100%@1702,100%@358,100%@1861,100%@264,100%@1801,100%@907] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@79.906C CPU@83.75C SOC2@80.375C SOC0@76.375C CV1@76.875C GPU@87.843C tj@87.843C SOC1@75.375C CV2@74.625C VDD_IN 24489mW/24437mW VDD_CPU_GPU_CV 13750mW/13751mW VDD_SOC 4827mW/4805mW
01-01-1970 08:19:00 RAM 3047/15503MB (lfb 2799x4MB) SWAP 2/7752MB (cached 0MB) CPU [100%@615,100%@422,100%@270,100%@1984,100%@260,100%@1984,100%@1852,100%@1692] EMC_FREQ 38%@3199 GR3D_FREQ 99%@[918,0] VIC_FREQ 729 APE 174 CV0@80.187C CPU@83.687C SOC2@80.375C SOC0@76.437C CV1@76.843C GPU@87.656C tj@87.656C SOC1@75.437C CV2@74.781C VDD_IN 24489mW/24438mW VDD_CPU_GPU_CV 13750mW/13751mW VDD_SOC 4827mW/4805mW

I have encountered the problem of frequency locking failure when using the purchased development kit or my own designed hardware for testing.

orinnx
orinnx973×1599 120 KB

I tried to flash JetPack5.1.3 and JetPack5.1.5, but both experienced frequency locking failure.

Please help me find the reason for the failure of frequency locking. Thanks

4

Hi jack.yan,

Could you also verify with the latest Jetpack 6.1.2(r36.4.3) to verify if there’s the similar issue?

Please reboot the device after configuring the power mode.

5

Hi,KevinFFF:

Our algorithm engineers require the system version to be JetPack5.1.5, so testing JetPack6.1.2 is not very helpful for us. I need to solve the problem of JetPack5.1.5 frequency locking failure.

I have tested the restart method and still cannot lock the frequency successfully.