NvSIPLCamera Init failed

Dear nvidia support,

We recently had to unplug, move the nvidia Drive to another location, and plug again everything. It work for 1 day or two but now when it is impossible to get it started again. Between the last time it run ok and now there was no SW change on our side. I could also reproduce the issue while running the sample application below. The error is the same everytime. I tried to change the deserializer group and tried different camera quad port with different type of cameras and same issue everytime. Could the HW have been damaged ? what else could it be ? please find the logs below.

nvidia@tegra-ubuntu:~/drive-t186ref-linux.bak/samples/nvmedia/nvsipl/test/camera$ ./nvsipl_camera --platform-config “SF3325_DPHY_x4” --link-enable-masks “0x0000 0x0001 0x0000 0x0000” --disableISP1Output -f test
Client: Send or Recv Msg failed
Module_id 30 Severity 2 : src/devblk/fusa/cameramodule/common/utils/pwr_utils.cpp 369
Module_id 30 Severity 2 : nvccp_request_ownership failed with status 1001
Module_id 30 Severity 2 : src/devblk/nonfusa/devices/MAX96712DeserializerDriver/CNvMMax96712.cpp 566
Module_id 30 Severity 2 : MAX96712: CNvMMax96712::DoSetPower failed with SIPL error 127
Module_id 30 Severity 2 : src/devblk/common/ddi/DeserializerIF/CNvMDeserializer.cpp 42
Module_id 30 Severity 2 : CNvMDeserializer::SetPower failed with SIPL error 127
Module_id 30 Severity 2 : src/devblk/common/core/CNvMDeviceBlock.cpp 647
Module_id 30 Severity 2 : Deserializer SetPower failed with SIPL error 127
DEVBLK_WORKER_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMDeviceBlockMgr.cpp: 435: ThreadFunc: Device block init failed(7f)
Module_id 30 Severity 2 : src/core/CNvMDeviceBlockMgr.cpp 144
Module_id 30 Severity 2 : Device block action failed for block (action, block) 10
Module_id 30 Severity 2 : src/core/CNvMDeviceBlockMgr.cpp 180
Module_id 30 Severity 2 : Failed to initialize device blocks

Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 436: Init: DeviceBlock manager init failed
nvsipl_camera: ERROR: NvSIPLCamera Init failed

nvsipl_camera: ERROR: Master initialization failed. status: 127

Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/CNvMSensorPipeline.cpp: 705: Deinit: Deinit() call in wrong state
Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 994: DeinitPipelines: Pipeline deinit failed for pipeline:4
Module_id 30 Severity 2 : src/devblk/nonfusa/devices/MAX96712DeserializerDriver/cdi_max96712.c 3623
Module_id 30 Severity 2 : MAX96712: Null handle passed to MAX96712SetDefaults
Module_id 30 Severity 2 : src/devblk/nonfusa/devices/MAX96712DeserializerDriver/CNvMMax96712.cpp 237
Module_id 30 Severity 2 : MAX96712: CDI_CONFIG_MAX96712_DISABLE_REPLICATION failed with NvMedia error 1
Module_id 30 Severity 2 : src/devblk/common/ddi/CNvMDevice.cpp 131
Module_id 30 Severity 2 : Driver failed Deinit() call 1
Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 49: ~CNvMCamera: CNvMCamera object fails to deinit

Software Version
DRIVE OS Linux 5.2.6

Target Operating System
Linux

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)

SDK Manager Version
other (1.7.0.8846)

Host Machine Version
native Ubuntu 18.04

Dear @sebastien.venturi,
It looks like the Aurix is not able to communicate with camera. Could you check running aurixreset command on aurix console and see if it helps.

Dear SivaRamaKrishna,

Thnaks for your help. Unfortunately after running aurixreset and shutdown + hard power cycle the problem is still exactly the same. Any other suggestion ? Please find the logs of aurixreset below:

