synaptics-astra · aduggan-syna · Dec 15, 2025 · Dec 2, 2025 · Dec 2, 2025 · Dec 2, 2025
diff --git a/conf.py b/conf.py
@@ -4,7 +4,7 @@
 author = 'Synaptics'
 
 # version of the software being documented
-release = 'scarthgap_6.12_v2.0.0'
+release = 'scarthgap_6.12_v2.1.0'
 
 extensions = [ 'synaptics_sphinx_theme' ]
 

diff --git a/hw/index.rst b/hw/index.rst
@@ -7,9 +7,11 @@ Astra Machina Eval Platform
    sl1680.rst
    sl1640.rst
    sl1620.rst
+   sl2600.rst
 
 In this section you can find the hardware user guides for the Astra Machina boards:
 
 - :doc:`sl1680`
 - :doc:`sl1640`
-- :doc:`sl1620`
+- :doc:`sl1620`
+- :doc:`sl2600`
diff --git a/hw/media/sl2600/image10.png b/hw/media/sl2600/image10.png
diff --git a/hw/media/sl2600/image11.png b/hw/media/sl2600/image11.png
diff --git a/hw/media/sl2600/image12.png b/hw/media/sl2600/image12.png
diff --git a/hw/media/sl2600/image13.png b/hw/media/sl2600/image13.png
diff --git a/hw/media/sl2600/image14.png b/hw/media/sl2600/image14.png
diff --git a/hw/media/sl2600/image15.png b/hw/media/sl2600/image15.png
diff --git a/hw/media/sl2600/image16.png b/hw/media/sl2600/image16.png
diff --git a/hw/media/sl2600/image17.png b/hw/media/sl2600/image17.png
diff --git a/hw/media/sl2600/image18.png b/hw/media/sl2600/image18.png
diff --git a/hw/media/sl2600/image19.png b/hw/media/sl2600/image19.png
diff --git a/hw/media/sl2600/image2.png b/hw/media/sl2600/image2.png
diff --git a/hw/media/sl2600/image20.png b/hw/media/sl2600/image20.png
diff --git a/hw/media/sl2600/image3.png b/hw/media/sl2600/image3.png
diff --git a/hw/media/sl2600/image4.png b/hw/media/sl2600/image4.png
diff --git a/hw/media/sl2600/image5.png b/hw/media/sl2600/image5.png
diff --git a/hw/media/sl2600/image6.png b/hw/media/sl2600/image6.png
diff --git a/hw/media/sl2600/image7.png b/hw/media/sl2600/image7.png
diff --git a/hw/media/sl2600/image8.png b/hw/media/sl2600/image8.png
diff --git a/hw/media/sl2600/image9.png b/hw/media/sl2600/image9.png
diff --git a/hw/sl2600.rst b/hw/sl2600.rst
diff --git a/index.rst b/index.rst
@@ -61,7 +61,7 @@ External Documentation
 
    This guide explains in depth how to use the SyNAP toolkit and the SyNAP runtime API.
 
-`Yocto Project Documentation <https://docs.yoctoproject.org/4.0.17/>`__
+`Yocto Project Documentation <https://docs.yoctoproject.org/5.0.9/>`__
 
    Official documentation of the Yocto project.
 

diff --git a/linux/index.rst b/linux/index.rst
diff --git a/linux/media/sl2619-isp-device-capabilities.png b/linux/media/sl2619-isp-device-capabilities.png
diff --git a/linux/media/sl2619-isp-path-devices.png b/linux/media/sl2619-isp-path-devices.png
diff --git a/linux/media/sl2619-list-ctrls.png b/linux/media/sl2619-list-ctrls.png
diff --git a/linux/media/sl2619-media.png b/linux/media/sl2619-media.png
diff --git a/linux/media/sl2619-torq-demo.png b/linux/media/sl2619-torq-demo.png
diff --git a/linux/media/sl2619-torq-image-classification.png b/linux/media/sl2619-torq-image-classification.png
diff --git a/linux/media/sl2619-torq-opbject-detection.png b/linux/media/sl2619-torq-opbject-detection.png
diff --git a/linux/media/sl2619_uart.jpg b/linux/media/sl2619_uart.jpg
diff --git a/quickstart/build_app.rst b/quickstart/build_app.rst
@@ -16,10 +16,10 @@ To build an application follows these steps:
 2. Unpack the toolchain package, the ``CPUTYPE`` for ``sl1680`` is ``cortexa73``, for ``sl1620`` and ``sl1640`` is
    ``cortexa55``::
 
