Update main documentation

Author: github-actions

main/examples/html/footer.js

@@ -1,3 +1,3 @@
 function writeFooter()  {
-    document.write('Generated on Wed Feb 11 2026 12:18:50 for PROJECT_NAME           = Examples Version 2.2.0 by Arm Ltd. All rights reserved.');
+    document.write('Generated on Wed Feb 11 2026 15:07:36 for PROJECT_NAME           = Examples Version 2.2.0 by Arm Ltd. All rights reserved.');
 };

main/infrastructure/html/footer.js

@@ -1,3 +1,3 @@
 function writeFooter()  {
-    document.write('Generated on Wed Feb 11 2026 12:18:50 for PROJECT_NAME           = Infrastructure Version 2.2.0 by Arm Ltd. All rights reserved.');
+    document.write('Generated on Wed Feb 11 2026 15:07:36 for PROJECT_NAME           = Infrastructure Version 2.2.0 by Arm Ltd. All rights reserved.');
 };

main/overview/html/footer.js

@@ -1,3 +1,3 @@
 function writeFooter()  {
-    document.write('Generated on Wed Feb 11 2026 12:18:50 for PROJECT_NAME           = Overview Version 2.2.0 by Arm Ltd. All rights reserved.');
+    document.write('Generated on Wed Feb 11 2026 15:07:36 for PROJECT_NAME           = Overview Version 2.2.0 by Arm Ltd. All rights reserved.');
 };

main/simulation/html/avh_fvp_cmsis.html

@@ -5,7 +5,7 @@
 <meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
 <meta http-equiv="X-UA-Compatible" content="IE=11"/>
 <meta name="viewport" content="width=device-width, initial-scale=1"/>
-<title>Arm FVP models: CMSIS-based projects</title>
+<title>Arm FVP models: CMSIS Support</title>
 <link href="doxygen.css" rel="stylesheet" type="text/css"/>
 <link href="tabs.css" rel="stylesheet" type="text/css"/>
 <link href="extra_navtree.css" rel="stylesheet" type="text/css"/>
@@ -125,12 +125,12 @@
 </div>
 
 <div><div class="header">
-  <div class="headertitle"><div class="title">CMSIS-based projects</div></div>
+  <div class="headertitle"><div class="title">CMSIS Support</div></div>
 </div><!--header-->
 <div class="contents">
 <div class="textblock"><p><a class="anchor" id="md_src_2avh__fvp__cmsis"></a></p>
-<p>To enable embedded software development for Arm FVP targets, Arm provides necessary device definitions, startup code, board support packages and simple examples in <a href="https://www.open-cmsis-pack.org/">Open-CMSIS-Pack format</a>. The same CMSIS-based concept is followed for Arm FVP targets as also used for more than 12000 real hardware devices. This significantly simplifies project management in IDEs such as Keil MDK, allows straightforward integration of other software components, and improves application portability.</p>
-<p>Table below lists FVPs with the corresponding CMSIS-Packs that implement device/board support, as well as target device names.</p>
+<p>Arm provides comprehensive CMSIS support for FVP targets in <a href="https://www.open-cmsis-pack.org/">Open-CMSIS-Pack format</a>, including device definitions, startup code, board support packages, and examples.</p>
+<p>The following table lists available FVP models with their corresponding CMSIS-Packs and device names:</p>
 <table class="doxtable" style="width:115%">
 <tr>
 <th style="width:27%">Arm FVP Model Name </th><th style="width:25%">CMSIS Packs with DFP/BSP<sup> (1)</sup> </th><th style="width:17%">Device name</th><th>Description </th></tr>
@@ -191,9 +191,36 @@
 <p class="endtd"></p>
 </td></tr>
 </table>
