Update build producer document for AGL IC container integrationpike_16.0.2pike_16.0.1pike/16.0.2pike/16.0.116.0.216.0.1

Updating AGL IC container integration documentation based on revised
documentation available on confluence
https://confluence.automotivelinux.org/display/IC/Build+Procedure+for+AGL+IC+with+Container+Integration

Bug-AGL: [SPEC-4805]
Signed-off-by: Vinod Ahuja <vahuja@unomaha.edu>
Change-Id: I6f49d3ee846bfee371662d0ac1b98dbd3fd76bbb
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29000
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
(cherry picked from commit c71f2899ee9c53f69d64ff44aeebf5f36eb0ac0b)
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/29077

12 files changed, 385 insertions, 73 deletions

diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/01_Instrument_Cluster_(IC-IVI_with_Container_isolation).md b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/01_Instrument_Cluster_(IC-IVI_with_Container_isolation).md
index e18903e..5e069e0 100644
--- a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/01_Instrument_Cluster_(IC-IVI_with_Container_isolation).md
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/01_Instrument_Cluster_(IC-IVI_with_Container_isolation).md
@@ -3,120 +3,432 @@ title: Instrument Cluster (IC-IVI with Container isolation)
 ---
 
 # Build and Boot AGL Instrument Cluster demo image (IC-IVI with Container isolation)
-## Required Equipments
-**1) Tested board:** **[Starter Kit Pro/M3](https://elinux.org/R-Car/Boards/M3SK) + [kingfisher support](https://elinux.org/R-Car/Boards/Kingfisher)**
 
-**2) MicroUSB**
 
-**3) MicroSD card**
-## 0. Host PC environemnt
-**Build PC**
-Ubuntu OS (Tested version 18.04.6 LTS)
+This document describe how to build AGL instrument cluster with
+container integration.
 