-    $ ./poky-glibc-x86_64-astra-media-${CPUTYPE}-${MACHINE}-toolchain-4.0.9.sh
-    Poky (Yocto Project Reference Distro) SDK installer version 4.0.9
+    $ ./poky-glibc-x86_64-astra-media-${CPUTYPE}-${MACHINE}-toolchain-5.0.9.sh
+    Poky (Yocto Project Reference Distro) SDK installer version 5.0.9
     =================================================================
-    Enter target directory for SDK (default: /opt/poky/4.0.9): toolchain
+    Enter target directory for SDK (default: /opt/poky/5.0.9): toolchain
     You are about to install the SDK to "/home/user/toolchain". Proceed [Y/n]?
     Extracting SDK.................................................................................................................................................................................................................................................................................................................................done
     Setting it up...done

diff --git a/quickstart/hw_setup.rst b/quickstart/hw_setup.rst
@@ -7,7 +7,7 @@ embedded Linux and Android processors. A modular
 design incorporates swappable core compute modules, a common I/O board,
 and daughter cards for connectivity, debug, and flexible I/O options.
 This page lists the simple steps to power on and boot up the system
-and applies to all SL-Series core modules: SL1680, SL1640, and SL1620.
+and applies to all SL-Series core modules: SL1680, SL1640, SL1620, and SL261x.
 
 .. figure:: ./media/connections.png
     :width: 6.5in

diff --git a/release_notes.rst b/release_notes.rst
@@ -5,6 +5,9 @@ SDK Release Notes
 .. toctree::
     :hidden:
 
+    release_notes/scarthgap_6.12_v2.1.0
+    release_notes/scarthgap_6.12_v2.0.2
+    release_notes/scarthgap_6.12_v2.0.1
     release_notes/scarthgap_6.12_v2.0.0
     release_notes/scarthgap_6.12_v2.0.0_alpha
     release_notes/kirkstone_5.15_v1.8.0
@@ -23,6 +26,12 @@ SDK Release Notes
 Scarthgap Releases
 ==================
 
+:doc:`release_notes/scarthgap_6.12_v2.1.0`
+
+:doc:`release_notes/scarthgap_6.12_v2.0.2`
+
+:doc:`release_notes/scarthgap_6.12_v2.0.1`
+
 :doc:`release_notes/scarthgap_6.12_v2.0.0`
 
 :doc:`release_notes/scarthgap_6.12_v2.0.0_alpha`

diff --git a/release_notes/scarthgap_6.12_v2.0.1.rst b/release_notes/scarthgap_6.12_v2.0.1.rst
diff --git a/release_notes/scarthgap_6.12_v2.0.2.rst b/release_notes/scarthgap_6.12_v2.0.2.rst
diff --git a/release_notes/scarthgap_6.12_v2.1.0.rst b/release_notes/scarthgap_6.12_v2.1.0.rst
diff --git a/subject/haier_panel_configuration.rst b/subject/haier_panel_configuration.rst
@@ -37,10 +37,10 @@ Software Configuration
 
 The Haier panel can be enabled by setting the ``dtbo`` variable, in U-Boot, to the correct device tree overlay.
 
-+-----------------+--------------------------------+-----------------------------------+----------------------------------+
-|                 | SL1620                         | SL1640                            | SL1680                           |
-+-----------------+--------------------------------+-----------------------------------+----------------------------------+
-| DTS Overlay     | myna2-haier-panel-overlay.dtbo | platypus-haier-panel-overlay.dtbo | dolphin-haier-panel-overlay.dtbo |
-+-----------------+--------------------------------+-----------------------------------+----------------------------------+
++-----------------+--------------------------------+-----------------------------------+----------------------------------+----------------------------------+
+|                 | SL1620                         | SL1640                            | SL1680                           | SL2619                           |
++=================+================================+===================================+==================================+==================================+
+| DTS Overlay     | myna2-haier-panel-overlay.dtbo | platypus-haier-panel-overlay.dtbo | dolphin-haier-panel-overlay.dtbo | sl2619-haier-panel-overlay.dtbo  |
++-----------------+--------------------------------+-----------------------------------+----------------------------------+----------------------------------+
 
 See :ref:`devicetree_overlays` for details on how to enable the devicetree overlays.