-<blockquote class="doxtable">
-<p><b>Note</b> <sup>(1)</sup> The BSP packs listed here (ending with "_BSP") also contain device definition as provided in the corresponding "Device Name" cell and do not require separate device family pack (DFP). </p>
-</blockquote>
+<p><b>Note:</b> <sup>(1)</sup> BSP packs (suffixed with "_BSP") include both board support and device definitions, eliminating the need for a separate Device Family Pack (DFP).</p>
+<h1><a class="anchor" id="autotoc_md0"></a>
+Software Layers</h1>
+<p>The AVH_FVP pack provides board support layers for Corstone FVP platforms in the <code>board/</code> folder. Each board layer includes hardware-specific configurations, drivers, and setup for running applications on FVP simulation models.</p>
+<table class="markdownTable">
+<tr class="markdownTableHead">
+<th class="markdownTableHeadLeft">Folder   </th><th class="markdownTableHeadLeft">Description    </th></tr>
+<tr class="markdownTableRowOdd">
+<td class="markdownTableBodyLeft"><code>./board/Corstone-300</code>   </td><td class="markdownTableBodyLeft">Board layer for Corstone-300 FVP with optional Ethos-U55/U65    </td></tr>
+<tr class="markdownTableRowEven">
+<td class="markdownTableBodyLeft"><code>./board/Corstone-310</code>   </td><td class="markdownTableBodyLeft">Board layer for Corstone-310 FVP with optional Ethos-U55/U65    </td></tr>
+<tr class="markdownTableRowOdd">
+<td class="markdownTableBodyLeft"><code>./board/Corstone-315</code>   </td><td class="markdownTableBodyLeft">Board layer for Corstone-315 FVP with optional Ethos-U65    </td></tr>
+<tr class="markdownTableRowEven">
+<td class="markdownTableBodyLeft"><code>./board/Corstone-320</code>   </td><td class="markdownTableBodyLeft">Board layer for Corstone-320 FVP with optional Ethos-U85   </td></tr>
+</table>
+<p>Each folder contains a <b>README</b> with implementation details and multiple <b>CSolution layer files</b> (<code>*.clayer.yml</code>) that configure different hardware variants. The postfix in the <code>*.clayer.yml</code> filename determines the Ethos-U NPU configuration:</p>
+<table class="markdownTable">
+<tr class="markdownTableHead">
+<th class="markdownTableHeadLeft">Layer File   </th><th class="markdownTableHeadLeft">NPU Configuration   </th><th class="markdownTableHeadLeft">Description    </th></tr>
+<tr class="markdownTableRowOdd">
+<td class="markdownTableBodyLeft"><code>Board.clayer.yml</code>   </td><td class="markdownTableBodyLeft">None   </td><td class="markdownTableBodyLeft">Cortex-M system only, no Ethos-U NPU    </td></tr>
+<tr class="markdownTableRowEven">
+<td class="markdownTableBodyLeft"><code>Board-U55.clayer.yml</code>   </td><td class="markdownTableBodyLeft">Ethos-U55   </td><td class="markdownTableBodyLeft">Cortex-M system + Ethos-U55 NPU (256 MACs)    </td></tr>
+<tr class="markdownTableRowOdd">
+<td class="markdownTableBodyLeft"><code>Board-U65.clayer.yml</code>   </td><td class="markdownTableBodyLeft">Ethos-U65   </td><td class="markdownTableBodyLeft">Cortex-M system + Ethos-U65 NPU    </td></tr>
+<tr class="markdownTableRowEven">
+<td class="markdownTableBodyLeft"><code>Board-U85.clayer.yml</code>   </td><td class="markdownTableBodyLeft">Ethos-U85   </td><td class="markdownTableBodyLeft">Cortex-M system + Ethos-U85 NPU   </td></tr>
+</table>
+<p>Refer to <a href="https://open-cmsis-pack.github.io/cmsis-toolbox/build-overview/#software-layers">CMSIS-Toolbox - Software Layers</a> for more information on using layers in projects. </p>
 </div></div><!-- contents -->
 </div><!-- PageDoc -->
 </div><!-- doc-content -->

main/simulation/html/doxygen_crawl.html

@@ -10,6 +10,7 @@
 <body>
 <a href="annotated.html"/>
 <a href="avh_fvp_cmsis.html"/>
+<a href="avh_fvp_cmsis.html#autotoc_md0"/>
 <a href="classes.html"/>
 <a href="dir_05919b2fbcaf3de9fbeeb988d1e0d89f.html"/>
 <a href="dir_2e1d9f80bbf17079ea58b080a2a5eec7.html"/>

main/simulation/html/footer.js

@@ -1,3 +1,3 @@
 function writeFooter()  {
-    document.write('Generated on Wed Feb 11 2026 12:18:55 for Arm FVP models Version 2.2.0 by Arm Ltd. All rights reserved.');
+    document.write('Generated on Wed Feb 11 2026 15:07:41 for Arm FVP models Version 2.2.0 by Arm Ltd. All rights reserved.');
 };

main/simulation/html/group__arm__vio__pyenv.html

@@ -133,7 +133,7 @@
 </p>
 <p>Python environment for Arm FVPs. </p>
 <p>Arm FVPs require an installation of <b>Python 3.9</b> for running the Python virtual interfaces. If you are using a Windows machine you can use an embedded Python installation in FVPs root directory, otherwise a system installation is required. Additional Python packages can be added using <em>pip</em>. In case you are using embedded Python installation see section: <a class="el" href="#embedded-pip-vio">Install additional packages in embedded Python</a></p>
-<h1><a class="anchor" id="autotoc_md0"></a>
+<h1><a class="anchor" id="autotoc_md1"></a>
 Known issues</h1>
 <p>Some Python packages can't be imported directly in the Python virtual interfaces, because they are incompatible with Python sub-interpreters (e.g. <em>numpy</em>). Possible workaround for this issue is to split the Python module into client and server scripts.</p>
 <h1><a class="anchor" id="embedded-pip-vio"></a>

main/simulation/html/group__arm__vsi__pyenv.html

@@ -129,23 +129,23 @@
 </div><!--header-->
 <div class="contents">
 <p>Arm FVPs require an installation of <b>Python 3.9</b> for running the Python virtual interfaces. Additional Python packages can be added using <em>pip</em>.</p>
