Driver installation failed for Arducam B0223 on Jetson Xavier NX L4T 35.3.1

Nvidia Jetson Cameras
1

Hi everyone. I’m trying to set up an Arducam B0223 on a Jetson Xavier NX Development Kit running L4T 35.3.1. I followed the Jetvariety Camera Quick Start Guide (Quick Start Guide - Arducam Wiki), but the driver installation keeps failing. I’ve attached the output log (output_error.txt) from the failed install. Has anyone run into this on 35.3.1?

2

Quick update: I also tested a B0429 camera and it looks like it relies on the same driver, so now I’m stuck on both cameras. Still waiting for any solution for the L4T 35.3.1 driver install failure. Any pointers would be appreciated.

3

Thanks for the log and details. We’re looking into the driver install failure on L4T 35.3.1. To help narrow this down, could you post photos of your Jetson Xavier NX, front and back, so we can check the board and how the camera is connected?

4

Here are photos of the board (front and back). A bit more info: on L4T 32.7.1 the driver installs without any problems and both cameras (B0223 and B0429) open fine, but I still need this working on 35.3.1. Separately, with the B0429 I can only get grayscale output. v4l2-ctl --list-formats-ext reports index 0 = Y16 and index 1 = BA10 (10-bit Bayer GRGR/BGBG). These two GStreamer pipelines work, but both produce grayscale:

gst-launch-1.0 v4l2src device=/dev/video0 ! ‘video/x-raw, width=1280, height=720’ ! videoconvert ! xvimagesink

gst-launch-1.0 v4l2src device=/dev/video0 ! ‘video/x-raw, format=GRAY16_LE, width=1280, height=720’ ! videoconvert ! xvimagesink

Does the grayscale output mean I need to convert to RGB somehow? And how do I capture BA10 and convert it to RGB?

5

Thanks for the photos. From what I can see, the board appears to be a third-party carrier board, not the official Nvidia carrier board. The Jetvariety camera driver isn’t compatible with third-party carrier boards, so unfortunately we can’t support the L4T 35.3.1 install on this hardware. Using the official Nvidia carrier board is the way to get Jetvariety driver support on 35.3.1.

As for the color image: BA10 is raw Bayer data, so you need to debayer it to get an RGB image. You can capture the BA10 frame with:

v4l2-ctl --device /dev/video0 --set-fmt-video=width=1280,height=720,pixelformat=‘BA10’ --stream-mmap --stream-to=frame.raw --stream-count=1

Then debayer the frame.raw output to RGB. The pipelines you’re currently using are effectively giving you the raw/grayscale data, which is expected for those formats.