diff --git a/subject/index.rst b/subject/index.rst
@@ -15,6 +15,7 @@ Subject Specific User Guides
    isp_sensor_integration
    updating_isp_sensor_configuration
    gpios
+   otp_guide
    mp_flow_user_guide
    fastlogo_image_generation
    uboot_fastlogo_configuration
@@ -55,6 +56,8 @@ The following guides provide additional details on a specific subject or module.
 
 - :doc:`gpios`
 
+- :doc:`otp_guide`
+
 - :doc:`mp_flow_user_guide`
 
 - :doc:`fastlogo_image_generation`

diff --git a/subject/isp_sensor_integration.rst b/subject/isp_sensor_integration.rst
@@ -5,7 +5,17 @@ ISP Sensor Integration Guide
 Introduction
 ============
 
-This document provides steps to add a new sensor driver to the SL1680. The sensor driver shall be implemented as per Application Programming Interface (API) of the Verisilicon ISP Independent Sensor Interface (ISI) framework. For more details, refer to ISI documentation.
+This document explains how to add a new sensor driver to the SL1680 and SL2610 platforms. Since the integration process differs between the two, refer to the appropriate section below.
+
+:ref:`sensor_sl1680`
+
+:ref:`sensor_sl2610`
+
+.. _sensor_sl1680:
+
+Sensor Integration on SL1680
+----------------------------
+The sensor driver shall be implemented as per Application Programming Interface (API) of the Verisilicon ISP Independent Sensor Interface (ISI) framework. For more details, refer to ISI documentation.
 
 
 Configuration
@@ -49,4 +59,52 @@ Edit ``meta-synaptics/recipes-devtools/synasdk/files/isp_media_server.sh`` with
 
    devtool build synasdk-v4l2isp-sensordrv
    devtool build linux-syna
-   devtool build-image astra-media
+   devtool build-image astra-media
+
+.. _sensor_sl2610:
+
+Sensor Integration on SL2610
+----------------------------
+Any **CSI-compatible sensor** that already includes a **V4L2 subdevice driver** can be integrated directly.
+If a V4L2 subdevice driver is not available, you can refer to the *ov5647.c* implementation from the Linux mainline kernel as a guide to create one.
+
+Make sure to enable the sensor driver as a **module** in the ``sl261x_defconfig``
+
+Device Tree Changes
+======================
+``sl2619-rdk.dts`` file should be changed to match the new sensor specific data. CSI is connected to I2C-0. Therefore, change the  ``i2c0``  device tree node, as explained below.
+
+::
+
+    &i2c0 {
+        cam_node: ov5647@36 {
+            compatible = "ovti,ov5647";
+            reg = <0x36>;
+            status = "okay";
+
+            pwdn-gpios = <&expander1 4 GPIO_ACTIVE_LOW>;
+            clocks = <&osc>;
+
+            port {
+                cam_endpoint: endpoint {
+                    clock-lanes = <0>;
+                    data-lanes = <1 2>;
+                    clock-noncontinuous;
+                    remote-endpoint = <&csi_input>;
+                };
+            };
+        };
+    };
+
+Update the ``cam_node`` to use the new sensor's ``compatible`` string and ``reg`` value (I2C slave address). Also adjust the ``clocks`` property to reflect the correct clock source for the sensor.
+
+The ``port`` node defines the data path. The ``remote-endpoint`` specifies that sensor data enters the CSI driver through the ``csi_input`` port of the CSI node. This does not need to be modified.
+
+However, properties such as ``clock-lanes``, ``data-lanes``, and ``clock-noncontinuous`` may need to be updated depending on the sensor, as these values vary between different devices.
+
+Expected Result
+---------------
+
+Correct sensor integration is confirmed if the ``media-ctl -p`` command shows an entry similar to this:
+
+.. figure:: media/media_ctl_output.png
diff --git a/subject/media/media_ctl_output.png b/subject/media/media_ctl_output.png