From cc5a7aee60661371c08db05154b38b39556e0b2f Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Mon, 7 Oct 2024 10:54:34 +0000
Subject: [PATCH] Update documentation for branch main

---
 main/FileSystem/File_Demo_Example.html     |  3 +-
 main/FileSystem/create_app.html            | 39 ++++++++-----
 main/FileSystem/examples.html              |  3 +-
 main/FileSystem/footer.js                  |  2 +-
 main/FileSystem/migration_guide.html       | 50 ++++++++++-------
 main/FileSystem/operation.html             | 51 ++++++++++-------
 main/FileSystem/resource_requirements.html | 65 +++++++++++-----------
 main/General/footer.js                     |  4 +-
 main/Network/footer.js                     |  2 +-
 main/USB/footer.js                         |  2 +-
 version.js                                 |  2 +-
 11 files changed, 128 insertions(+), 95 deletions(-)

diff --git a/main/FileSystem/File_Demo_Example.html b/main/FileSystem/File_Demo_Example.html
index 2965851c..0f51377d 100644
--- a/main/FileSystem/File_Demo_Example.html
+++ b/main/FileSystem/File_Demo_Example.html
@@ -161,7 +161,8 @@ <h2>Software Components Configuration Files</h2>
 </ul>
 <p>When a board layer is added to the project, corresponding configuration files for the board and device components will become available in the local <code>./Board/</code> directory.</p>
 <h2>Board Layer</h2>
-<p>In order to build the project it shall be extended with a compatible board layer that provides following interfaces as <a href="https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/ReferenceApplications.md#connections">connections</a>:</p><ul>
+<p>In order to build the project it shall be extended with a compatible board layer that provides following interfaces as <a href="https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/ReferenceApplications.md#connections">connections</a>:</p>
+<ul>
 <li><code>CMSIS_MCI</code>: CMSIS-Driver for Memory Card Interface</li>
 <li><code>CMSIS_VIO</code>: CMSIS-Driver for Virtual I/O interface</li>
 <li><code>STDIN</code>: Standard Input redirection</li>
diff --git a/main/FileSystem/create_app.html b/main/FileSystem/create_app.html
index bfc42ff1..24d0cefb 100644
--- a/main/FileSystem/create_app.html
+++ b/main/FileSystem/create_app.html
@@ -166,11 +166,13 @@ <h1><a class="anchor" id="fs_drives"></a>
 <p>The section <a class="el" href="operation.html#drive">Drives, Memory Devices and Drivers</a> shows the relationship between drive - memory device - and driver/interface.</p>
 <h2><a class="anchor" id="nor_usage"></a>
 NOR Flash Drive</h2>
-<p>For using a NOR Flash drive, a  <script>link_ext('Flash-API');</script> driver is required, which encapsulates either the Memory Bus interface or SPI (in which case an  <script>link_ext('SPI-API');</script> driver is required in addition):</p><ul>
+<p>For using a NOR Flash drive, a  <script>link_ext('Flash-API');</script> driver is required, which encapsulates either the Memory Bus interface or SPI (in which case an  <script>link_ext('SPI-API');</script> driver is required in addition):</p>
+<ul>
 <li>Set <b>File System:Drive:NOR</b> to at least '1' to use a NOR Flash drive (independently if it is using a memory bus or SPI interface).</li>
 <li>From the <b>CMSIS-Driver</b> Component, select an appropriate <b>Flash (API)</b> device. If your NOR Flash uses an SPI interface, select <b>SPI (API)</b> additionally.</li>
 </ul>
-<p>If your NOR Flash device is not listed, use one of the examples as a reference to implement a driver for your specific device:</p><ul>
+<p>If your NOR Flash device is not listed, use one of the examples as a reference to implement a driver for your specific device:</p>
+<ul>
 <li>AM29x800BB/<a href="https://www.farnell.com/datasheets/40281.pdf">M29W640FB</a> (Flash with 16-bit memory bus interface)</li>
 <li><a href="https://www.infineon.com/dgdl/Infineon-S29GL064N_S29GL032N_64_Mbit_32_Mbit_3_V_Page_Mode_MirrorBit_Flash-DataSheet-v03_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ed556fd548b">S29GL064Nx2</a> (Flash with 32-bit memory bus interface)</li>
 <li><a href="https://datasheet.octopart.com/AT45DB642D-CNU-Atmel-datasheet-9652374.pdf">AT45DB642D</a> (Flash with SPI interface using an SPI driver)</li>
@@ -206,12 +208,14 @@ <h2><a class="anchor" id="mc_usage"></a>
 <img src="fs_config_mc_0_h.png" alt=""/>
 <div class="caption">
 Memory Card Drive Configuration File</div></div>
-    <dl class="section note"><dt>Note</dt><dd><ul>
+    <blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
 <li>If your microcontroller device does not have a <b>CMSIS-Driver</b> for the <b>MCI (API)</b> or <b>SPI (API)</b>, you can try to develop your own one based on the  <script>link_ext('CMSIS-Driver-Ref');</script> documentation.</li>
 <li>The page <a class="el" href="operation.html#mc_control_layer">Memory Card Control Layer</a> lists all supported memory card types and gives further details on how to use these cards.</li>
-<li>General <a class="el" href="create_app.html#system_configuration">System Resource Configuration</a> requirements apply.</li>
+<li>General <a class="el" href="create_app.html#system_configuration">System Resource Configuration</a> requirements apply. </li>
 </ul>
-</dd></dl>
+</blockquote>
 <h2><a class="anchor" id="usb_usage"></a>
 USB Flash Drive</h2>
 <ul>
@@ -224,11 +228,13 @@ <h2><a class="anchor" id="usb_usage"></a>
 <img src="fs_config_usb_0_h.png" alt=""/>
 <div class="caption">
 USB Host Mass Storage Class Drive Configuration File</div></div>
-    <dl class="section note"><dt>Note</dt><dd><ul>
+    <blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
 <li>If your microcontroller device does not have a <b>CMSIS-Driver</b> for the <b>USB Host (API)</b>, you can try to develop your own one based on the  <script>link_ext('CMSIS-Driver-Ref');</script> documentation.</li>
