fix(linux): Corrected the fastboot steps

source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst

@@ -56,57 +56,57 @@ in :file:`Rules.make` file present in the top level of Linux SDK Installer.
 
       UBOOT_MACHINE_R5=am62x_evm_r5_defconfig am62x_r5_usbdfu.config
 
-      UBOOT_MACHINE_A53=am62x_evm_r5_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62x_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
       # For AM62X LP
 
       UBOOT_MACHINE_R5=am62x_lpsk_r5_defconfig am62x_r5_usbdfu.config
 
-      UBOOT_MACHINE_A53=am62x_lpsk_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62x_lpsk_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
       # For AM62X SIP
 
       UBOOT_MACHINE_R5=am62xsip_evm_r5_defconfig am62x_r5_usbdfu.config
 
-      UBOOT_MACHINE_A53=am62xsip_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62xsip_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
 .. ifconfig:: CONFIG_part_variant in ('AM64X')
 
    .. code-block:: make
 
       UBOOT_MACHINE_R5=am64x_evm_r5_defconfig
 
-      UBOOT_MACHINE_A53=am64x_evm_a53_defconfig am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am64x_evm_a53_defconfig am6x_a53_snagfactory.config
 
 .. ifconfig:: CONFIG_part_variant in ('AM62AX')
 
    .. code-block:: make
 
       UBOOT_MACHINE_R5=am62ax_evm_r5_defconfig am62x_r5_usbdfu.config
 
-      UBOOT_MACHINE_A53=am62ax_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62ax_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
 .. ifconfig:: CONFIG_part_variant in ('AM62PX')
 
    .. code-block:: make
 
       UBOOT_MACHINE_R5=am62px_evm_r5_defconfig am62x_r5_usbdfu.config
 
-      BOOT_MACHINE_A53=am62px_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62px_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
 .. ifconfig:: CONFIG_part_variant in ('AM62DX')
 
    .. code-block:: make
 
       UBOOT_MACHINE_R5=am62dx_evm_r5_defconfig am62x_r5_usbdfu.config
 
-      BOOT_MACHINE_A53=am62dx_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62dx_evm_a53_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
 .. ifconfig:: CONFIG_part_variant in ('AM62LX')
 
    .. code-block:: make
 
-      BOOT_MACHINE_A53=am62lx_evm_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
+      UBOOT_MACHINE=am62lx_evm_defconfig am62x_a53_usbdfu.config am6x_a53_snagfactory.config
 
 Generate the bootloader images using top-level makefile by running following
 commands on the terminal from the top-level of the Linux SDK installer.
@@ -136,10 +136,51 @@ Connections
 
 * Power off the EVM and set up the boot mode switches to boot from USB DFU.
 
-.. code-block:: text
+  .. ifconfig:: CONFIG_part_variant in ('AM62X')
+
+    AM62X (SK-AM62B-P1) - USB-DFU Boot
+
+    .. code-block:: text
+
+        SW2 - BOOTMODE[8:15]   = 00000000
+        SW1 - BOOTMODE[0:7]    = 11001010
+
+  .. ifconfig:: CONFIG_part_variant in ('AM62AX')
+
+    AM62A (SK-AM62A-LP) - USB-DFU Boot
+
+    .. code-block:: text
+
+        SW3 - BOOTMODE[8:15]   = 00000000
+        SW2 - BOOTMODE[0:7]    = 11001010
+
+  .. ifconfig:: CONFIG_part_variant in ('AM62PX')
+
+    AM62P (SK-AM62P-LP) - USB-DFU Boot
+
+    .. code-block:: text
+
+        SW5 - BOOTMODE[8:15]   = 00000000
+        SW4 - BOOTMODE[0:7]    = 11001010
+
+  .. ifconfig:: CONFIG_part_variant in ('AM62LX')
+
+    AM62L (TMDS62LEVM) - USB-DFU Boot
 
-   SW2-11001100
-   SW3-00000000
+    .. code-block:: text
+
+        SW2 - BOOTMODE[8:11]    = 0000
+        SW3 - BOOTMODE[12:15]   = 0000
+        SW4 - BOOTMODE[0:7]     = 11001010
+
+  .. ifconfig:: CONFIG_part_variant in ('AM64X')
+
+    AM64X (TMDS64EVM) - USB-DFU Boot
+
+    .. code-block:: text
+
+        SW2 - BOOTMODE[0:7] = 11001010
+        SW3 - BOOTMODE[8:15] = 00000000
 
 * Power on the board.
 * Optionally you can also connect host PC to board via UART to read the console logs.
@@ -214,12 +255,15 @@ The following table outline the board names for snagfactory yaml configuration.
    * - am62sip-evm
      - am6x
      - am625
-   * - am64xx-evm
-     - am6x
-     - am6442
    * - am62dxx-evm
      - am6x
      - am62d2
+   * - am62axx-evm
+     - am6x
+     - am62a7
+   * - am64xx-evm
+     - am6x
+     - am6442
 
 The example configuration files for **emmc** and **ospi-nand** and **ospi-nor** are as follows.
 
@@ -392,6 +436,8 @@ For reference, the  :file:`emmc.yaml` file for **am62l** platform can be as foll
            - image: "<path_to_flash_binaries>/rootfs.ext4"
              part: "rootfs"
 
+For eMMC boot configuration, refer :ref:`emmc_boot_config`
+
 **Snagboot Command-line Configuration and Device Flashing Procedure**
 
 Snagrecover uses vendor-specific ROM code mechanisms to initialize external RAM and run U-Boot, without modifying any non-volatile memories.

source/linux/How_to_Guides/Target/How_to_emmc_boot.rst

@@ -209,6 +209,8 @@ Mount the new partition and flash the rootfs as shown :ref:`here <mmc-flash-emmc
 The Linux kernel :file:`Image` and DT file are expected to be in the /boot folder of the
 "root" partition in order for u-boot to find and load them.
 
+.. _emmc_boot_config:
+
 eMMC boot configuration
 =======================