Merge to production

.github/workflows/main.yml

@@ -41,6 +41,7 @@ jobs:
       - name: Build
         run: |
           hugo --minify
+          cp learn-image-sitemap.xml public/learn-image-sitemap.xml
           bin/pagefind --site "public"
 
       # Deploys website to AWS S3

.wordlist.txt

@@ -2633,3 +2633,24 @@ xy
 zfs
 zfsutils
 zxf
+CoreDebug
+Cryptocell
+GGUF
+GenAI
+Georgi
+Gerganov
+LLM
+LLMs
+STMU
+TheBloke
+XXS
+quant
+quantized
+quantizing
+impactful
+symlinks
+nlp
+eval
+datascience
+chatbot
+Guid

content/install-guides/ambaviz.md

@@ -2,16 +2,16 @@
 ### Title the install tools article with the name of the tool to be installed
 ### Include vendor name where appropriate
 title: Arm AMBA Viz
-draft: true
+
 ### Optional additional search terms (one per line) to assist in finding the article
 additional_search_terms:
 - architecture
-- soc
-- ip
-- coresight
-- corelink
-- success kits
-- hsk
+- SoC
+- IP
+- CoreSight
+- CoreLink
+- Success Kits
+- HSK
 
 ### Estimated completion time in minutes (please use integer multiple of 5)
 minutes_to_complete: 15
@@ -29,15 +29,15 @@ multitool_install_part: false   # Set to true if a sub-page of a multi-page arti
 layout: installtoolsall         # DO NOT MODIFY. Always true for tool install articles
 ---
 
