IMX477 connect on custom NANO board

Hello,

I have custom carrier board NANO.
I am trying to mount an IMX477 on the board.
L4T is 32.5.
An error is displayed when the following command is executed.

nvidia@linux:~$ gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! 'video/x-raw(memory:NVMM), width=(int)4056, height=(int)3040, framerate=15/1' ! nvvidconv flip-method=0 ! 'video/x-raw, format=(string)I420' ! nvoverlaysink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 4032 x 3040 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 22.250000; Exposure Range min 11000, max 500000000;

GST_ARGUS: 1920 x 1080 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 22.250000; Exposure Range min 11000, max 500000000;

GST_ARGUS: Running with following settings:
   Camera index = 0 
   Camera mode  = 0 
   Output Stream W = 4032 H = 3040 
   seconds to Run    = 0 
   Frame Rate = 29.999999 
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
nvbuf_utils: Can not get HW buffer from FD... Exiting...
ERROR: from element /GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0: CANCELLED
Additional debug info:
Argus Error Status
Execution ended after 0:00:04.120661421
Setting pipeline to PAUSED ...
Setting pipeline to READY ...

(gst-launch-1.0:15980): GStreamer-CRITICAL **: 05:41:14.982: gst_mini_object_set_qdata: assertion 'object != NULL' failed
GST_ARGUS: Cleaning up
(Argus) Error EndOfFile: Unexpected error in reading socket (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 266)
(Argus) Error EndOfFile: Receive worker failure, notifying 1 waiting threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 340)
(Argus) Error InvalidState: Argus client is exiting with 1 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 357)
(Argus) Error EndOfFile: Receiving thread terminated with error (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadWrapper(), line 368)
(Argus) Error EndOfFile: Client thread received an error from socket (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 145)
(Argus) Error EndOfFile:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 87)
Setting pipeline to NULL ...
Freeing pipeline ...
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 96)
(Argus) Error InvalidState:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 87)
nvidia@linux:~$ 

There is also a large number of kernel error messages.

[   68.530994] host1x 50000000.host1x: cdma_handle_timeout: timeout: 34 (54080000.vi_1) client 10, HW thresh 0, done 1
[   68.541499] host1x 50000000.host1x: cdma_handle_timeout: timeout: 38 (54080000.vi_4) client 10, HW thresh 0, done 1
[   68.566986] host1x 50000000.host1x: cdma_handle_timeout: timeout: 35 (54080000.vi_2) client 10, HW thresh 2, done 2

error.log (111.5 KB)

IMX477 and I2C communication is normal.
Is there any way to debug it? (HW/SW)
help is appreciated.

Did you remove the rR8 resistor on RPi HQ camera module?

Thank you for answer.

I have two types of boards.
A. NANO devkit board
B. NANO custom board

If IMX477 is connected to A, it works normally. However, when connected to B, the above error occurs.
(NANO EMMC modules are common.)

Your answer is the camera module of the IMX477.
Is there any case to change the resistance of the board?

Due to you have a working base to compare to figure it out.

I’ll look for it

Thanks.

@young

How did you solve it, please?

Couldn’t solve it.
And the sensor was replaced.