MAX96712 GMSL decoding error

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Hi there,

We’re using SONY’s IMX390 with our Drive AGX and we have recently started seeing the following error when running our camera pipline using SIPL framework:

nvmedia: ERROR: MAX96712: Link 0: GMSL2 decoding error (1)
libnvsipl.so: CNvMCamera.cpp: 309: OnLinkError: DeviceBlock 0 encountered link errors. Link Mask:1

Do you have any information on what could cause this and how we can troubleshoot the issue?

Thanks,

B.

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version => 5.1.6.1-16902563
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.4.1.7402
other

Host Machine Version
native Ubuntu 18.04
other

2

Dear @bogdan0kg3v ,
Could you confirm if it is a customer DRIVE OS build?
Could you check with other camera module, fakra Coax Cable and Quad Camera Breakout Cable (which is working on another port) and try it on the port.

3

Hi Siva,

Thanks for a quick reply.

We are running a Dockerized environment on our Drive AGX units. This issue appears only on a single board and a single GMSL port.

We have tried out different camera module, fakra and quad breakout cable and we are still seeing the issue on the same port.

Any ideas on how we can get more debug info on what could be wrong?

Thanks again,

B.

4

Dear @bogdan0kg3v ,
This issue appears only on a single board and a single GMSL port

Does that mean, other ports in the board have no issue and other boards works with same setup?

5

Hi Siva,

Exactly. Everything is fine on the other ports and boards with the same setup. The whole setup was working properly with all the cameras, but at some point one of the cameras started failing with the error that I’ve shared.

Could it be that there a hardware issue with the board?

Thanks again for your help,

B.

6

Dear @bogdan0kg3v,
Did you use this board in car or office premises before this occurred? This is looking like a HW issue.

7

Hi Siva,

We are keeping this board in the vehicle. Any suggestion how we can confirm the HW issue?

Thanks,

B.

9

Dear @bogdan0kg3v,
Could you share the port, camera and used command to double check?

Any suggestion how we can confirm the HW issue?

As you said your Sony IMX390 camera is working on all other ports with the same quad cable on same target, could you check with other camera models like sekonix on the same port to confirm if it is HW issue(issue with port).
Please check the issue from both Tegras and share feedback.

Also, could you check Problem with xavier port B cameras - #10 by VickNV if it helps.

11

Hi Siva,

We have tried the following:

  1. We replaced the SONY IMX390 cameras with Sekonix, but the issue was still there when running the pipeline from Xavier A.
  2. We tried to run our pipeline from Xavier B and the issue was not present. All cameras were working fine.

Looking at above results, it looks like it’s HW issue. Please let us know on the next steps we could do to troubleshoot this problem.

Regarding the link that you shared from above, is that relevant given that all cameras are working on Xavier B?

Thank you,

B.

12

Dear @bogdan0kg3v ,
The issue is looking similar. Could you check the HW errata provided in the link and confirm.

13

Dear @bogdan0kg3v ,
We notice similar issue couple of month ago at Defect Nvidia Drive AGX . Is this a new issue? We did not hear any update on that thread.

14

Dear @bogdan0kg3v,
Could you check MAX96712 GMSL decoding error - #12 by SivaRamaKrishnaNV and confirm for further guidance

15

Hi Siva,

The team is looking into this atm. We will get back as soon as we have more info.

Thanks,

B.

16

Hi Siva,
I am a colleague. I was checking our DRIVE AGX at is has a “QC PASSED” right next to the serial number.

17

Hi Siva,

Any updates from your side? What would be the suggested next steps in troubleshooting this issue?

Thank you,

B.

18

Dear @bogdan0kg3v,
Could you share the complete logs.

19

Hi Siva,

Please find the logs from not-working (Xavier A) and working (Xavier B) camera stream:

Camera-Xavier-b.log (267.6 KB) Camera-Xavier-a.log (27.2 KB)

Thanks,

B.

20

Hi @SivaRamaKrishnaNV,

Any updates on your side on this one. Did the team have a chance to take a look into the logs? Thanks!

21

Hi @bogdan0kg3v ,

We are still checking with an internal team. Please also contact with your nvidia representative to get more attention on this. Thanks.

22

Dear @bogdan0kg3v ,
Could you check connecting four SF3324/25 cameras to that port and run nvmimg_cap sample with relevant configuration(SF33(24|25)-TRIO-(AB|CD|EF|GH ) set and share log

./nvmimg_cap -cf ddpx-a.conf -c SF33(24|25)-TRIO-XX -(AB|CD|EF|GH ) v 2 --aggregate 4