Built documentation

Author: KeilChris

site/404.html

@@ -27,7 +27,7 @@
           <a href="/index.html" class="icon icon-home"> Arm Keil Studio for VS Code
         </a>
         <div class="version">
-          1.64.0
+          1.66.0
         </div><div role="search">
   <form id ="rtd-search-form" class="wy-form" action="//search.html" method="get">
       <input type="text" name="q" placeholder="Search docs" aria-label="Search docs" title="Type search term here" />
@@ -81,7 +81,7 @@
                 </li>
               </ul>
               <ul>
-                <li class="toctree-l1"><a class="reference internal" href="/read_further.html">Read further</a>
+                <li class="toctree-l1"><a class="reference internal" href="/reldocs.html">Related documentation</a>
                 </li>
               </ul>
               <ul>

site/build_run.html

@@ -34,7 +34,7 @@
           <a href="index.html" class="icon icon-home"> Arm Keil Studio for VS Code
         </a>
         <div class="version">
-          1.64.0
+          1.66.0
         </div><div role="search">
   <form id ="rtd-search-form" class="wy-form" action="./search.html" method="get">
       <input type="text" name="q" placeholder="Search docs" aria-label="Search docs" title="Type search term here" />
@@ -102,7 +102,7 @@
                 </li>
               </ul>
               <ul>
-                <li class="toctree-l1"><a class="reference internal" href="read_further.html">Read further</a>
+                <li class="toctree-l1"><a class="reference internal" href="reldocs.html">Related documentation</a>
                 </li>
               </ul>
               <ul>

site/create_app.html

@@ -34,7 +34,7 @@
           <a href="index.html" class="icon icon-home"> Arm Keil Studio for VS Code
         </a>
         <div class="version">
-          1.64.0
+          1.66.0
         </div><div role="search">
   <form id ="rtd-search-form" class="wy-form" action="./search.html" method="get">
       <input type="text" name="q" placeholder="Search docs" aria-label="Search docs" title="Type search term here" />
@@ -72,15 +72,21 @@
     </li>
     <li class="toctree-l2"><a class="reference internal" href="#configure-a-solution">Configure a solution</a>
     </li>
-    <li class="toctree-l2"><a class="reference internal" href="#software-components">Software components</a>
+    <li class="toctree-l2"><a class="reference internal" href="#software-components-and-packs">Software components and packs</a>
         <ul>
     <li class="toctree-l3"><a class="reference internal" href="#software-components-view">Software Components view</a>
         <ul>
     <li class="toctree-l4"><a class="reference internal" href="#validation">Validation</a>
     </li>
         </ul>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#rtos-example">RTOS Example</a>
+    <li class="toctree-l3"><a class="reference internal" href="#rtos-example">RTOS example</a>
+    </li>
+    <li class="toctree-l3"><a class="reference internal" href="#software-packs">Software packs</a>
+        <ul>
+    <li class="toctree-l4"><a class="reference internal" href="#manage-software-packs">Manage software packs</a>
+    </li>
+        </ul>
     </li>
         </ul>
     </li>
@@ -116,7 +122,7 @@
                 </li>
               </ul>
               <ul>
-                <li class="toctree-l1"><a class="reference internal" href="read_further.html">Read further</a>
+                <li class="toctree-l1"><a class="reference internal" href="reldocs.html">Related documentation</a>
                 </li>
               </ul>
               <ul>
@@ -301,7 +307,7 @@ <h2 id="templates">Templates</h2>
 !!! CAUTION
     If you see this warning:
     ![Task errors output](./images/task-errors.png)