-## 1. Define Your Top-Level Directory
+## 1. Select Image type and target board
+
+AGL IC container integration has various type.  Developer need to choice
+which integration type.  Those type show in table1. 
+
+**Table 1. Integration type.**
+
+| No. | Type name | Detail of type | Required storage (SD card) size - board. | Build time AMD R9 5900HX /64GByte RAM | Required storage size-build. |  |
+|:---:|:---:|:---:|:---:|:---:|:---:|:---:|
+| 1 | Simple container host | This integration aim to core package definition for container host using LXC.  This integration is not include demo package. This integration aim to define starting point for downstream product development. | 1G Byte |  | 150GByte | Console only. |
+| 2a | Instrument cluster with simple demo IVI install to one partition. | This integration aim to get most simple integration with demo feature.  This container runtime and management is constructed with LXC package only.  On the other hand, it has limitation for supported use case.  This integration support two demo guest run in one board (instrument cluster guest and momi IVI guest). This integration aim to learn drm lease and LXC container by developer. | 2GByte | 2h | 300GByte | ![](images/image1.png) |
+| 3a | Instrument cluster with demo IVI install to one by one partition. | This integration aim to get simple integration with demo feature.  This container runtime and management is constructed with container management daemon with liblxc.  This integration will improve to support many embedded use case.  This integration support two demo guest run in one board (instrument cluster guest and momi IVI guest). This integration aim to learn and develop AGL IC container integration by developer. | 16GByte (Including pre-allocated partition for 3 guests.) | 2h | 300GByte | ![](images/image1.png) |
+| 3b | Instrument cluster with four demo IVI install to one by one partition. | This integration aim to get full demo integration with AGL demo IVI.  This integration is extend from 3a integration.  This integration support instrument cluster guest and four IVI guest (momi, qt, flutter, html5).   This integration aim to use AGL demonstration in each event by developer. | 16GByte | 3a+6h | 600GByte | ![](images/image2.png) |
+
+We recommend to choice 3a.  It can extend to 3b.
+
+AGL IC container integration supported two board.  Those board show in
+table2.
+
+**Table2. Supported board.**
+
+| Board type | Support integration type | status |
+|:---:|:---:|:---:|
+| AGL RefHW | 1,2a,3a,3b | Tested |
+| R-CarH3 Starter Kit with Kingfisher board | 1,2a,3a,3b | Not tested. |
+| R-CarM3 Starter Kit with Kingfisher board | 1,2a,3a,3b | EOL Board. Not tested. |
+| R-CarH3 Starter Kit | 1,2a | End of Supported in latest release. |
+| R-CarM3 Starter Kit | 1,2a | EOL Board. End of  support in latest release. |
+| Raspberry Pi4 (4G or 8G) | 1,2a,3a,3b | Tested. |
+
+
+We recommend to choice AGL RefHW or Raspberry Pi4 (4G or 8G).
+
+**Typical Hardware Set is shown in Appendix.1. **
+
+## 2. Setup build environment
+
+Build environment for AGL IC container integration is same as AGL other
+profile build environment. 
+
+### 1st step:
+Please read [[Build Process Overview]](https://docs.automotivelinux.org/en/pike/#01_Getting_Started/02_Building_AGL_Image/01_Build_Process_Overview/) in AGL doc.
+
+### 2nd step:
+Please read [[Preparing Your Build Host]](https://docs.automotivelinux.org/en/pike/#01_Getting_Started/02_Building_AGL_Image/02_Preparing_Your_Build_Host/) in AGL doc.
+
+### 3rd step: 
+Define Your Top-Level Directory.
+
+```bash
+$ export AGL_TOP=$HOME/AGL
+$ mkdir -p $AGL_TOP
+```
+
+### 4th step: Download the repo Tool and Set Permissions
+
+If your environment already install google repo, please skip this step.
+
+```bash
+$ mkdir -p $HOME/bin
+$ export PATH=$HOME/bin:$PATH
+$ curl https://storage.googleapis.com/git-repo-downloads/repo > $HOME/bin/repo
+$ chmod a+x $HOME/bin/repo
+```
+
+### 5th step: Setup git
+
+If your environment already setup user information for git, please skip this step.
+
+```bash
+$ git config \--global user.email "you@example.com"
+$ git config \--global user.name "Your Name"
+```
+
+### 6th step: Download the AGL Source Files
+
+```bash
+$ cd $AGL_TOP
+$ mkdir pike
+$ export AGL_TOP=$HOME/AGL/pike
+$ cd $AGL_TOP
+$ repo init -b pike -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
+$ repo sync
+```
+
+### 7th step: Downloading Proprietary Drivers  (AGL RefHW and R-Car H3/M3 with Kingfisher board only procedure)
+
+If your board is Raspberry Pi4, please skip this step.
+
+#### 7-1: Downloading Proprietary Drivers from [Renesas-automotive-products](https://www.renesas.com/us/en/products/automotive-products/automotive-system-chips-socs/r-car-h3-m3-documents-software).
+
+In case of Optimistic Octopus and master, please download this.
+
+![](images/image3.png)
+
+#### 7-2: To check the files to download.
+```bash
+$ grep -rn ZIP_.= $AGL_TOP/meta-agl/meta-agl-bsp/meta-rcar-gen3/scripts/setup_mm_packages.sh
+$ export XDG_DOWNLOAD_DIR=$HOME/Downloads
+```
+
+#### 7-3: Download and copy Proprietary Drivers files (Run commands at downloaded files directory).
+
+```bash
+$ cp R-Car_Gen3_Series_Evaluation_Software_Package_* $XDG_DOWNLOAD_DIR/
+$ chmod a+rw $XDG_DOWNLOAD_DIR/*.zip
+```
+
+## 3. Configure to target board and build.
+
+### 1st step:  Run the aglsetup.sh Script.
+
+```bash
+$ cd $AGL_TOP
+```
+
+When your board is AGL RefHW.
+
+```bash
+$ source meta-agl/scripts/aglsetup.sh -f -m h3ulcb -b build-ic-refhw agl-ic-container agl-refhw-h3
+```
+
+When your board is R- CarH3 Starter Kit with Kingfisher board.
+
+```bash
+$ source meta-agl/scripts/aglsetup.sh -f -m h3ulcb-kf -b build-ic-h3kf agl-ic-container
+```
+
+When your board is Raspberry Pi 4
+```bash
+$ source meta-agl/scripts/aglsetup.sh -f -m raspberrypi4 -b build-ic-rpi4 agl-ic-container
+```
+
+### 2nd step: Build target image.
+
+In this time, you can build 1,2a and 3a.  If you want to build 3b,
+please do extra step in next section.
+
+When you choice integration type 1.
+
+```bash
+$ bitbake lxc-host-image-minimal
+```
+
+When you choice integration type 2a.
+
+```bash
+$ bitbake agl-cluster-demo-lxc-host
+```
+
+When you choice integration type 3a.
+
+```bash
+$ bitbake agl-instrument-cluster-container-demo
+```
+
+## 4. Extra step for type 3b build.
+
+This extra step can select 4a or 4b.  When you want to build AGL demo
+IVI container guest in myself, please select 4a work flow.  When you
+want to create AGL IC container demo quicly, please select 4b work flow.
+
+Typically 4a step require long build time about 6h.  When you want to
+build AGL Ref HW/ SK+ Kinfgisher software, you can\'t select select 4b
+work flow that depend to Renesas propriety license limitation.
+
+### 4a. Extra step for type 3b build myself.
+
+#### 1st step: Configure 2nd build tree.
+
+We recommend to open new terminal to do this extra section.
+
+```bash
+$ export AGL_TOP=$HOME/AGL/pike
+$ cd $AGL_TOP
+```
+
+When your board is AGL RefHW.
 
 ```bash
-export AGL_TOP=$HOME/AGL
-mkdir -p $AGL_TOP
+$ source meta-agl/scripts/aglsetup.sh -f -m h3ulcb -b build-ivi-refhw agl-container-guest-demo agl-demo agl-refhw-h3
 ```
 
-## 2. Download the repo Tool and Set Permissions
+When your board is R- CarH3 Starter Kit with Kingfisher board.
 
 ```bash
-mkdir -p $HOME/bin
-export PATH=$HOME/bin:$PATH
-curl https://storage.googleapis.com/git-repo-downloads/repo > $HOME/bin/repo
-chmod a+x $HOME/bin/repo
+$ source meta-agl/scripts/aglsetup.sh -f -m h3ulcb-kf -b build-ivi-h3kf agl-container-guest-demo agl-demo
 ```
 
-## 3. Download the AGL Source Files
-- **AGL Version:** Magic Marlin
+When your board is Raspberry Pi 4
 ```bash
-cd $AGL_TOP
-mkdir marlin
-export AGL_TOP=$HOME/AGL/marlin
-cd $AGL_TOP
-git config --global user.email "you@example.com"
-git config --global user.name "Your Name"
-repo init -b pike -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
-repo sync
+$ source meta-agl/scripts/aglsetup.sh -f -m raspberrypi4 -b build-ivi-rpi4 agl-container-guest-demo agl-demo
 ```
-- Optional: Specify the manifest file(pike_16.0.0.xml) using -m option
+
+#### 2nd step: Build target images.
+
+Type 3b integration need to build 3 image, these image are
+agl-ivi-demo-platform, agl-ivi-demo-platform-flutter and
+agl-ivi-demo-platform-html5.
 
 ```bash
-repo init -b pike -m pike_16.0.0.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
+$ bitbake agl-ivi-demo-platform
+$ bitbake agl-ivi-demo-platform-flutter
+$ bitbake agl-ivi-demo-platform-html5
 ```
-- Optional: Specify the master branch
+
+#### 3rd step: Set deploy path of AGL IVI Demo to IC side config.
+
+Type 3b integration refer to IVI pre build image.  Please set IVI side
+deploy directory in ic side local.conf (or site.conf).
+
+At $AGL_TOP/build-ic-XXXX/conf/local.conf
+
+Add to
 ```bash
-repo init -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
+OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR = "/path/to/deploy/"
 ```
 
-## 4. Downloading Proprietary Drivers
-Downloading Proprietary Drivers from [Renesas-automotive-products](https://www.renesas.com/us/en/products/automotive-products/automotive-system-chips-socs/r-car-h3-m3-documents-software)
-- To check the files to download
+ex.  When your board is AGL RefHW and your home directory is "/home/user/".
 ```bash
-grep -rn ZIP_.= $AGL_TOP/meta-agl/meta-agl-bsp/meta-rcar-gen3/scripts/setup_mm_packages.sh
-export XDG_DOWNLOAD_DIR=$HOME/Downloads
+OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR = "/home/user/AGL/octopus/build-ivi-refhw/tmp/deploy"
 ```
-- Download and copy Proprietary Drivers files (Run commands at downloaded files directory)
+
+ex.  When your board is R- CarH3 Starter Kit with Kingfisher board and your home directory is "/home/user/".
+
 ```bash
-cp R-Car_Gen3_Series_Evaluation_Software_Package_* $XDG_DOWNLOAD_DIR/
-chmod a+rw $XDG_DOWNLOAD_DIR/*.zip
+OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR = "/home/user/AGL/octopus/build-ivi-h3kf/tmp/deploy"
 ```
-## 5. Define Your Board
-- Supporting Starter Kit Pro/M3 + kingfisher Board (For other supported boards, check [Define Your Board](https://docs.automotivelinux.org/en/pike/#01_Getting_Started/02_Building_AGL_Image/09_Building_for_Supported_Renesas_Boards.md))
+
+ex.  When your board is Raspberry Pi 4 and your home directory is "/home/user/".
+
 ```bash
-export MACHINE=m3ulcb-kf
+OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR = "/home/user/AGL/octopus/build-ivi-rpi4/tmp/deploy"
 ```
-## 6. Run the aglsetup.sh Script
+
+#### 4th step: Build all in one image (3b).
+
+Back to terminal for ic build.
+
 ```bash
-cd $AGL_TOP
-source meta-agl/scripts/aglsetup.sh -f -m $MACHINE -b $MACHINE agl-ic-container
+$ bitbake agl-instrument-cluster-container-demo
 ```
 
-## 7. Using BitBake
+### 4b. Extra step for type 3b using pre build image.
+
+The 4b can select Raspberry Pi 4 board only, this limitation depend to
+Renesas propriety license limitation.
+
+#### 1st step: Download stable prebuild image from AGL site.
+
+Download IVI guest images from this link.
+
+[[Prebuild AGL Demo IVI container images for Raspberry Pi
+4.]](https://drive.google.com/file/d/1uXel0K9_IK7SAEc8msKyXvNWhFRWgF4C/view?usp=sharing)
+
+Extract download tar.bz2 archive to any directory.
+
 ```bash
-bitbake agl-cluster-demo-lxc-host
+$ cd /path/to/directory/
+$ tar xvJf /path/to/download/agl-demo-ivi-container-guest-raspberrypi4-64.tar.bz2
 ```
-- The build process puts the resulting image in the Build Directory
-($AGL_TOP/m3ulcb-kf/tmp/deploy/images/m3ulcb)
-## 8.Boot the Board (Deploying the AGL Demo Image)
-- To boot your image on the Renesas board, you need to do three things:
 
-a) Update all [firmware](https://docs.automotivelinux.org/en/pike/#01_Getting_Started/02_Building_AGL_Image/09_Building_for_Supported_Renesas_Boards/#4-troubleshooting) on R-Car M3 Starter Kit board (Flashing firmware).
+#### 2nd step: Set deploy path of AGL IVI Demo to IC side config.
 
-b) Prepare the MicroSD card and Flash image to the MicroSD card using [Etcher](https://www.balena.io/etcher/)
- (**image file name:** lxc-host-image-demo-m3ulcb-kf.wic.xz), then insert MicroSD card in the R-Car M3SK.  
-c) Boot the board.
+Set extracted directory using OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR in
+local.conf (or site.conf).
 
-1) Use a MicroUSB cable to connect the PC to R-Car Starter Kit Pro (M3ULCB) board CN12 "CPLD/DEBUG"
-- Serial settings are 115200 8N1.
-- Run any standard terminal emulator program (e.g. minicom).
-[Replace **"Device"** with USB tty device name, for example **`/dev/ttyUSB0`**]
 ```bash
-sudo minicom -b 115200 -D "DEVICE"
+OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR="/path/to/directory/prebuild/"
 ```
 
-- Power on the board
-- Quickly hit any key to get into the U-boot command prompt; you should see the following:
- ```bash
-Hit any key to stop autoboot:  0                                                                =>
+#### 3rd step: Build all in one image (3b).
+
+Back to terminal for ic build.
+
+```bash
+$ bitbake agl-instrument-cluster-container-demo
 ```
-- Booting image command (for details check [How to boot](https://elinux.org/R-Car/AGL#Instrument_Cluster_with_Container_isolation_demo_image))
- ```bash
-ext4load 0x48080000 Image
-ext4load 0x48000000 /boot/r8a77961-ulcb-kf.dtb
-booti 0x48080000 - 0x48000000
+
+## 5. Write image to SD card.
+
+The 3a and 3b image is constructed by wic image, that include partition
+table and each partition data into one image file.
+
+In default setting, that wic image is compressed xz.  When that wic
+image write to SD card, you need to use xzcat ant dd command in build
+PC.
+
+```bash
+$ sudo bash -c "xzcat /path/to/image/directory/agl-instrument-cluster-container-demo-XXXXX.wic.xz | dd of=/dev/sdXXX bs=128M"
 ```
 
-# Run SoC board Screen
-A) Connect HDMI panel to M3SK(CN4) for **IVI Container**
-![IVI](https://elinux.org/images/9/91/Marlin-lxc-Ivi.JPG)
+**If you are missing to set SD card device "/dev/sdXXX", it cause
+SSD/HDD data break (only logical, not physical).**
+
+For example;
+
+A /dev/sda is SSD for your PC.  A /dev/sdb is SD card.  You should use
+/dev/sdb, must not use /dev/sda.
+
+When your PC has direct SD card interface not a use card reader, your SD
+card device is /dev/mmcblkX may be.
+
+## 6. Power on.
+
+## 7. How to use container exchange UI.
+
+### 7a. Momi Web
+
+The Momi web is a web interface for container exchange.  When you want
+to use Momi web, you must connect network between board and
+PC/Tablet/Phone.
+
+**The Momi web is completely demo feature, that open many security hole.
+ You shall not use out of standalone demo.**
+
+#### 1st step: Check IP address in your board.
+
+After booting, you check IP address in your board.
+
+```bash
+root@raspberrypi4-64:\~# ifconfig\
+eth0      Link encap:Ethernet  HWaddr E4:XX:YY:ZZ:WW:VV\
+           inet addr:192.168.10.128  Bcast:192.168.10.255
+  Mask:255.255.255.0
+```
+
+In this case, this board set IP address by 192.168.10.128.
+
+#### 2nd step: Connect to board using web browser.
+
+Open "[http://a.b.c.d:8080](http://a.b.c.d:8080)".  When
+a board is set IP address 192.168.10.128, you open
+"[http://192.168.10.128:8080](http://192.168.10.128:8080)".
+
+When you success to connect to board, your web browser show these web
+UI.
+
+#### PC View
+
+![](images/image4.png)
+
+#### Mobile View
+
+![](images/image5.png)
+
+### 7b. Keyboard Interface
+
+Please refer to Appendix 3.
+
+## Appendix.1.  Typical Hardware set.
+
+### AGL Reference Hardware.
+
+![](images/image6.png)
+
+
+| **No** | **Name** | **num** | **Where to buy** |
+|---|---|---|---|
+| 1 | AGL Ref HW | 1 | Ask to Panasonic. [Contact about purchase](https://confluence.automotivelinux.org/display/RHSA/Contact+about+purchase) |
+| 2 | Touch Display (Full HD) | 1 | [https://amzn.asia/d/7URb6r8](https://amzn.asia/d/7URb6r8) |
+| 3 | Cluster Display (1920x720 or Full HD) | 1 | [https://amzn.asia/d/bGircST](https://amzn.asia/d/bGircST) |
+| 4 | HDMI Cable (Need to check how to connect this cable to Touch/Cluster Display, that depend to display side connector) | 2 | [https://amzn.asia/d/auuhnTK](https://amzn.asia/d/auuhnTK) |
+| 5 | Optional: Special Keyboard | 1 | [https://amzn.asia/d/dZdbp9X](https://amzn.asia/d/dZdbp9X) |
+
+### Raspberry PI4
+
+![](images/image7.png)
+
+| **No** | **Name** | **num** | **Where to buy** |
+|---|---|---|---|
+| 1 | Raspberry PI 4(4G or 8G) with Power supply | 1 | [https://akizukidenshi.com/catalog/g/gM-14778/](https://akizukidenshi.com/catalog/g/gM-14778/) [https://akizukidenshi.com/catalog/g/gM-16293/](https://akizukidenshi.com/catalog/g/gM-16293/) |
+| 2 | Touch Display (Full HD) | 1 | [https://amzn.asia/d/7URb6r8](https://amzn.asia/d/7URb6r8) |
+| 3 | Cluster Display (1920x720 or Full HD) | 1 | [https://amzn.asia/d/bGircST](https://amzn.asia/d/bGircST) |
+| 4 | HDMI Cable (Need to check how to connect this cable to Touch/Cluster Display, that depend to display side connector) | 2 | [https://akizukidenshi.com/catalog/g/gC-15002/](https://akizukidenshi.com/catalog/g/gC-15002/) |
+| 5 | Optional: Special Keyboard | 1 | [https://amzn.asia/d/dZdbp9X](https://amzn.asia/d/dZdbp9X) |
+
+
+## Appendix.2. Cluster with IVI Containers View.
+
+### Qt IVI
+
+![](images/image8.jpeg)
+
+### Flutter IVI
+
+![](images/image9.jpeg)
+
+### HTML5 IVI
+
+![](images/image10.jpeg)
+
+### Momi IVI
+
+![](images/image11.jpeg)
+
+## Appendix 3. How to configure Special Keyboard.
+
+### How to get configuration tool.
+
+This description is targeting to [this type of special
+keyboard](https://amzn.asia/d/dUxGK5Q). 
+
+The usb-12key-kbd-prog is unofficial community tool of this key board
+that is possible to use linux.  Official windows tool is possible to get
+official site.
+
+Usage of usb-12key-kbd-prog is please refer to upstream site.
+
+Upstream:
+[https://github.com/NeoCat/usb-12key-kbd-prog](https://github.com/NeoCat/usb-12key-kbd-prog)
 
-B) Connect HDMI panel to Kingfisher(CN49)for **Cluster Container**
-![IC](https://elinux.org/images/7/76/Marlin-lxc-Cluster.JPG)
+### Key Map.
+| Key | Container |
+|---|---|
+| A | Momi IVI |
+| C | Crash IVI guest |
+| D | Qt IVI |
+| G | Flutter IVI |
+| H | HTML5 IVI |
 
-<! -- https://elinux.org/images/thumb/7/76/Marlin-lxc-Cluster.JPG/1200px-Marlin-lxc-Cluster.JPG) -->
 # Reference webpages
  1. [eLinux](https://elinux.org/R-Car/AGL)
  1. [Kingfisher Board](https://elinux.org/R-Car/Boards/Kingfisher)
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image1.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image1.png
new file mode 100644
index 0000000..044e01e
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image1.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image10.jpeg b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image10.jpeg
new file mode 100644
index 0000000..70af6c2
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image10.jpeg
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image11.jpeg b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image11.jpeg
new file mode 100644
index 0000000..5f4c695
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image11.jpeg
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image2.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image2.png
new file mode 100644
index 0000000..64006af
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image2.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image3.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image3.png
new file mode 100644
index 0000000..e3f3c8a
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image3.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image4.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image4.png
new file mode 100644
index 0000000..41d2878
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image4.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image5.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image5.png
new file mode 100644
index 0000000..f3edc1f
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image5.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image6.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image6.png
new file mode 100644
index 0000000..2830ffa
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image6.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image7.png b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image7.png
new file mode 100644
index 0000000..158545a
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image7.png
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image8.jpeg b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image8.jpeg
new file mode 100644
index 0000000..f6937a6
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image8.jpeg
diff --git a/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image9.jpeg b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image9.jpeg
new file mode 100644
index 0000000..0a3e945
--- /dev/null
+++ b/docs/01_Getting_Started/03_Build_and_Boot_guide_Profile/images/image9.jpeg