NvShell>aurixreset
Info: Executing cmd: aurixreset, argc: 0, args:
NvShell>INFO: PSM_ModMgr: Powering off
Stop task Nvptp_Task_88E6321_2
Stop task Nvptp_Task_88E6321_1
Stop Nvptp_Task_SJA1105Q
INFO: PSM_EthInit: Ethernet peripherals de-initialized
INFO: PSM_EthInit: Linkup status is not active
INFO: PSM_EthInit: Linkup status is not active
INFO: PSM_IoHwAbs: X1 shutdown notification triggered
INFO: PSM_IoHwAbs: X2 shutdown notification triggered
*************** NvShell Initialization Start******************
DRIVE-V5.2.6-E3550-AFW-Aurix-With3LSS-StepA-4.04.01
Compilation date: Apr 6 2021, 00:00:08
Enter ‘help’ to see the available commands.
*************** NvShell Initialized *************************
Press ‘Enter’ for NvShell prompt


INFO: PSM_ModMgr: Powering up
INFO: PSM_IoHwAbs: Power On sequence Triggered.
INFO: PSM_IoHwAbs: Waiting for Voltages to drop below safe margin of 80mV -
INFO: SftyMon_tmon: Temperature sensor initialized
INFO: PSM_PwrCtrl: Detect 2nd Harness is not connected.
INFO: PSM_PwrCtrl: If you are using DGPU, please contact your hardware INFO: PSM_PwrCtrl: representative to get 2nd harness cable
INFO: PSM_PwrCtrl: Configured BootStraps for X1 as QSPI
INFO: PSM_PwrCtrl: Configured BootStraps for X2 as QSPI
INFO: PSM_PwrCtrl: Tegra x1 Boot Chain: A
INFO: PSM_PwrCtrl: Tegra x2 Boot Chain: A
INFO: PSM_PwrCtrl: COM Exp card not detected
INFO: PSM_PwrCtrl: COM Exp card not detected
Init NXP
INFO: PSM_EthInit: Linkup status is not active
INFO: PSM_EthInit: Sja1105Q Link Active
Init Marvell
Init stbm
init_nxp_switch
Applying multicast address filter in Eth_Drv
Initial 88Q2112
Initial 88Q2112 A0 silicon slave address 01
Initial 88Q2112 A0 silicon slave address 02
Initial 88Q2112 A0 silicon slave address 03
Initial 88Q2112 A0 silicon slave address 04
Initial 88Q2112 A0 silicon slave address 05
Initial 88Q2112 A0 silicon slave address 06
Initial 88Q2112 A0 silicon slave address 07
88E6321_1 is in CPU mode
88E6321_2 is in CPU mode
Initial 88e6321_1
Enable 88E6321-1 VLAN
Initial 88e6321_1 port 1 in SGMII Mode.
Initial 88e6321_2
switch 2 DSA Only
Enable VLAN on 88Q5050 for OTA
Default 5050 init for VLAN
NvShell>

Dear @sebastien.venturi,
Do you see the same issue on another Tegra? Is it ok to reflash the target? This should confirm if it is HW/SW issue.

I guess we will have to find out. If I understand correctly you recommend applying all the steps described here ?https://docs.nvidia.com/drive/drive-os-5.2.6.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_NGC_Development_Guide/Flashing%20Basics/flashing_aurix.html#wwconnect_header

or only a subset ?

Dear @sebastien.venturi,
I recommend flashing the taget again using sdkmanager if possible.

Dear @sebastien.venturi,
Any update on the issue?

The procedure you recommended worked: actually the problem was with both AGX but after reflashing only one of them with sdkmanager and rebooting everything, then both worked again !
We are happy we could solve the issue but would really appreciate if you can share any idea of what could have caused the issue…

Dear @sebastien.venturi,
Glad to hear the issue is fixed. I suspect the issue was because of Aurix and Tegra communication and reinstallation fixed the SW issue.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.