-<h1><a class="anchor" id="autotoc_md1"></a>
+<h1><a class="anchor" id="autotoc_md2"></a>
 Python requirements</h1>
 <p>The following packages are required on Linux systems (Ubuntu 20.04 and later):</p><ul>
 <li><em>libatomic1</em> </li>
 <li><em>python3.9</em> </li>
 <li><em>python3-pip</em> </li>
 </ul>
 <p>Run the following command to install required packages on Ubuntu: </p><div class="fragment"><div class="line">sudo apt install libatomic1 python3.9 python3-pip</div>
-</div><!-- fragment --><h1><a class="anchor" id="autotoc_md2"></a>
+</div><!-- fragment --><h1><a class="anchor" id="autotoc_md3"></a>
 Known issues</h1>
 <ul>
 <li>Some Python packages can't be imported directly in the Python virtual interfaces, because they are incompatible with Python sub-interpreters (e.g. <em>numpy</em>). Possible workaround for this issue is to split the Python module into client and server scripts.</li>
 </ul>
-<h1><a class="anchor" id="autotoc_md3"></a>
+<h1><a class="anchor" id="autotoc_md4"></a>
 Setup for FVPs older than 11.26</h1>
 <p>If you are using a Windows machine you can use an embedded Python installation in FVPs root directory, otherwise a system installation is required.</p>
-<h2><a class="anchor" id="autotoc_md4"></a>
+<h2><a class="anchor" id="autotoc_md5"></a>
 Install additional packages in embedded Python</h2>
 <p>By default the embedded Python installation on Windows does not support installation of new packages using pip. To enable installing new packages follow the steps described below.</p><ul>
 <li>Download <a href="https://bootstrap.pypa.io/get-pip.py">get-pip.py</a> to the FVPs root directory.</li>
@@ -156,7 +156,7 @@ <h2><a class="anchor" id="autotoc_md4"></a>
 <li>Install new packages using: <div class="fragment"><div class="line">.\python.exe -m pip install &lt;package&gt;</div>
 </div><!-- fragment --> The packages will be installed in <code>Lib\site-packages</code> subfolder.</li>
 </ul>
-<h2><a class="anchor" id="autotoc_md5"></a>
+<h2><a class="anchor" id="autotoc_md6"></a>
 Known issues</h2>
 <ul>
 <li>Fast Models (Version 11.22.39) available through vcpkg include a stripped-down version of libpython3.9 library on Linux systems. This can cause the Fast Model to close with an error (<em>VSI:Video:ImportError: No module named '_posixsubprocess'</em>) when running applications with VSI. <br  />

main/simulation/html/group__arm__vsi__video.html

@@ -165,7 +165,7 @@
 <img src="vsi_video_structure.png" alt=""/>
 <div class="caption">
 Video VSI Implementation Overview</div></div>
-<h2><a class="anchor" id="autotoc_md6"></a>
+<h2><a class="anchor" id="autotoc_md7"></a>
 Python requirements</h2>
 <p>In addition to the requirements listed in <a class="el" href="group__arm__vsi__pyenv.html">Python environment setup</a>, the VSI Video use case also requires installed OpenCV Python package. Run the following command to install it with pip: </p><div class="fragment"><div class="line">pip install opencv-python</div>
 </div><!-- fragment --><h2><a class="anchor" id="video_vsi_detail"></a>

main/simulation/html/hints.html

@@ -150,7 +150,7 @@ <h2><a class="anchor" id="uart"></a>
 <p>Below is useful information for using UART I/O on FVP targets:</p>
 <ul>
 <li><b>Concept</b>: <a href="https://developer.arm.com/documentation/100966/latest/Getting-Started-with-Fixed-Virtual-Platforms/Using-a-terminal-with-an-FVP">Using-a-terminal-with-an-FVP</a> and <a href="https://developer.arm.com/documentation/100964/1126/Fast-Models-components/Peripheral-components/TelnetTerminal">TelnetTerminal</a> explain the concept in details.</li>
-<li><b>UART Drivers</b>: CMSIS BSP packs listed in <a class="el" href="avh_fvp_cmsis.html">CMSIS-based projects</a> contain drivers for UART access on corresponding FVP targets.</li>
+<li><b>UART Drivers</b>: CMSIS BSP packs listed in <a class="el" href="avh_fvp_cmsis.html">CMSIS Support</a> contain drivers for UART access on corresponding FVP targets.</li>
 <li><b>Retarget to UART</b>: <a href="https://arm-software.github.io/CMSIS_6/latest/Compiler/index.html">CMSIS-Compiler component</a> implements retargeting of standard output functions, such as <code>printf()</code>.</li>
 <li><b>FVP parameters</b>: the default values of FVP configuration parameters related to UART and Telnet should already work correctly. Refer to the FVP and Fast Models documentation as well as reference examples for additional information.</li>
 <li><b>Windows setup</b> : On Windows you need to enable Telnet, as follows:<ul>