-    Click **Show output** to configure the solution. You can add board, shield, or socket layers to your reference
+    Click **Show output** to¬ configure the solution. You can add board, shield, or socket layers to your reference
     application. You can also select a compiler for reference applications and other solution types.
 
 Depending on the selected example, you might need to [configure the solution](./configuration.md#configure-a-solution)
@@ -368,27 +374,19 @@ <h2 id="configure-a-solution">Configure a solution</h2>
   connections are detailed.</li>
 </ul>
 </div>
-<h2 id="software-components">Software components</h2>
+<h2 id="software-components-and-packs">Software components and packs</h2>
 <p>A <a href="https://open-cmsis-pack.github.io/cmsis-toolbox/CreateApplications/#software-components">software component</a>
-encapsulates a set of related functions. The <strong>Software Components</strong> view shows all the software components selected in
-the active project of a solution.</p>
-<p>You can:</p>
-<ul>
-<li>
-<p>Modify the software components of the project.</p>
-</li>
-<li>
-<p>Manage the dependencies between components for each target type defined in your solution, or for all the target types at
-  once.</p>
-</li>
-</ul>
+encapsulates a set of related functions and is delivered in a
+<a href="https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/index.html">software pack</a>. The
+<strong>Software Components</strong> view enables you to manage the software components and software packs selected in the active
+project of a solution.</p>
 <h3 id="software-components-view">Software Components view</h3>
 <p>Open the <strong>CMSIS view</strong> and click <img alt="Manage software components" src="images/software-components-icon.png" /> to open the
 <strong>Software Components</strong> view:</p>
-<p><img alt="The 'Software Components' " src="images/software-components-view.png" /></p>
+<p><img alt="The 'Software Components' view" src="images/software-components-view.png" /></p>
 <p>You can:</p>
 <ol>
-<li>Switch between <em>components</em> and <em>software packs</em>.</li>
+<li>Switch between <em>components</em> and <a href="#software-packs"><em>software packs</em></a>.</li>
 <li>View only components that are <em>part of the csolution</em> or components from <em>all installed packs</em>.</li>
 <li>Set the <em>context</em> for which the component selection applies (including layers).</li>
 <li><em>Select/remove</em> software components.</li>
@@ -439,7 +437,7 @@ <h4 id="validation">Validation</h4>
    components available).</li>
 </ol>
 <p>When done, don't forget to <strong>Save</strong> the changes!</p>
-<h3 id="rtos-example">RTOS Example</h3>
+<h3 id="rtos-example">RTOS example</h3>
 <p>This example shows how to add a real-time operating systems (RTOS), such as Keil RTX5.</p>
 <p>Before adding the component, add the CMSIS-RTX pack to your local installation. In a Terminal, run:</p>
 <pre><code class="language-sh">cpackget add ARM::CMSIS-RTX
@@ -464,6 +462,36 @@ <h3 id="rtos-example">RTOS Example</h3>
     # CMSIS-Pack containing the RTOS component added: 
     - pack: ARM::CMSIS-RTX
 </code></pre>
+<h3 id="software-packs">Software packs</h3>
+<p><img alt="The 'Software Components - Software packs' view" src="images/software-packs.png" /></p>
+<p>You can:</p>
+<ol>
+<li>Switch between <a href="#software-components-view"><em>components</em></a> and <em>software packs</em>.</li>
+<li>View only software packs that are <em>part of the csolution</em> or view <em>all installed packs</em>.</li>
+<li>Select the scope for which the software pack selection applies (solution/project/layer).</li>
+<li>Examine on which level the packs are references (csolution/cproject/clayer).</li>
+<li><a href="#manage-software-packs"><em>Manage software packs</em></a>.</li>
+<li>Open <em>related documentation</em>.</li>
+</ol>
+<h4 id="manage-software-packs">Manage software packs</h4>
+<p>Click on either icon: <img alt="Manage software packs" src="images/manage-packs.png" /> to open the <strong>Manage Pack</strong> dialog:</p>
+<p><img alt="Manage Pack dialog" src="images/manage-pack-dialog.png" /></p>
+<p>In the <strong>Current References</strong> section, you can:</p>
+<ul>
+<li>Set the specific
+  <a href="https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/pdsc_package_pg.html#VersionType">version</a> for a
+  pack to be used on the csolution/cproject/clayer level. Use these version specifiers:<ul>
+<li><code>Unspecified</code>: use the latest installed version of a pack</li>
+<li><code>@</code>: exact version</li>
+<li><code>@&gt;=</code>: equal or higher</li>
+<li><code>@^</code>: equal or higher with same major version</li>
+<li><code>@~</code>: Equal or higher with same major <em>and</em> minor version</li>
+</ul>
+</li>
+<li>Add a pack to a csolution/cproject/clayer.</li>
+</ul>
+<p>Below that, the <em>used pack</em> version is shown. It is computed from the requirements above.</p>
+<p>In the <strong>Update Pack</strong> section, you can see the latest installed version and check for updates.</p>
 
             </div>
           </div><footer>

