Merge branch 'Poojahalappanavar15-master-patch-32271' into 'master'

Update avenger-96-board.rst

See merge request OSTC/OHOS/docs/developer-guide!76

documentation/source/quick-start/avenger-96-board.rst

 Avenger 96 Board
 ################
 
-The STM32MP157 is a highly integrated multi-market system-on-chip designed to enable secure and space constraint applications within the Internet of Things. Avenger96 board features dual Arm Cortex-A7 cores and an Arm Cortex-M4 core. In addition, an extensive set of interfaces and connectivity peripherals are included to interface to cameras, touch-screen displays an MMC/SD cards. It also fully supports wireless communication, including WLAN and BLE.
+The STM32MP157 is a highly integrated multi-market system-on-chip designed to enable secure and space constraint applications within the Internet of Things. Open harmony OS based supports Linux 5.4 for Cortex-A7 cre and ZEphyr for Cortex-M4. In addition, an extensive set of interfaces and connectivity peripherals are included to interface to cameras, touch-screen displays an MMC/SD cards. It also fully supports wireless communication, including WLAN and BLE.
 
 .. figure:: images/avenger96.png
 
@@ -79,30 +79,63 @@ For more details on Avenger 96 board, refer https://www.96boards.org/product/ave
 
 Bulding Zephyr onto Avenger96 board
 *************************************
+OpenHarmony can be hosted on top of variety of kernels. Currently supported kernels (a.k.a. OHOS flavours) are Linux.
 
-Creating uSD card image for the Avenger96 board
-===============================================
+To build OHOS flavour, use the following command syntax:
 
-Steps for building a BSP for ST's development boards is referred here: `<https://wiki.st.com/stm32mpu/index.php/STM32MP1_Distribution_Package>`_.
+.. code-block:: console
+
+   $ TEMPLATECONF=../sources/meta-ohos/flavours/<lower_case_flavour> . ./sources/poky/oe-init-build-env   build-<flavour>-<stm32mp1-avg96>
+
+   $ bitbake <image-name>
+
+MACHINE variable can be set up in conf/local.conf file under build directory or via command line:
+
+Example:
+
+.. code-block:: console
+
+   $ MACHINE=<stm32mp1-avg96> bitbake <image-name>
+
+OHOS Linux flavour
+******************
+OHOS Linux flavour is based on poky distribution
+
+Supported images : core-image-minimal
+
+Supported machines : stm32mp1-avg96
+
+Example:
+
+.. code-block:: console
 
-Building the BSP for the Avenger96 follows the scheme of the above build process but starts with a different 'repo' manifest file:
+   $ TEMPLATECONF=../sources/meta-ohos/flavours/linux . ./sources/poky/oe-init-build-env build-ohos-linux-stm32mp1-avg96
+   $ bitbake core-image-minimal
 
-* Create the build directory following ST's recommendations at https://wiki.st.com/stm32mpu/wiki/Example_of_directory_structure_for_Packages.
+You can test the image built for the stm32mp1-avg96 target by issuing:
 
-		
-* Enter the working directory and execute the following commands:
-	
 .. code-block:: console
 
-   $ repo init -u https://github.com/dh-electronics/manifest-av96 -b dunfell
-	  
-   $ repo sync
-	  
-   $ source layers/meta-arrow/scripts/init-build-env.sh
-	  
-   $ bitbake av96-weston
+   $ runqemu stm32mp1-avg96 qemuparams="-nographic"
+
+After successful bootup, you should see following:
+
+.. code-block:: console
 
-The last command will build the BSP. The full build will take about 1-2 hours dpending on machine and internet speed and will require around 25GB disk space. 
+   Poky (Yocto Project Reference Distro) 3.1.4 stm32mp1-avg96 /dev/ttyS0
+   stm32mp1-avg96 login:
+
+Default login is root without a password. After login you should see following prompt:
+
+.. code-block:: console
+
+   root@qstm32mp1-avg96:~#
+
+To exit qemu, you can either shut down the system:
+
+.. code-block:: console
+
+   root@stm32mp1-avg96:~# poweroff -f
 
 
 Flashing an Application to Avenger96 board
@@ -113,8 +146,7 @@ When the build completes it puts all the required files into the'deploy' folder.
 
    $ cd tmp-glibc/deploy/images/stm32mp1-av96/
      
-	$ ./scripts/create_sdcard_from_flashlayout.sh flashlayout_av96-weston/trusted/ 
-      FlashLayout_sdcard_stm32mp157a-av96-trusted.tsv
+	$ ./scripts/create_sdcard_from_flashlayout.sh stm32mp1-avg96/flashlayout_core-image-base/extensible/FlashLayout_sdcard_stm32mp157a-av96-extensible.tsv
 
 The last command creates FlashLayout_sdcard_stm32mp157a-av96-trusted.raw.
 We can write it to a uSD card with:
@@ -125,6 +157,8 @@ We can write it to a uSD card with:
 
 Once you have built your own AV96 Yocto image, your build provides all the files you need to use the Cube Programmer.
 
+Note: Refer for more information related to Aenger96 image programming : https://wiki.dh-electronics.com/index.php/Avenger96_Image_Programming
+
 
 Debugging
 *********