-[Arm AMBA Viz](https://www.arm.com/products/development-tools/embedded-and-software/amba-viz) is a tool used to visualize AMBA events to accelerate SoC verification.
+[Arm AMBA Viz](https://www.arm.com/products/development-tools/embedded-and-software/amba-viz) is a tool to visualize AMBA events to accelerate SoC verification. This guide is for SoC verification and validation engineers to efficiently analyze hardware signals in their designs.
 
 ## Download installer packages
 
 AMBA Viz is a component of [Arm Hardware Success Kits](https://www.arm.com/products/development-tools/success-kits).
 
-It is available to download via the [Arm Product Download Hub](https://developer.arm.com/downloads/view/HWSKT-KS-0002).
+It is available to download at the [Arm Product Download Hub](https://developer.arm.com/downloads/view/HWSKT-KS-0002).
 
-You can download AMBA Viz as an individual standalone component, or you can download the complete success kits.
+You can download AMBA Viz as an individual standalone component, or you can download the complete Success Kits.
 
 For more information on the Download Hub, refer to the [Arm Product Download Hub install guide](../pdh).
 
@@ -51,7 +51,7 @@ Extract the software from the bundle to the desired install location. For exampl
 tar -xf ambaviz.tar.gz
 ```
 
-Navigate into the newly created `ambaviz-<version>` folder, and run the following script to set up environment variables.
+Navigate to the newly-created `ambaviz-<version>` folder, and run the following script to set up environment variables:
 
 #### sh/bash
 ```command
@@ -62,18 +62,18 @@ source sourceMe.sh
 sourceMe.csh
 ```
 
-Full installation instructions are provided in the AMBA Viz Release Notes, located in the extracted directory at:
+The AMBA Viz Release Notes provide full installation instructions, located in the extracted directory at:
 ```command
 docs/public/assets/pdfs/ambaviz-release-note.pdf
 ```
 
 ## Set up the product license
 
-AMBA Viz is license managed. License setup instructions are available in the [Arm License install guide](../license/).
+AMBA Viz is license-managed. License set up instructions are available in the [Arm License install guide](../license/).
 
 ## Get started
 
-Typically AMBA Viz is launched with a waveform file:
+Typically, AMBA Viz is launched with a waveform file:
 ```command
 ambaviz -f <waveform_file>
 ```
@@ -84,7 +84,7 @@ To convert `VCD` or `FSDB` files to this format, use the `wave2avdb` script, for
 ```command
 wave2avdb -d cmn600 -f waves.vcd -o waves.avdb
 ```
-Full usage instructions are given in the User Guide, located in the extracted directory at:
+The User Guide provides full usage instructions, located in the extracted directory at:
 ```command
 docs/public/assets/pdfs/ambaviz-user-guide.pdf
 ```

content/install-guides/avh.md

@@ -48,7 +48,7 @@ Information about launching an AWS instance is available in the [Getting Started
 
 On your local machine, run the following command to connect to the instance (with user name `ubuntu`) with SSH Key `your_key.pem`.
 ```console
-ssh  -i <path_to>/your_key.pem ubuntu@<Instance_IP_address>
+ssh  -i <path_to>/your_key.pem ubuntu@<AMI_IP_address>
 ```
 ### Verify instance has launched successfully
 
@@ -92,8 +92,25 @@ Connect your VNC client to port `5901`. You will be prompted for the VNC passwor
 
 A number of [example](https://arm-software.github.io/AVH/main/examples/html/index.html) projects are available to further help you get started.
 
+### Use of FVP_Corstone-1000
+
+When using the supplied `FVP_Corstone-1000`,  you must disable the Cryptocell component therein, else you will see a licensing error.
+
+To do this, add the parameter `se.cryptocell.DISABLE_DEVICE=1` to your launch command:
+
+```console
+FVP_Corstone-1000 -C se.cryptocell.DISABLE_DEVICE=1  ...
+```
+
 ## Arm Virtual Hardware 3rd Party {#thirdparty}
 
 A valid [Arm AVH account](https://www.arm.com/resources/contact-us/virtual-hardware-boards) is required.
 
-When you login to the [AVH Dashboard](https://app.avh.arm.com) you can create virtual devices based on a growing library of real boards from Arm partners. To get started, a selection of [Quickstart Guides](https://intercom.help/arm-avh/en/collections/3380338-getting-started#quickstart) are provided to launch the particular platforms with ready made example images.
+When you login to the [AVH Dashboard](https://app.avh.arm.com) you can create virtual devices based on a growing library of real devices and boards from Arm partners. Supported targets include:
+
+* STMU5 IoT Discovery Kit
+* Raspberry Pi 4
+* i.MX 8M Plus
+* i.MX 93
+
+A selection of [Quickstart Guides](https://developer.arm.com/documentation/107660/latest/Getting-Started) are provided to launch the platforms with ready made example images.

content/install-guides/fvps-on-macos.md

@@ -0,0 +1,73 @@
+---
+### Title the install tools article with the name of the tool to be installed
+### Include vendor name where appropriate
+title: AVH FVPs on MacOS
+
+### Optional additional search terms (one per line) to assist in finding the article
+additional_search_terms:
+- AVH
+- Keil
+- FVP
+- Mac
+
+### Estimated completion time in minutes (please use integer multiple of 5)
+minutes_to_complete: 15
+
+author_primary: Christopher Seidl
+
+### Link to official documentation
+official_docs: https://github.com/Arm-Examples/FVPs-on-Mac/blob/main/README.md
+
+
+### PAGE SETUP
+weight: 1                       # Defines page ordering. Must be 1 for first (or only) page.
+tool_install: true              # Set to true to be listed in main selection page, else false
+multi_install: false            # Set to true if first page of multi-page article, else false
+multitool_install_part: false   # Set to true if a sub-page of a multi-page article, else false
+layout: installtoolsall         # DO NOT MODIFY. Always true for tool install articles
+---
+This guide is intended to get you up and running with the [Arm Virtual Hardware (AVH) Fixed Virtual Platforms (FVPs)](https://www.arm.com/products/development-tools/simulation/virtual-hardware) on MacOS. For a thorough review of all options, refer to the offical documentation.
+
+## Prerequisites
+
+[Install Docker Desktop on Mac](https://docs.docker.com/desktop/install/mac-install/).
+
+If this is for commercial use, you might require a paid subscription.
+
+## Clone the repo
+
+Open a terminal and set the working directory to the location in which you would like to store the Fast Model. Then run:
+
+```sh
+git clone https://github.com/Arm-Examples/FVPs-on-Mac.git
+```
+
+This creates the subdirectory `FVPs-on-Mac` in the current working directory.
+
+## Build the Docker wrapper
+
+Run the build script to create the Docker image and populate the `bin` folder with model wrappers:
+
+```sh
+./build.sh
+```
+
+
+When this completes, inspect the created `bin` folder containing symlinks to `fvp.sh`.
+These wrappers can be used exactly like any native model executable:
+
+```sh
+./bin/FVP_MPS2_Cortex-M3 --version
+```
+
+## Expose models to local environment
+
+Add `$(pwd)/FVPs-on-Mac/bin` to `PATH` environment:
+
+```sh
+export PATH=$PATH:$(pwd)/FVPs-on-Mac/bin
+```
+
+Put this to your `~/.zshrc` to make it permanent.
+
+For further information, refer to the [repository's README.md file](https://github.com/Arm-Examples/FVPs-on-Mac).

content/install-guides/ssh.md

@@ -35,13 +35,13 @@ Feel free to seek out additional SSH tutorials or add more information to this p
 
 SSH is a client server application.
 
-An SSH server, also called the SSH deamon, runs on a remote machine. 
+An SSH server, also called the SSH daemon, runs on a remote machine. 
 
 An SSH client runs on the local machine (the one you are typing on) and connects to the remote daemon. 
 
 ### Decide if the SSH daemon is already running
 
-For SSH to work, the SSH deamon must be running on the remote machine. Many Linux distributions install and run the SSH daemon automatically.
+For SSH to work, the SSH daemon must be running on the remote machine. Many Linux distributions install and run the SSH daemon automatically.
 
 To find out if the SSH daemon is already running running use the `ps` command.
 ```console

content/install-guides/streamline.md

@@ -49,7 +49,7 @@ For other use cases, use Arm Streamline as provided with Arm Development Studio.
 
 Download the appropriate package from the [Product Download Hub](https://developer.arm.com/downloads).
 
- - [Arm Mobile Studio](https://developer.arm.com/downloads/view/MOBST-PRO0)
+ - [Arm Performance Studio](https://developer.arm.com/downloads/view/MOBST-PRO0)
  - [Arm Development Studio](https://developer.arm.com/downloads/view/DEVST-GLD0)
 
 Arm Performance Studio supports Windows, Linux, and MacOS hosts.
@@ -58,17 +58,17 @@ Arm Development Studio supports Windows and Linux hosts.
 
 ## Installation
 
-#### Arm Performance Studio
+### Arm Performance Studio
 
-Install instructions are given in the Performance Studio [Release Notes](https://developer.arm.com/documentation/107649).
+Full install instructions are given in section 3 of the Performance Studio [Release Notes](https://developer.arm.com/documentation/107649).
+
+See also the Arm Performance Studio [install guide](../ams/).
 
 If working with an Android target, you must also install Android Debug Bridge (`adb`) available with [Android SDK platform tools](https://developer.android.com/studio/releases/platform-tools).
 
 Add the Android SDK platform tools directory to your `PATH` environment variable.
 
-See also the Arm Performance Studio [install guide](../ams/).
-
-#### Arm Development Studio
+### Arm Development Studio
 
 Install Arm Development Studio using the instructions in the [Arm Development Studio Getting Started Guide](https://developer.arm.com/documentation/101469/latest/Installing-and-configuring-Arm-Development-Studio).
 

content/install-guides/topdown-tool.md

@@ -1,7 +1,7 @@
 ---
 ### Title the install tools article with the name of the tool to be installed
 ### Include vendor name where appropriate
-title: Telemetry Solution
+title: Telemetry Solution (Topdown Methodology)
 
 ### Optional additional search terms (one per line) to assist in finding the article
 additional_search_terms:

content/learning-paths/embedded-systems/raspberry_pi_chatgpt_bot/5run.md

@@ -34,7 +34,7 @@ After the keyword is heard, you will see the `Please speak...` message indicatin
 ![the terminal, listening for you to speak after hearing the keyword](./terminal2.png)
 
 {{% notice Note %}}
-The errors are normal and do not effect the operation of the bot. 
+The errors are normal and do not affect the operation of the bot. 
 {{% /notice %}}
 
 You have constructed a bot on your Raspberry Pi which wakes up on a keyword and answers your questions. 

content/learning-paths/laptops-and-desktops/win_net/_index.md

@@ -1,5 +1,5 @@
 ---
-title: Build a Windows on Arm native application with .NET framework
+title: Build a Windows on Arm native application with .NET
 
 minutes_to_complete: 20
 

content/learning-paths/microcontrollers/asm/_index.md

@@ -5,17 +5,17 @@ minutes_to_complete: 60
 
 author_primary: Ronan Synnott
 
-who_is_this_for: This is an introductory topic for software developers interested programming microcontrollers with C/Assembly.
+who_is_this_for: This is an introductory topic for software developers who are interested in programming microcontrollers with C/Assembly.
 
 learning_objectives: 
     - Write a mixed C program and assembly language subroutines for the microcontroller. 
     - Call the subroutines written in assembly in a C function.  
     - Use Arm register calling conventions when writing subroutines in assembly language.  
-    - Step through the code to understand operation
+    - Step through the code to understand operation.
 
 prerequisites:
-    - Some familiarity with C/Assembly
-    - A Windows computer to run Keil MDK
+    - Some familiarity with C/Assembly.
+    - A Windows computer to run Keil MDK.
 
 ### Tags
 skilllevels: Introductory

content/learning-paths/microcontrollers/project-migration-cmsis-v6/troubleshooting.md

@@ -18,7 +18,7 @@ This section provides an overview of the most common errors you might encounter
 - [Linker warning L6314W](#linker-warning-l6314w)
 - [Linker errors using the RTX5 library](#linker-errors-using-the-rtx5-library)
 - [Run-time exceptions due to wrong processor mode in RTX5](#run-time-exceptions-due-to-wrong-processor-mode-in-rtx5)
-
+- [Use of undeclared identifier CoreDebug error](#use-of-undeclared-identifier-coredebug-error)
 
 ### Missing device
 
@@ -196,3 +196,56 @@ If an exception occurs at run-time, check the "Default Processor Mode for Thread
 Please note that you can also set the processor mode for threads individually (by setting the [osThreadPrivileged](https://arm-software.github.io/CMSIS_6/v6.0.0/RTOS2/group__CMSIS__RTOS__ThreadMgmt.html#ga7c2b7db42d23e4f56132e0ed739d02e5) define in the [osThread_Attr_t](https://arm-software.github.io/CMSIS_6/v6.0.0/RTOS2/group__CMSIS__RTOS__ThreadMgmt.html))
 {{% /notice %}}
 
+### Use of undeclared identifier CoreDebug error
+
+Some symbol names were changed in CMSIS v6 which might lead to the following error:
+
+```txt
+/fsl_common_arm.c:126:9: error: use of undeclared identifier 'CoreDebug'
+  126 |         CoreDebug->DEMCR |= CoreDebug_DEMCR_TRCENA_Msk;
+      |         ^
+```
+
+This results in failing builds.
+
+{{% notice Note %}}
+In general, you should ask the provider of the software component that fails because of using legacy symbols to provide an updated version that is compliant to CMSIS v6.
+{{% /notice %}}
+
+If an update is not possible or pushed out, we have created a header file that patches the changes and allows you to run older software with CMSIS v6.
+
+{{% notice Resolution for Csolution-based projects%}}
+1. Please download this [header file](https://armkeil.blob.core.windows.net/developer/Files/downloads/cmsis/cmsis_5_to_6_patch.h) to a `<known_location>`.
+
+1. In the `*.cproject.yml` file of your project, under the `add_path:` keyword, add `<known_location>`. Example:
+
+```yml
+project:
+  add-path:
+    -  <known_location>       #directory of any files you would like to include. 
+```
+
+3. In the `*.cproject.yml` file of your project, under the `misc:` keyword, add the pre-include command for the compiler you are using. Example:
+
+```yml
+project:
+  misc: 
+    - for-compiler: AC6
+      C:
+        - --include cmsis_5_to_6_patch.h
+      CPP:
+        - --include cmsis_5_to_6_patch.h
+```
+
+For more information on how to configure your *.cproject.yml file, please refer to [YML-Input-Format.md](https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/YML-Input-Format.md#project). It has a comprehensive explanation of how to write your own *.cproject.yml along with some examples.
+{{% /notice %}}
+
+{{% notice Resolution for µVision projects%}}
+1. Please download this [header file](https://armkeil.blob.core.windows.net/developer/Files/downloads/cmsis/cmsis_5_to_6_patch.h) to a `<known_location>`. A good place would be the project directory.
+
+1. Go to **Project - Options for Target** and switch to the **C/C++ (AC6)** tab. Add `-include <known_location>\cmsis_5_to_6_patch.h` to the **Misc Controls**:
+
+   ![Add patch file](./CoreDebug_uvision.png)
+
+1. Rebuild the project.
+{{% /notice %}}