site/debug.html

@@ -34,7 +34,7 @@
           <a href="index.html" class="icon icon-home"> Arm Keil Studio for VS Code
         </a>
         <div class="version">
-          1.64.0
+          1.66.0
         </div><div role="search">
   <form id ="rtd-search-form" class="wy-form" action="./search.html" method="get">
       <input type="text" name="q" placeholder="Search docs" aria-label="Search docs" title="Type search term here" />
@@ -122,6 +122,8 @@
     </li>
     <li class="toctree-l2"><a class="reference internal" href="#configure-run-and-debug">Configure run and debug</a>
         <ul>
+    <li class="toctree-l3"><a class="reference internal" href="#custom-launchjson-and-tasksjson-settings">Custom launch.json and tasks.json settings</a>
+    </li>
     <li class="toctree-l3"><a class="reference internal" href="#pyocd">pyOCD</a>
     </li>
     <li class="toctree-l3"><a class="reference internal" href="#j-link-server">J-Link Server</a>
@@ -170,7 +172,7 @@
                 </li>
               </ul>
               <ul>
-                <li class="toctree-l1"><a class="reference internal" href="read_further.html">Read further</a>
+                <li class="toctree-l1"><a class="reference internal" href="reldocs.html">Related documentation</a>
                 </li>
               </ul>
               <ul>
@@ -645,6 +647,32 @@ <h2 id="configure-run-and-debug">Configure run and debug</h2>
 various debug adapters from the <a href="https://github.com/Open-CMSIS-Pack/debug-adapter-registry">Debug Adapter Registry</a> and
 taking the user inputs into account, the <strong>CMSIS Solution</strong> extension then generates the <code>launch.json</code> and <code>tasks.json</code>
 files.</p>
+<h3 id="custom-launchjson-and-tasksjson-settings">Custom <code>launch.json</code> and <code>tasks.json</code> settings</h3>
+<p>User defined launch configurations and tasks can be added directly into the workspace files. When updating these
+files custom or modified entries are kept untouched if detected:</p>
+<ul>
+<li><code>.vscode/launch.json</code>
+  Each auto-generated configuration has an additional property <code>cmsis.updateConfiguration="auto"</code>. By either removing
+  this property, or by setting it to <code>manual</code> will exclude it from further automatic updates.</li>
+<li><code>.vscode/tasks.json</code>
+  All auto-generated tasks have labels starting with <code>CMSIS</code>. Such tasks are removed on updates. Custom tasks
+  must assure they use names not starting with <code>CMSIS</code>.</li>
+</ul>
+<p>Instead of adding custom content into these automatically updated files causing version system modifications all the
+time, one can extract those into configuration subfolders and only keep these under version control:</p>
+<ul>
+<li><code>.vscode/launch.json.d/*.json</code>
+  Each JSON file must respect the <code>launch.json</code> schema. All contained <code>configurations</code> are merged into the workspace
+  <code>.vscode/launch.json</code> file by <code>name</code> property. Auto-generated configurations can be overwritten if required without
+  attention to the <code>cmsis.updateConfiguration</code> property.</li>
+<li><code>.vscode/tasks.json.d/*.json</code>
+  Each JSON file must respect the <code>tasks.json</code> schema. All contained <code>tasks</code> are merged into the workspace
+  <code>.vscode/tasks.json</code> file by <code>label</code> property. Auto-generated <code>CMSIS</code> tasks can be overwritten if required.</li>
+</ul>
+<p>For multi-solution workspaces, i.e., having multiple <code>.csolution.yml</code> files in subfolders, solution-specific
+files in solution's <code>.vscode/launch.json.d/</code> and <code>.vscode/tasks.json.d/</code> directories are included for the
+active solution applying the same rules as above. This can be used to include solution specific content into the
+workspace configuration based on the currently used solution.</p>
 <h3 id="pyocd">pyOCD</h3>
 <p>In the <a href="manage_settings.html">Manage Solution</a> dialog, select the one of the debug adapters named <strong>xyz@pyOCD</strong>:</p>
 <p>For the <strong>Debug Interface</strong>, you can:</p>