-<li>General <a class="el" href="create_app.html#system_configuration">System Resource Configuration</a> requirements apply.</li>
+<li>General <a class="el" href="create_app.html#system_configuration">System Resource Configuration</a> requirements apply. </li>
 </ul>
-</dd></dl>
+</blockquote>
 <h2><a class="anchor" id="nand_usage"></a>
 NAND Flash Drive</h2>
 <ul>
@@ -240,14 +246,16 @@ <h2><a class="anchor" id="nand_usage"></a>
 <img src="fs_config_nand_0_h.png" alt=""/>
 <div class="caption">
 NAND Flash Drive Configuration File</div></div>
-    <dl class="section note"><dt>Note</dt><dd><ul>
+    <blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
 <li>If your microcontroller device does not have a <b>CMSIS-Driver</b> for the <b>NAND (API)</b>, you can try to develop your own one based on the  <script>link_ext('CMSIS-Driver-Ref');</script> documentation.</li>
 <li>The page <a class="el" href="operation.html#nand_flash_TL">NAND Flash Translation Layer</a> describes additional features specific to these devices.</li>
 <li>Using a <b>NAND (API)</b> driver, you can use any NAND Flash device with an 8-/16-bit memory bus interface for data storage.</li>
 <li>NAND Flashes with SPI interface (Serial NAND) are currently <em>not supported</em> by the File System Component.</li>
-<li>General <a class="el" href="create_app.html#system_configuration">System Resource Configuration</a> requirements apply.</li>
+<li>General <a class="el" href="create_app.html#system_configuration">System Resource Configuration</a> requirements apply. </li>
 </ul>
-</dd></dl>
+</blockquote>
 <h1><a class="anchor" id="fs_configuration"></a>
 File System Configuration</h1>
 <p>The File System configuration file <code>FS_Config.h</code> contains settings for the amount of files that can be open at the same time:</p>
@@ -266,7 +274,8 @@ <h1><a class="anchor" id="hw_configuration"></a>
     <dl class="section note"><dt>Note</dt><dd>Consult the device's user manual or hardware reference guide for more details.</dd></dl>
 <h1><a class="anchor" id="system_configuration"></a>
 System Resource Configuration</h1>
-<p>For proper operation, the File System Component requires some system configuration settings. The requirements are:</p><ul>
+<p>For proper operation, the File System Component requires some system configuration settings. The requirements are:</p>
+<ul>
 <li>Minimum <b>heap size of 512 + 96 Bytes for each opened file</b>. If you want to be able to have three files open at the same time, you need to set a heap size of at least 3 * (512+96) Bytes = 1824 Bytes. This can be configured in the device's <code>startup_device.s</code> file (<code>Heap_Size</code>).</li>
 <li>As the File System Component is not creating any additional threads, you need to add thread stack size to the calling thread. This calling thread can be the main thread, a thread with a default stack size or a thread with a user provided stack size. Changing the size for these threads can be done in the  <script>link_ext('RTX-Conf-CM5');</script> file.</li>
 <li>Each opened file is protected with a mutex in order to ensure thread-safe operation. When working with file functions from the standard C library, you need to ensure enough mutex objects available for the file stream operations in the standard library system. File System component's <a class="el" href="resource_requirements.html">Resource Requirements</a> section explains how to determine the right setting in detail. Adjusting the number of mutex objects available for standard library system can be done in the  <script>link_ext('RTX-Conf-CM5');</script> file.</li>
@@ -284,7 +293,8 @@ <h2><a class="anchor" id="fsEvrSupport"></a>
 Event Recorder Support</h2>
 <p> <script>link_ext('Event-Recorder-About');</script> is a powerful tool that provides visibility to the dynamic execution of the program.</p>
 <p>The File System Component generates <a class="el" href="group__evr__gr.html">a broad set of Debug Events</a> for the Event Recorder and implements required infrastructure to interface with it.</p>
-<p>To use the Event Recorder it is required to create an image with event generation support. The necessary steps are:</p><ol type="1">
+<p>To use the Event Recorder it is required to create an image with event generation support. The necessary steps are:</p>
+<ol type="1">
 <li> <script>link_ext('Event-Recorder-Enable');</script>: in the RTE management dialog enable the software component <b>CMSIS-View:Event Recorder</b>.</li>
 <li>Ensure that Event Recorder is initialized preferably by  <script>link_ext('RTX5-Event-Recorder-Config');</script> if CMSIS-RTOS2 RTX v5 is used, or alternatively by calling the function  <script>link_ext('Event-Recorder-Initialize-Func');</script> in the application code.</li>
 <li><a class="el" href="create_app.html#fsEvrConfig">Event Recorder Configuration</a>: if necessary, adjust default Event Recorder configuration.</li>
@@ -301,7 +311,8 @@ <h3><a class="anchor" id="fsEvrConfig"></a>
 <img src="fs_debug_h.png" alt=""/>
 <div class="caption">
 FS_Debug.h file for event generation configuration</div></div>
-    <p>The following settings are available for event generation configuration of each module:</p><ul>
+    <p>The following settings are available for event generation configuration of each module:</p>
+<ul>
 <li><b>Off</b> means no events will be generated by the module</li>
 <li><b>Errors</b> means only error events will be generated by the module</li>
 <li><b>Errors + API</b> means error and API call events will be generated by the module</li>
diff --git a/main/FileSystem/examples.html b/main/FileSystem/examples.html
index f41d6a1d..47a35fa6 100644
--- a/main/FileSystem/examples.html
+++ b/main/FileSystem/examples.html
@@ -128,7 +128,8 @@
   <div class="headertitle"><div class="title">Examples </div></div>
 </div><!--header-->
 <div class="contents">
