Staging Changes for IMX219 and Arducam FPDLink

boards/beagley/ai/04-expansion.rst

@@ -13,3 +13,4 @@ PCIe
 For software reference, you can see how PCIe is used on NVMe HATs.
 
 * :ref:`beagley-ai-expansion-nvme`
+* :ref:`imx219-csi-cameras`

boards/beagley/ai/05-demos.rst

@@ -8,4 +8,5 @@ Demos and tutorials
 
    demos/beagley-ai-expansion-nvme
    demos/pca9685-motor-drivers
+   demos/arducam-imx219-v3link-dual-camera-kit
 

boards/beagley/ai/demos/arducam-imx219-v3link-dual-camera-kit.rst

+.. _arducam-imx219-v3link-dual-camera-kit:
+
+.. note:: This page is a work in progress. Further drive testing and images will be added soon
+
+Using the Arducam Dual V3Link Camera Kit
+############################################
+
+`The Arducam Dual V3Link Camera Kit <https://www.arducam.com/product/arducam-imx219-v3link-camera-kit-for-raspberry-pi/>`_ is an IMX219 based kit that leverages Texas Instruments' FPDLink technology to enable using two CSI cameras over a single port up to 15 minutes away using twisted pair cables.
+
+.. image:: ../images/arducam_dual_1.jpg
+
+.. note:: Unlike the larger quad-camera kit, the dual camera kit aims to simplify the software stack and improve operability with the Pi and other non-TI SBCs by forgoing the ability to support multi-stream CSI inputs. This means that it is limited to "switching" between the two FPDLink inputs but have the benefit of not requiring additional drivers beyond support for the base CSI camera driver (IMX219 in this case)
+
+Initial Hardware Connection
+*****************************
+
+Simply plug in the HAT into the BeagleY GPIO header and connect the CSI header as shown below. 
+
+Either CSI header may be connected but make sure you use the corresponding CSI port DTS when enabling your "camera".
+
+TODO - ADD CSI 0/1 Header Location photo.
+
+Verify that the HAT is connected
+************************************
+
+The Arducam HAT should present itself as an I2C device on Bus 1.
+
+To check that the I2C Bus looks like we expect:
+
+.. code:: console
+
+    sudo i2cdetect -r -y 1
+
+
+To verify actual communication with the FPDlink device, we issue the following command: 
+
+.. code:: console
+
+    sudo i2ctransfer -f -y 4 w3@0x0c 0xff 0x55 0x01 r1
+
+
+Switching CSI Channels
+************************************
+
+The channel numbering for FPDLink goes from 1 to 2 (as opposed to counting from 0 as is the case for CSI)
+
+Thus, to select video output from channel 1: 
+
+.. code:: console
+
+    sudo i2ctransfer -f -y 4 w3@0x0c 0xff 0x55 0x01 
+
+To switch to channel 2:
+
+.. code:: console
+
+    sudo i2ctransfer -f -y 4 w3@0x0c 0xff 0x55 0x02
+
+
+Troubleshooting
+************************************
+
+For additional documentation and support, see the `Arducam Docs <https://docs.arducam.com/V3Link-Camera-Solution/V3Link-Camera-Solution-for-Raspberry-Pi/Introduction/>`_.
\ No newline at end of file

boards/beagley/ai/expansion/Connecting IMX219 CSI Cameras.rst

+.. _imx219-csi-cameras:
+
+.. note:: This page is a work in progress. Further drive testing and images will be added soon
+
+
+Using IMX219 CSI Cameras
+############################
+
+To enable an IMX219 CSI camera, modify the following file: /boot/firmware/extlinux/extlinux.conf
+
+Using CSI Port 0
+**************************************
+
+Then, add the following line to load the IMX219 CSI0 DTBO: 
+
+.. code:: bash
+
+   fdtoverlays /overlays/k3-am625-beagleplay-lt-lcd185.dtbo
+
+Your /boot/firmware/extlinux/extlinux.conf file should look something like this:
+
+.. code:: bash
+
+   label Linux eMMC
+      kernel /Image
+      append root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 systemd.unified_cgroup_hierarchy=false quiet
+      fdtdir /
+      fdtoverlays /overlays/k3-am625-beagleplay-lt-lcd185.dtbo
+      initrd /initrd.img
+
+Using CSI Port 1
+*******************
+
+
+Troubleshooting
+*******************
\ No newline at end of file