diff --git a/doc/sphinx/source/projects/ad405x_iio/ad4052_connection_diagram.png b/doc/sphinx/source/projects/ad405x_iio/ad4052_connection_diagram.png
deleted file mode 100644
index 282104b2..00000000
Binary files a/doc/sphinx/source/projects/ad405x_iio/ad4052_connection_diagram.png and /dev/null differ
diff --git a/doc/sphinx/source/projects/ad405x_iio/ad405x_connection_diagram.png b/doc/sphinx/source/projects/ad405x_iio/ad405x_connection_diagram.png
new file mode 100644
index 00000000..d247661b
Binary files /dev/null and b/doc/sphinx/source/projects/ad405x_iio/ad405x_connection_diagram.png differ
diff --git a/doc/sphinx/source/projects/ad405x_iio/ad405x_iio.rst b/doc/sphinx/source/projects/ad405x_iio/ad405x_iio.rst
index cacdbf2d..bb30aeab 100644
--- a/doc/sphinx/source/projects/ad405x_iio/ad405x_iio.rst
+++ b/doc/sphinx/source/projects/ad405x_iio/ad405x_iio.rst
@@ -8,10 +8,12 @@ Supported Hardware
 **Supported Devices:**
 
 * `AD4052 <https://www.analog.com/en/products/ad4052.html>`_ 
+* `AD4050 <https://www.analog.com/en/products/ad4050.html>`_
 
 **Supported Evaluation Boards:**
 
 * `EVAL-AD4052-ARDZ <https://www.analog.com/en/resources/evaluation-hardware-and-software/evaluation-boards-kits/eval-ad4052.html>`_
+* `EVAL-AD4050-ARDZ <https://www.analog.com/en/resources/evaluation-hardware-and-software/evaluation-boards-kits/eval-ad4050.html>`_
 
 **Supported Carrier Boards:**
 
@@ -22,10 +24,10 @@ Introduction
 ============
 
 This page gives an overview of using the ARM platforms supported (default is Mbed) 
-firmware example with Analog Devices AD4052 Evaluation board and SDP-K1 controller board. 
+firmware example with Analog Devices AD4052/AD4050 Evaluation boards and SDP-K1 controller board.
 This example code leverages the ADI developed IIO (Industrial Input Output) ecosystem to 
-evaluate the AD4052 device by providing a device debug and data capture support.
-The code provides support for MBED and STM32 platforms, using the SDP-K1 controller board.
+evaluate the AD4052 or AD4050 device by providing a device debug and data capture support.
+The code provides support for MBED and STM32 platforms.
 
 The respective build guides for each of the platforms
 can be found in the further sections. The active platform can be chosen by selecting the appropriate 
@@ -50,13 +52,13 @@ to communicates with IIO device.
 Hardware Connections
 ====================
 
-Required: SDP-K1 (or alternative Mbed enabled controller board, or an STM32 board ), EVAL-AD4052 board
+Required: SDP-K1 (or alternative Mbed enabled controller board, or an STM32 board ), EVAL-AD4052 or EVAL-AD4050 board
 and USB cable.
 
-Connect the EVAL-AD042 board to SDP-K1 board (or any other Mbed enabled controller 
+Connect the EVAL-AD4052/EVAL-AD4050 board to SDP-K1 board (or any other Mbed enabled controller
 board or an equivalent STM32 board). Connect controller board to the PC using the USB cable. 
 
-   .. image:: /source/projects/ad405x_iio/ad4052_connection_diagram.png
+   .. image:: /source/projects/ad405x_iio/ad405x_connection_diagram.png
       :width: 600
 
 
@@ -69,9 +71,9 @@ SDP-K1 :
 Connect the VIO_ADJUST jumper on the SDP-K1 to 3.3V position 
 to drive SDP-K1 GPIOs at 3.3V
 
-**EVAL-AD4052:**
+**EVAL-AD4052/AD4050:**
 
-Please refer to the user guide for the jumper connections on the EVAL-AD4052 board
+Please refer to the user guide for the jumper connections on the EVAL-AD4052/AD4050 board
 
 .. Communication Interface section:
 
@@ -89,6 +91,17 @@ Please refer to the user guide for the jumper connections on the EVAL-AD4052 boa
 
 .. include:: /source/tinyiiod/iio_firmware_structure.rst
 
+**Selection of active device:**
+
+The active device is set to AD4052 by default if no other device type is defined.
+The active device can be changed to AD4050 by defining the macro **DEV_AD4050** in the app_config.h file.
+This can be done by uncommenting the corresponding line of code in that file.
+
+
+.. code-block:: C
+
+   // #define DEV_AD4050
+
 =======
 Support
 =======