-<div class="textblock"><p><a class="anchor" id="md_src_examples"></a> The File System Component is used in many different applications and examples. One stand-alone example is available to demonstrate the usage of the File System. Other examples use the File System Component in conjunction with other Components (such as USB or Network for example).</p><ul>
+<div class="textblock"><p><a class="anchor" id="md_src_examples"></a> The File System Component is used in many different applications and examples. One stand-alone example is available to demonstrate the usage of the File System. Other examples use the File System Component in conjunction with other Components (such as USB or Network for example).</p>
+<ul>
 <li><a class="el" href="File_Demo_Example.html">File Demo Example</a> shows the basic functionality of the File System.</li>
 <li><a href="../USB/usbd_example_msc.html">USB Device Mass Storage</a> shows how to create an USB MSC Device that is recognized by an USB Host controller.</li>
 <li><a href="../USB/usbh_example_msc.html">USB Host Mass Storage</a> explains how to access file system data from an attached USB memory device.</li>
diff --git a/main/FileSystem/footer.js b/main/FileSystem/footer.js
index aac6d14e..29264d48 100644
--- a/main/FileSystem/footer.js
+++ b/main/FileSystem/footer.js
@@ -3,5 +3,5 @@ function writeHeader() {
 };
 
 function writeFooter()  {
-    document.write('Generated on Mon Oct  7 2024 10:19:20 for File System Component 8.0.0. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
+    document.write('Generated on Mon Oct  7 2024 10:53:28 for File System Component 8.0.0. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
 };
diff --git a/main/FileSystem/migration_guide.html b/main/FileSystem/migration_guide.html
index a9c0ed53..f2166ac5 100644
--- a/main/FileSystem/migration_guide.html
+++ b/main/FileSystem/migration_guide.html
@@ -138,26 +138,33 @@ <h1><a class="anchor" id="migrate_components"></a>
 <p>There are three major changes in File System version 8 that affect how File System components get selected.</p>
 <ol type="1">
 <li><p class="startli">Bundle <b>MDK</b> has replaced bundles <b>MDK-Pro</b> and <b>MDK-Plus</b></p>
-<p class="startli">Where applicable replace components: </p><div class="fragment"><div class="line">Keil::File System&amp;MDK-Pro</div>
+<p class="startli">Where applicable replace components:</p>
+<div class="fragment"><div class="line">Keil::File System&amp;MDK-Pro</div>
 <div class="line">or</div>
 <div class="line">Keil::File System&amp;MDK-Plus</div>
-</div><!-- fragment --><p class="startli">with components that reference bundle <b>MDK</b>: </p><div class="fragment"><div class="line">Keil::File System&amp;MDK</div>
+</div><!-- fragment --><p class="startli">with components that reference bundle <b>MDK</b>:</p>
+<div class="fragment"><div class="line">Keil::File System&amp;MDK</div>
 </div><!-- fragment --></li>
 <li><p class="startli">Legacy Standard C Library retarget components are no longer supported</p>
 <p class="startli">This means that using components from the CMSIS-Compiler is now mandatory. Nevertheless, migrating from Compiler to CMSIS-Compiler components is straightforward.</p>
-<p class="startli">To migrate your project replace component: </p><div class="fragment"><div class="line">Keil::Compiler::I/O:File&amp;File System</div>
-</div><!-- fragment --><p class="startli">with components from CMSIS-Compiler class: </p><div class="fragment"><div class="line">ARM::CMSIS-Compiler:CORE</div>
+<p class="startli">To migrate your project replace component:</p>
+<div class="fragment"><div class="line">Keil::Compiler::I/O:File&amp;File System</div>
+</div><!-- fragment --><p class="startli">with components from CMSIS-Compiler class:</p>
+<div class="fragment"><div class="line">ARM::CMSIS-Compiler:CORE</div>
 <div class="line">and</div>
 <div class="line">ARM::CMSIS-Compiler:File Interface:MDK-MW File System</div>
 </div><!-- fragment --><p class="startli">Components from <b>Compiler</b> and <b>CMSIS-Compiler</b> are incompatible and cannot coexist hence all other components from Compiler class must also be migrated to components from CMSIS-Compiler:</p>
-<p class="startli">Migrate components: </p><div class="fragment"><div class="line">Keil::Compiler:I/O:STDERR&amp;{Cvariant}  -&gt;  ARM::CMSIS-Compiler:STDERR:{Csub}</div>
+<p class="startli">Migrate components:</p>
+<div class="fragment"><div class="line">Keil::Compiler:I/O:STDERR&amp;{Cvariant}  -&gt;  ARM::CMSIS-Compiler:STDERR:{Csub}</div>
 <div class="line">Keil::Compiler:I/O:STDIN&amp;{Cvariant}   -&gt;  ARM::CMSIS-Compiler:STDIN:{Csub}</div>
 <div class="line">Keil::Compiler:I/O:STDOUT&amp;{Cvariant}  -&gt;  ARM::CMSIS-Compiler:STDOUT:{Csub}</div>
 <div class="line">Keil::Compiler:I/O:TTY&amp;{Cvariant}     -&gt;  ARM::CMSIS-Compiler:TTY:{Csub}</div>
 </div><!-- fragment --></li>
 <li><p class="startli"><b>Event Recorder</b> component is now part of <b>CMSIS-View</b> class</p>
-<p class="startli">If your project is configured for debugging then you need to replace component: </p><div class="fragment"><div class="line">Keil::Compiler:Event Recorder</div>
-</div><!-- fragment --><p class="startli">with component from CMSIS-View class: </p><div class="fragment"><div class="line">ARM::CMSIS-View:Event Recorder</div>
+<p class="startli">If your project is configured for debugging then you need to replace component:</p>
+<div class="fragment"><div class="line">Keil::Compiler:Event Recorder</div>
+</div><!-- fragment --><p class="startli">with component from CMSIS-View class:</p>
+<div class="fragment"><div class="line">ARM::CMSIS-View:Event Recorder</div>
 </div><!-- fragment --></li>
 </ol>
 <h1><a class="anchor" id="migrate_config"></a>
@@ -165,24 +172,29 @@ <h1><a class="anchor" id="migrate_config"></a>
 <p>In general two major changes were made to the File System version 8 configuration files and affect how File System gets configured.</p>
 <ol type="1">
 <li><p class="startli">The core configuration has been moved from C source file to C header file</p>
-<p class="startli">To migrate configuration of an existing project use compare/merge tool on the following files: </p><div class="fragment"><div class="line">FS_Config.c  and  FS_Config.h</div>
-</div><!-- fragment --> <blockquote class="doxtable">
+<p class="startli">To migrate configuration of an existing project use compare/merge tool on the following files:</p>
+<div class="fragment"><div class="line">FS_Config.c  and  FS_Config.h</div>
+</div><!-- fragment --></li>
+</ol>
+<blockquote class="doxtable">
 <p>&zwj;Note: FS_Config.h does not have configuration for Initial Current Drive anymore. To understand how current drive is set see chapter <a class="el" href="operation.html#cur_sys_drive">Current Drive</a>. </p>
 </blockquote>
-</li>
+<ol type="1">
 <li><p class="startli">Drive configuration changed the way how drive cache and drive buffer placement works</p>
 <p class="startli">On microcontrollers where DMA has limited access to memory areas one must place drive buffers into the appropriate memory in order for peripheral driver to work. In File System version 8 this is supported by placing drive buffer in a dedicated section which must be properly located with the toolchain linker script.</p>
 <p class="startli">The latest drive configuration files contain a define named **_CACHE_SECTION** where one can define the section name.</p>
-<p class="startli">For example: </p><div class="fragment"><div class="line">//     &lt;s&gt;Section Name</div>
-<div class="line">//     &lt;i&gt;Define the name of the section for the drive cache and drive buffers.</div>
-<div class="line">//     &lt;i&gt;Linker script shall have this section defined.</div>
-<div class="line">#define MC0_CACHE_SECTION       &quot;.driver.mci0&quot;</div>
+<p class="startli">For example:</p>
+<div class="fragment"><div class="line"><span class="comment">//     &lt;s&gt;Section Name</span></div>
+<div class="line"><span class="comment">//     &lt;i&gt;Define the name of the section for the drive cache and drive buffers.</span></div>
+<div class="line"><span class="comment">//     &lt;i&gt;Linker script shall have this section defined.</span></div>
+<div class="line"><span class="preprocessor">#define MC0_CACHE_SECTION       &quot;.driver.mci0&quot;</span></div>
 </div><!-- fragment --><p class="startli">When using RAM drive one can move the file system data buffer (buffer that holds directories, files and files content) into a specific memory. The latest drive configuration file supports this by using define **_SECTION**.</p>
-<p class="startli">The define for RAM drive 0 looks like shown below: </p><div class="fragment"><div class="line">//     &lt;s&gt;Section Name</div>
-<div class="line">//     &lt;i&gt;Define the name of the section for the file system buffer.</div>
-<div class="line">//     &lt;i&gt;Linker script shall have this section defined.</div>
-<div class="line">#define RAM0_SECTION           &quot;.filesystem.ram0&quot;</div>
-</div><!-- fragment --><p> To migrate configuration of an existing project use compare/merge tool on drive configuration files and update toolchain linker script to support defined sections. </p>
+<p class="startli">The define for RAM drive 0 looks like shown below:</p>
+<div class="fragment"><div class="line"><span class="comment">//     &lt;s&gt;Section Name</span></div>
+<div class="line"><span class="comment">//     &lt;i&gt;Define the name of the section for the file system buffer.</span></div>
+<div class="line"><span class="comment">//     &lt;i&gt;Linker script shall have this section defined.</span></div>
+<div class="line"><span class="preprocessor">#define RAM0_SECTION           &quot;.filesystem.ram0&quot;</span></div>
+</div><!-- fragment --><p class="startli">To migrate configuration of an existing project use compare/merge tool on drive configuration files and update toolchain linker script to support defined sections. </p>
 </li>
 </ol>
 </div></div><!-- contents -->
diff --git a/main/FileSystem/operation.html b/main/FileSystem/operation.html
index 5565f0ca..c9b72374 100644
--- a/main/FileSystem/operation.html
+++ b/main/FileSystem/operation.html
@@ -129,7 +129,8 @@
 </div><!--header-->
 <div class="contents">
 <div class="textblock"><p><a class="anchor" id="md_src_operation"></a> The File System Component provides functions to create, save, read, and modify files. The Retarget Interface of the C/C++ compiler run-time library allows the usage of ANSI C standard file I/O functions. The File System Component is designed for Cortex-M processor-based devices and requires an CMSIS-RTOS compliant real-time operating system for thread-safe operation.</p>
-<p>The File System Component consists of two different file systems, placed on top of different layers, depending on the media type:</p><ul>
+<p>The File System Component consists of two different file systems, placed on top of different layers, depending on the media type:</p>
+<ul>
 <li><a class="el" href="operation.html#fat_fs">FAT File System</a> (using FAT12, FAT16, or FAT32) is used for <a class="el" href="create_app.html#mc_usage">memory card</a> devices, <a class="el" href="create_app.html#usb_usage">USB Memory sticks</a>, <a class="el" href="create_app.html#nand_usage">NAND Flash</a> devices, and <a class="el" href="create_app.html#ram_usage">RAM disks</a>. FAT is a standard file system used on many computers.</li>
 <li><a class="el" href="operation.html#emb_fs">Embedded File System (EFS)</a> is optimized for <a class="el" href="create_app.html#nor_usage">NOR Flash</a> memory devices.</li>
 <li><a class="el" href="operation.html#journaling_fat">Journaling for the FAT File System</a> is an extension to the <a class="el" href="operation.html#fat_fs">FAT File System</a> that helps to keep the file system consistent in an embedded system.</li>
@@ -155,7 +156,8 @@ <h1><a class="anchor" id="fs_usage"></a>
 <li><b>FAT, EFS Media</b>: the FAT file system supports Memory Cards (MC), NAND Flash, and USB memory sticks, and RAM disks. The Embedded File System (EFS) supports NOR Flash devices.</li>
 <li><b>Drivers</b> The File System Core accesses the drives via CMSIS-Drivers that are typically part of the Device Family Pack. Every drive uses dedicated driver.</li>
 </ul>
-<p>The configuration steps and files that are needed to create applications for the different devices are explained here:</p><ul>
+<p>The configuration steps and files that are needed to create applications for the different devices are explained here:</p>
+<ul>
 <li><a class="el" href="create_app.html#nor_usage">NOR Flash Drive</a></li>
 <li><a class="el" href="create_app.html#ram_usage">RAM Disk Drive</a></li>
 <li><a class="el" href="create_app.html#mc_usage">Memory Card Drive</a></li>
@@ -175,9 +177,9 @@ <h1><a class="anchor" id="drive"></a>
 <tr class="markdownTableHead">
 <th class="markdownTableHeadLeft">Drive   </th><th class="markdownTableHeadCenter">File System   </th><th class="markdownTableHeadLeft">Drive Type   </th><th class="markdownTableHeadNone">CMSIS-Driver/Interface    </th></tr>
 <tr class="markdownTableRowOdd">
-<td class="markdownTableBodyLeft">"F:" or "F0:"   </td><td class="markdownTableBodyCenter"><a class="el" href="operation.html#emb_fs">EFS</a>   </td><td class="markdownTableBodyLeft">NOR Flash drive 0   </td><td class="markdownTableBodyNone"> <script>link_ext('Flash-API');</script> (Memory Bus or  <script>link_ext('SPI-API');</script>    </td></tr>
+<td class="markdownTableBodyLeft">"F:" or "F0:"   </td><td class="markdownTableBodyCenter"><a class="el" href="operation.html#emb_fs">EFS</a>   </td><td class="markdownTableBodyLeft">NOR Flash drive 0   </td><td class="markdownTableBodyNone"> <script>link_ext('Flash-API');</script> (Memory Bus or  <script>link_ext('SPI-API');</script>)    </td></tr>
 <tr class="markdownTableRowEven">
-<td class="markdownTableBodyLeft">"F1:"   </td><td class="markdownTableBodyCenter"><a class="el" href="operation.html#emb_fs">EFS</a>   </td><td class="markdownTableBodyLeft">NOR Flash drive 1   </td><td class="markdownTableBodyNone"> <script>link_ext('Flash-API');</script> (Memory Bus or  <script>link_ext('SPI-API');</script>    </td></tr>
+<td class="markdownTableBodyLeft">"F1:"   </td><td class="markdownTableBodyCenter"><a class="el" href="operation.html#emb_fs">EFS</a>   </td><td class="markdownTableBodyLeft">NOR Flash drive 1   </td><td class="markdownTableBodyNone"> <script>link_ext('Flash-API');</script> (Memory Bus or  <script>link_ext('SPI-API');</script>)    </td></tr>
 <tr class="markdownTableRowOdd">
 <td class="markdownTableBodyLeft">"R:" or "R0:"   </td><td class="markdownTableBodyCenter"><a class="el" href="operation.html#fat_fs">FAT</a>   </td><td class="markdownTableBodyLeft">RAM drive   </td><td class="markdownTableBodyNone">N/A    </td></tr>
 <tr class="markdownTableRowEven">
@@ -193,22 +195,26 @@ <h1><a class="anchor" id="drive"></a>
 <tr class="markdownTableRowOdd">
 <td class="markdownTableBodyLeft">"N1:"   </td><td class="markdownTableBodyCenter"><a class="el" href="operation.html#fat_fs">FAT</a>   </td><td class="markdownTableBodyLeft">NAND Flash drive 1   </td><td class="markdownTableBodyNone"> <script>link_ext('NAND-API');</script> (Memory Bus)   </td></tr>
 </table>
-<dl class="section note"><dt>Note</dt><dd><ul>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
 <li>NOR Flash is typically connected over Memory Bus or SPI. For using a NOR Flash drive, a Flash driver is required which encapsulates either the Memory Bus interface or SPI (in which case an SPI driver required in addition).</li>
 <li>The Middleware Component contains example drivers for Flash devices that can be used to implement other device drivers if required. The examples are: AM29x800BB/<a href="https://www.farnell.com/datasheets/40281.pdf">M29W640FB</a> (Flash with 16-bit memory bus interface), <a href="https://www.infineon.com/dgdl/Infineon-S29GL064N_S29GL032N_64_Mbit_32_Mbit_3_V_Page_Mode_MirrorBit_Flash-DataSheet-v03_00-EN.pdf">S29GL064Nx2</a> (Flash with 32-bit memory bus interface), and <a href="https://datasheet.octopart.com/AT45DB642D-CNU-Atmel-datasheet-9652374.pdf">AT45DB642D</a> (Flash with SPI interface using an SPI driver).</li>
 <li>Other drives (memory card, USB memory device, NAND Flash) require appropriate CMSIS-Driver for the microcontroller device. If no suitable CMSIS-Driver is available for your selected device, you may create the required Flash interface driver. Refer to the  <script>link_ext('CMSIS-Driver-Ref');</script> for details.</li>
-<li>Currently, using NAND Flash devices with SPI interface (Serial NAND) <em>is not supported</em>.</li>
+<li>Currently, using NAND Flash devices with SPI interface (Serial NAND) <em>is not supported</em>. </li>
 </ul>
-</dd></dl>
+</blockquote>
 <h2><a class="anchor" id="cur_sys_drive"></a>
 Current Drive</h2>
 <p>The <b>Current Drive</b> defines the drive used when the filename itself does not specify the drive or when functions that expect a drive are called with an empty ("") string.</p>
 <p>If there is only one drive enabled in the system then it automatically becomes the "Current Drive". Alternatively, when there are multiple drives enabled, the one with the drive letter that is first in alphabetical order is set as the "Current Drive". The <a class="el" href="operation.html#cur_sys_drive">Current Drive</a> can be changed during run-time using the function <a class="el" href="group__utility__routines.html#ga75a680af8cbd2e2fae87d99d9ab50e11">fchdrive</a>.</p>
-<dl class="section note"><dt>Note</dt><dd><ul>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
 <li>Define <code>FS_INITIAL_CDRIVE</code> can be used to define initial current drive at build time.</li>
-<li>Set <code>FS_INITIAL_CDRIVE</code> to one of the following values: 0(F0), 1(F1), 2(M0), 3(M1), 4(N0), 5(N1), 6(R0), 9(R1), 7(U0), 8(U1)</li>
+<li>Set <code>FS_INITIAL_CDRIVE</code> to one of the following values: 0(F0), 1(F1), 2(M0), 3(M1), 4(N0), 5(N1), 6(R0), 9(R1), 7(U0), 8(U1) </li>
 </ul>
-</dd></dl>
+</blockquote>
 <h1><a class="anchor" id="fat_fs"></a>
 FAT File System</h1>
 <p>The FAT File System was initially used on PC operating systems such as MS-DOS and early versions of Microsoft Windows. Still, it is widely used on <b>USB memory sticks</b> or <b>memory cards</b> for file storage. It is simple, robust and offers good performance especially in embedded applications.</p>
@@ -216,7 +222,8 @@ <h1><a class="anchor" id="fat_fs"></a>
 <p>Since the first implementation, the maximum number of clusters of a drive has increased dramatically, and so the number of bits used to identify each cluster has grown. The versions of the FAT format are named after the number of table element bits: <b>FAT12</b>, <b>FAT16</b>, and <b>FAT32</b>. Each of these variants is is supported by the File System Component.</p>
 <h2><a class="anchor" id="fat_layout"></a>
 Layout</h2>
-<p>The actual FAT file system is made up of four different sections: </p><table class="markdownTable">
+<p>The actual FAT file system is made up of four different sections:</p>
+<table class="markdownTable">
 <tr class="markdownTableHead">
 <th class="markdownTableHeadLeft">Section   </th><th class="markdownTableHeadLeft">Description    </th></tr>
 <tr class="markdownTableRowOdd">
@@ -272,16 +279,16 @@ <h2><a class="anchor" id="lfn_sfn_handling"></a>
 Long and Short File Name handling</h2>
 <p>File System Component is provided with the long (LFN) and short (SFN or 8.3) filename support. Since there is no compulsory algorithm for creating the 8.3 name from an LFN, File System Component uses convention described below.</p>
 <ul>
-<li>Uppercased or lowercased name which is 8.3 valid, is stored uppercased in a single SFN entry<ul>
+<li>The name in uppercase or lowercase, which is 8.3 valid, is stored in uppercase in a single SFN entry<ul>
 <li>Example: "TEXTFILE.TXT" is stored as "TEXTFILE.TXT" (SFN)</li>
 <li>Example: "textfile.txt" is stored as "TEXTFILE.TXT" (SFN)</li>
 </ul>
 </li>
-<li>Mixedcase name which is 8.3 valid, is stored mixed-case in LFN entry and SFN entry is created, which is concluded with tilde and a numeric value.<ul>
+<li>A mixed-case name, which is 8.3 valid, is stored as mixed-case in LFN entry and SFN entry is created, which is concluded with tilde and a numeric value.<ul>
 <li>Example: "TextFile.txt" is stored as "TextFile.txt" (LFN) and "TEXTFI~1.TXT" (SFN)</li>
 </ul>
 </li>
-<li>Name which is not 8.3 valid is stored in LFN entry and SFN entry. Name writen in SFN entry is uppercased, stripped of invalid 8.3 characters which are replaced with underscore "_" and concluded with tilde and a numeric value.<ul>
+<li>Name which is not 8.3 valid is stored in LFN entry and SFN entry. Name written in SFN entry is in uppercase, stripped of invalid 8.3 characters, which are replaced with underscore "_" and concluded with tilde and a numeric value.<ul>
 <li>Example: "Tex+File.txt" is stored as "Tex+File.txt" (LFN) and "TEX_FI~1.TXT (SFN)"</li>
 </ul>
 </li>
@@ -444,6 +451,12 @@ <h3><a class="anchor" id="autotoc_md7"></a>
 <li>define lock operation by setting member <code>.flags</code> to <a class="el" href="rl__fs_8h.html#a615e2a30a6833ad0ad79e7186cbbad1b">FS_DEVICE_LOCK_UNLOCK</a></li>
 </ul>
 <p>When operation executes successfully, data access protection is activated. All read/write accesses are rejected.</p>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b> It is possible to set password and lock the card in a single step:</p>
+<ul>
+<li>define set password and lock the card operation by setting member <code>.flags</code> to (<a class="el" href="rl__fs_8h.html#a4dcee13db9af51353d3509331d6ded8f">FS_DEVICE_SET_PASSWORD</a> | <a class="el" href="rl__fs_8h.html#a615e2a30a6833ad0ad79e7186cbbad1b">FS_DEVICE_LOCK_UNLOCK</a>) </li>
+</ul>
+</blockquote>
 <p><b>Unlock the card:</b></p>
 <ul>
 <li>assign password buffer to member <code>.password</code></li>
@@ -457,15 +470,13 @@ <h3><a class="anchor" id="autotoc_md7"></a>
 <li>define force erase operation by setting member <code>.flags</code> to <a class="el" href="rl__fs_8h.html#a94e215f84b9683736f1c6d7a574d8875">FS_DEVICE_ERASE</a></li>
 </ul>
 <p>When operation executes successfully, all the card data content is erased along with the current password.</p>
-<dl class="section note"><dt>Note</dt><dd>It is possible to set password and lock the card in a single step:</dd></dl>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
 <ul>
-<li>define set password and lock the card operation by setting member <code>.flags</code> to (<a class="el" href="rl__fs_8h.html#a4dcee13db9af51353d3509331d6ded8f">FS_DEVICE_SET_PASSWORD</a> | <a class="el" href="rl__fs_8h.html#a615e2a30a6833ad0ad79e7186cbbad1b">FS_DEVICE_LOCK_UNLOCK</a>)</li>
-</ul>
-<dl class="section note"><dt>Note</dt><dd><ul>
 <li>SD and MMCA specification also allows to replace the password in a single step. This is not supported by the FileSystem library, since it is known that various devices have issues with the interpretation of this operation. Therefore, when changing the password, old one must be first cleared and then new password can be set.</li>
-<li>Is is also recommended to unlock the device before resetting the password.</li>
+<li>Is is also recommended to unlock the device before resetting the password. </li>
 </ul>
-</dd></dl>
+</blockquote>
 <p>To successfully <a class="el" href="group__system__routines.html#gade92b7c5b374fb1485f2f9faa7259f27">mount</a> locked memory card and gain read/write data access, password management information must be provided from the user application:</p>
 <ul>
 <li><a class="el" href="group__media__support__routines.html#gace19ffe245efca9f6ee93e744041b2f1">fs_mc_lock_unlock</a> function is used to return pointer to <a class="el" href="rl__fs_8h.html#structfsLockUnlock">fsLockUnlock</a> structure containing password information</li>
diff --git a/main/FileSystem/resource_requirements.html b/main/FileSystem/resource_requirements.html
index d09fac76..13de3f51 100644
--- a/main/FileSystem/resource_requirements.html
+++ b/main/FileSystem/resource_requirements.html
@@ -131,35 +131,41 @@
 <div class="textblock"><p><a class="anchor" id="md_src_resource_requirements"></a> This section describes the resource requirements of the <b>File System</b> component. The actual requirements depend on the features used in the application. Therefore, the numbers provided here are guidelines only and the actual numbers may differ.</p>
 <h1><a class="anchor" id="fs_stack_req"></a>
 Stack Requirements</h1>
-<p>The File System component receives events sent from the interrupt service routine (ISR) of the drivers of the different drives. The stack requirements for the ISR are typically less than 512 Bytes. The stack requirements for ISR are configured in the <code>startup_device.s</code> file located under the <b>Device</b> component class.</p>
+<p>The File System component receives events sent from the interrupt service routine (ISR) of the drivers of the different drives. The stack requirements for the ISR are typically less than 512 Bytes.</p>
 <table class="markdownTable">
 <tr class="markdownTableHead">
 <th class="markdownTableHeadLeft">Option (under section Stack Configuration)   </th><th class="markdownTableHeadLeft">Increase Value by    </th></tr>
 <tr class="markdownTableRowOdd">
 <td class="markdownTableBodyLeft">Stack Size (in Bytes)   </td><td class="markdownTableBodyLeft">+ 512 for Driver of a Drive   </td></tr>
 </table>
-<dl class="section note"><dt>Note</dt><dd><ul>
-<li>When using a CMSIS-RTOS, the Stack Size in the startup_*device*.s file configures only the stack space that is used by exception and interrupt service routines of the drivers. The stack size requirements depend on the maximum nesting of exception and ISR execution and therefore on the priority settings of the various interrupt and exception sources.</li>
-<li>If you have multiple drives configured in your system with the same interrupt priority, you only need to add the stack of the drive with the largest requirement. If you have drives with nested interrupts (different priorities), you need to add the sum of all stack requirements.</li>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
+<li>Stack size for the ISRs is typically configured in the application <code>linker script</code> or device <code>startup_device.s</code>.</li>
+<li>The stack size for the ISRs configures only the stack space that is used by exception and interrupt service routines of the drivers. The stack size requirements depend on the maximum nesting of exception and ISR execution and therefore on the priority settings of the various interrupt and exception sources. The stack size of the thread that calls FileSystem API function is configured in configuration file specific to the CMSIS-RTOS2 in use.</li>
+<li>If you have multiple drives configured in your system with the same interrupt priority, you only need to add the stack of the drive with the largest requirement. If you have drives with nested interrupts (different priorities), you need to add the sum of all stack requirements. </li>
 </ul>
-</dd></dl>
+</blockquote>
 <h1><a class="anchor" id="fs_heap_req"></a>
 Heap Requirements</h1>
-<p>Heap is used by memory allocation functions. It is also configured in the <code>startup_device.s</code> file located under the <b>Device</b> component class. For every simultaneously opened file, you need to configure 512 + 96 Bytes of additional heap. If you wish to have three files open simultaneously, you need to configure an additional heap size of 3 x (512 + 96) Bytes.</p>
+<p>Heap is used by the standard C library memory allocation functions. The amount of heap required therefore depends on the toolchain used to build the application image. The table below shows the heap requirements per simultaneously opened file. If you wish to have three files open simultaneously, the value from the table must be multiplied by three.</p>
 <table class="markdownTable">
 <tr class="markdownTableHead">
-<th class="markdownTableHeadLeft">Option (under section Heap Configuration)   </th><th class="markdownTableHeadLeft">Increase Value by    </th></tr>
+<th class="markdownTableHeadLeft">Toolchain   </th><th class="markdownTableHeadLeft">Increase Value by    </th></tr>
 <tr class="markdownTableRowOdd">
-<td class="markdownTableBodyLeft">Heap Size (in Bytes)   </td><td class="markdownTableBodyLeft">+ (512 + 96) for each open file   </td></tr>
+<td class="markdownTableBodyLeft">Arm Compiler 6   </td><td class="markdownTableBodyLeft">+ (512 + 96) for each open file    </td></tr>
+<tr class="markdownTableRowEven">
+<td class="markdownTableBodyLeft">GCC   </td><td class="markdownTableBodyLeft">+ (1024 + 64) for each open file   </td></tr>
 </table>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<p>Heap is used to hold the file descriptor and file data buffer. The size of data buffer can be changed with function <code>setvbuf</code> which is part of the standard C library. </p>
+</blockquote>
 <h1><a class="anchor" id="fs_rtos_req"></a>
 CMSIS-RTOS Requirements</h1>
 <h2><a class="anchor" id="autotoc_md13"></a>
 Thread Stack Requirements</h2>
-<p>Although the File System component requires a CMSIS-RTOS to be present, it is not creating any additional threads.</p>
-<p><b>Using CMSIS-RTOS RTX v5</b></p>
-<p>The calling thread can be a thread with a default stack size (dynamic memory) or a thread with a complete stack or only stack size provided using <code>osThreadAttr_t</code> structure (static or dynamic memory).</p>
-<p>For the additional required stack size, please refer to the following table:</p>
+<p>Although the File System component requires a CMSIS-RTOS to be present, it is not creating any additional threads. Stack consumption depends greatly on the compiler optimization level. The table below shows approximate stack size required by the FileSystem functions when compiled for production ready application with high optimization level. For debugging purposes, with low or disabled optimization, the stack value should be increased.</p>
 <table class="doxtable" summary="Memory Requirements">
 <tr>
 <th>Drive Type </th><th align="left">Value  </th></tr>
@@ -174,33 +180,24 @@ <h2><a class="anchor" id="autotoc_md13"></a>
 <tr>
 <td align="center">USB </td><td>min. 1.1 kBytes + USB Driver  </td></tr>
 </table>
-<dl class="section note"><dt>Note</dt><dd><ul>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
 <li>The stack in bytes stated is required to work with the files from top level functions like fopen, fclose, …, fdelete, frename and so on.</li>
-<li>The drivers for the different types of drives require additional stack. This differs from device to device, but in general the stack usage for MCI, NAND, and Flash should not exceed additional 100 bytes. For USB drive, refer to  <script>link_ext('USB-Resource-Req');</script> for details.</li>
-<li>If your application supports a combination of multiple drives, you need to configure your system to the the combined stack size for the sum of all drives.</li>
+<li>The drivers for the different types of drives require additional stack. This differs from device to device, but in general the stack usage for MCI, NAND, and Flash should not exceed additional 256 bytes. For USB drive, refer to  <script>link_ext('USB-Resource-Req');</script> for details.</li>
+<li>If your application supports a combination of multiple drives, you need to configure your system to the the combined stack size for the sum of all drives. </li>
 </ul>
-</dd></dl>
-<p>For  <script>link_ext('CMSIS-RTX5');</script>, the threads requirements are configured in the  <script>link_ext('RTX-Conf-CM5');</script> file located under the <b>CMSIS</b> component class:</p>
-<table class="doxtable" summary="CMSIS-RTOS Configuration">
-<tr>
-<th align="left">Option (under section Thread Configuration) </th><th>Increase Value by  </th></tr>
-<tr>
-<td>Default Thread stack size [bytes] </td><td>Stack size from table above  </td></tr>
-<tr>
-<td align="center" colspan="2"><b>or</b>  </td></tr>
-<tr>
-<td>Main Thread stack size [bytes] </td><td>Stack size from table above  </td></tr>
-<tr>
-<td align="center" colspan="2"><b>or</b>  </td></tr>
-<tr>
-<td>Total stack size [bytes]for threads with user-provided stack size </td><td>Stack size from table above  </td></tr>
-</table>
+</blockquote>
 <h2><a class="anchor" id="autotoc_md14"></a>
 Mutex Requirements</h2>
 <p>Additionally, you may also need to adjust the memory used to allocate mutex objects required by the C stdio library. Depending on the toolchain used, the total number of mutex objects required for proper operation may differ, but in general every active file stream requires a mutex object.</p>
-<dl class="section note"><dt>Note</dt><dd>Arm Standard C Library requires the following mutexes: 2 (internal stdio operations) + 3 (stdin, stdout and stderr file streams) + 1 for each active file stream</dd></dl>
-<p><b>Using CMSIS-RTOS RTX v5</b></p>
-<p>Memory for mutex objects is allocated from the dynamic memory pool (RTX_Config.h - System Configuration - Global Dynamic Memory size [bytes]). The size of dynamic memory pool must be configured so that the control blocks for the mutexes mentioned above fit inside. The size of a control block for a mutex depends on the RTOS2 implementation. For RTX5 can be found in rtx_os.h and is equal to the size of <code>osRtxMutex_t</code>.</p>
+<blockquote class="doxtable">
+<p>&zwj;<b>Note</b></p>
+<ul>
+<li>Arm Standard C Library and GCC Newlib require the following mutexes: 2 (internal stdio operations) + 3 (stdin, stdout and stderr file streams) + 1 for each active file stream</li>
+<li><a href="https://github.com/ARM-software/CMSIS-Compiler">CMSIS-Compiler</a> provides software component <code>OS Interface:CMSIS-RTOS2</code> that implements multithreading support across different toolchains when using CMSIS-RTOS2. It shall be used when file operation functions get called from multiple threads. </li>
+</ul>
+</blockquote>
 <h1><a class="anchor" id="fs_spec_mem_req"></a>
 Memory Requirements</h1>
 <p>The following table shows the memory requirements for read-only (Flash) and read-write (RAM) memory. These numbers may be used to estimate the total size requirements of the application, but the actual numbers depend on compiler optimizations and target processor and may be therefore slightly different.</p>
diff --git a/main/General/footer.js b/main/General/footer.js
index 8335595c..73e5f55b 100644
--- a/main/General/footer.js
+++ b/main/General/footer.js
@@ -1,7 +1,7 @@
 function writeHeader() {
-    document.write('Version 8.0.0-dev217');
+    document.write('Version 8.0.0-dev218');
 };
 
 function writeFooter()  {
-    document.write('Generated on Mon Oct  7 2024 10:19:20 for MDK-Middleware 8.0.0-dev217+g08b985c. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
+    document.write('Generated on Mon Oct  7 2024 10:53:28 for MDK-Middleware 8.0.0-dev218+g7514020. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
 };
diff --git a/main/Network/footer.js b/main/Network/footer.js
index 30662af4..288e99d2 100644
--- a/main/Network/footer.js
+++ b/main/Network/footer.js
@@ -3,5 +3,5 @@ function writeHeader() {
 };
 
 function writeFooter()  {
-    document.write('Generated on Mon Oct  7 2024 10:19:20 for Network Component 8.0.0. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
+    document.write('Generated on Mon Oct  7 2024 10:53:28 for Network Component 8.0.0. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
 };
diff --git a/main/USB/footer.js b/main/USB/footer.js
index 7733fe56..9e28674e 100644
--- a/main/USB/footer.js
+++ b/main/USB/footer.js
@@ -3,5 +3,5 @@ function writeHeader() {
 };
 
 function writeFooter()  {
-    document.write('Generated on Mon Oct  7 2024 10:19:21 for USB Component 8.0.0. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
+    document.write('Generated on Mon Oct  7 2024 10:53:29 for USB Component 8.0.0. Copyright &copy; 2024 Arm Limited (or its affiliates). All rights reserved.');
 };
diff --git a/version.js b/version.js
index fc4f43ba..ba12fb8b 100644
--- a/version.js
+++ b/version.js
@@ -1,7 +1,7 @@
 //--- list of versions‚ ---
 const versions = {
     "General": {
-        "latest": "8.0.0-dev217",
+        "latest": "8.0.0-dev218",
         "doc_usb": "8.0.0-dev211"
     },
     "FileSystem": {