Merge pull request #107 from ryanvergel/gh-pages

Updates

bootfw/build/html/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 92d69b79deb16575164d3241fda5c917
+config: 1ed14ceb51ad76e5d9cbad31448650d3
 tags: 645f666f9bcd5a90fca523b33c5a78b7

bootfw/build/html/_sources/docs/bootfw_boot.bin_generation.md.txt

@@ -3,28 +3,28 @@
 
 ## Introduction
 
-As outlined in [bootfw overview](./bootfw_overview.md), Kria SOM Starter Kit BOOT.BIN is part of QSPI image, and contains 4 components - FSBL, PMU_FW, TF-A, U-boot. This page outlines the process to re-create a BOOT.bin for Kria SOM Starter kits used in A/B image update. Both PetaLinux and Yocto supports BOOT.BIN Generation. [Yocto](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto) support for generating Kria SOM Starter Kit BOOT.BIN image only starts in 2023.1, previous versions do not have support.
+As outlined in the [bootfw overview](./bootfw_overview.md), the AMD Kria™ SOM Starter Kit BOOT.BIN is part of the quad SPI (QSPI) image, and contains four components: FSBL, PMU_FW, TF-A, and U-Boot. This page outlines the process to recreate a BOOT.bin for Kria SOM Starter kits used in A/B image update. Both PetaLinux and Yocto supports BOOT.BIN generation. [Yocto](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto) support for generating the Kria SOM Starter Kit BOOT.BIN image only starts in 2023.1, previous versions do not have support.
 
-## Generate BOOT.BIN using Yocto
+## Generate BOOT.BIN Using Yocto
 
- [Yocto Kria Support](https://xilinx.github.io/kria-apps-docs/yocto.html) details how to use Yocto to generate Kria artifacts, go through this page from beginning to "Build the Artifacts" section to setup Yocto.
+ [Yocto Kria Support](https://xilinx.github.io/kria-apps-docs/yocto.html) details how to use Yocto to generate Kria artifacts; go through this page from beginning to "Build the Artifacts" section to set up Yocto.
 
- The bitbake recipe for BOOT.BIN in Yocto is ```xilinx-bootbin``` and command to build is:
+ The bitbake recipe for `BOOT.BIN` in Yocto is ```xilinx-bootbin``` and the command to build is:
 
  ``` shell
  MACHINE=k26-smk bitbake xilinx-bootbin # for K26
  MACHINE=k24-smk bitbake xilinx-bootbin # for K24
  ```
 
- To set u-boot configuration, use this command before building:
+ To set U-Boot configuration, use this command before building:
 
  ```shell
  MACHINE=k26-smk bitbake virtual/bootloader -c menuconfig
  ```
 
-## Generate BOOT.BIN using PetaLinux
+## Generate BOOT.BIN Using PetaLinux
 
-Go through [Xilinx Wiki PetaLinux Build Instructions](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM#PetaLinux-Build-instructions) - there are instructions to generate BOOT.BIN from PetaLinux. To recap they are the following:
+Go through the [PetaLinux Build Instructions](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM#PetaLinux-Build-instructions). There are instructions to generate BOOT.BIN from PetaLinux. To recap, they are the following:
 
 ```shell
 petalinux-create -t project -s <kria_starterkit>.bsp
@@ -33,15 +33,15 @@ petalinux-build
 petalinux-package --boot --u-boot --force
 ```
 
-You will find new boot firmware at /image/linux/BOOT.BIN.
+You will find new boot firmware at `/image/linux/BOOT.BIN`.
 
-To set configuration for u-boot, use this command before petalinux-build:
+To set the configuration for U-Boot, use this command before `petalinux-build`:
 
 ```shell
 petalinux-config –c u-boot
 ```
 
-The new BOOT.BIN can be loaded to the Starter Kit using the xmutil bootfw_update utility described in [Kria Wiki's Boot FW Update Process section](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM#Boot-FW-Update-Process).
+The new `BOOT.BIN` can be loaded to the Starter Kit using the xmutil bootfw_update utility described in [Kria Wiki's Boot FW Update Process section](https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1641152513/Kria+K26+SOM#Boot-FW-Update-Process).
 
 ## License
 
@@ -52,4 +52,4 @@ You may obtain a copy of the License at
 
 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 
-<p class="sphinxhide" align="center">Copyright&copy; 2023 Advanced Micro Devices, Inc</p>
+<p class="sphinxhide" align="center">Copyright&copy; 2023-2025 Advanced Micro Devices, Inc</p>

bootfw/build/html/_sources/docs/bootfw_image_recovery.md.txt

@@ -2,9 +2,9 @@
 
 ## Introduction
 
-The Kria Starter Kit solution stack includes an Ethernet based recovery tool called Boot Image Recovery Tool that can be used in conjunction with a standard web-browser on a Host PC to provide direct update of the Kria user A/B boot firmware partitions and the corresponding persistent register information. The recovery tool is maintained in a reserved section of the QSPI memory and is intended as a platform recovery mechanism is there is an issue with the normal A/B boot FW update mechanism.  
+The AMD Kria;™ Starter Kit solution stack includes an Ethernet based recovery tool called Boot Image Recovery Tool that can be used in conjunction with a standard web-browser on a host PC to provide direct update of the Kria user A/B boot firmware partitions and the corresponding persistent register information. The recovery tool is maintained in a reserved section of the QSPI memory and is intended as a platform recovery mechanism if there is an issue with the normal A/B boot FW update mechanism.  
 
-Boot Image Recovery Tool is an application that runs a simplified Ethernet stack for interacting with a user's host machine (e.g. laptop) to allow a manual update/overwrite of Image A and Image B on QSPI on SOM.  The recovery tool updates the corresponding A/B persistent registers to an appropriate state based on the user actions in the web UI. A user can also override the QSPI persistent register states via the WebUI.
+Boot Image Recovery Tool is an application that runs a simplified Ethernet stack for interacting with your host machine (for example, laptop) to allow a manual update/overwrite of Image A and Image B on QSPI on SOM.  The recovery tool updates the corresponding A/B persistent registers to an appropriate state based on the user actions in the web UI. You can also override the QSPI persistent register states via the WebUI.
 
 The Boot Image Recovery Tool requires no incremental tools on the customer PC besides a web-browser with a fixed IP address of 192.168.0.111. The user PC must have access to the new firmware binary file (BOOT.BIN). AMD distributes boot FW and “factory boot file” updates to the Kria Wiki. The Boot Image Recovery Tool writes the a given BOOT.BIN to QSPI physical address based on the image target selection made in the web UI.