Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions configs/AM62LX/AM62LX_linux_toc.txt
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,7 @@ linux/Foundational_Components_Filesystem
linux/Foundational_Components_Tools
linux/Foundational_Components/Tools/Development_Tools
linux/Foundational_Components/Tools/Pin_Mux_Tools
linux/Foundational_Components/Tools/Flash_via_Fastboot
#linux/Foundational_Components/Tools/GPIO_Tools
linux/Foundational_Components_Machine_Learning
linux/Foundational_Components/Machine_Learning/arm_compute_library
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@

.. note::

At the time of 11.1 release, the corresponding Snagfactory version was v2.3.
At the time of 11.2 release, the corresponding Snagfactory version was v2.5.

.. ifconfig:: CONFIG_part_variant in ('AM62DX')

Expand Down Expand Up @@ -102,6 +102,12 @@

BOOT_MACHINE_A53=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

Generate the bootloader images using top-level makefile by running following
commands on the terminal from the top-level of the Linux SDK installer.

Expand Down Expand Up @@ -185,6 +191,36 @@
* Once you load the YAML configuration file, the SnagFactory GUI tool will flash the device with
the specified configuration.

The following table outline the board names for snagfactory yaml configuration.

Check warning on line 194 in source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [RedHat.Spelling] Verify the word 'yaml'. It is not in the American English spelling dictionary used by Vale. Raw Output: {"message": "[RedHat.Spelling] Verify the word 'yaml'. It is not in the American English spelling dictionary used by Vale.", "location": {"path": "source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst", "range": {"start": {"line": 194, "column": 61}}}, "severity": "WARNING"}

Check warning on line 194 in source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [RedHat.CaseSensitiveTerms] Use 'YAML' rather than 'yaml'. Raw Output: {"message": "[RedHat.CaseSensitiveTerms] Use 'YAML' rather than 'yaml'.", "location": {"path": "source/linux/Foundational_Components/Tools/Flash_via_Fastboot.rst", "range": {"start": {"line": 194, "column": 61}}}, "severity": "WARNING"}

.. list-table::
:header-rows: 1

* - Evaluation Board
- Family
- board
* - am62pxx-evm
- am6x
- am62p
* - am62xx-evm
- am6x
- am625
* - am62lxx-evm
- am62lx
- am62l3
* - am62xx-lp-evm
- am6x
- am625
* - am62sip-evm
- am6x
- am625
* - am64xx-evm
- am6x
- am6442
* - am62dxx-evm
- am6x
- am62d2

The example configuration files for **emmc** and **ospi-nand** and **ospi-nor** are as follows.

For reference, the :file:`ospi-nor.yaml` file for **am62p** platform can be as follows:
Expand Down Expand Up @@ -314,6 +350,48 @@
- image: "<path_to_flash_binaries>/rootfs.ext4"
part: "rootfs"

For reference, the :file:`emmc.yaml` file for **am62l** platform can be as follows:

.. code-block:: text

boards:
"0451:6165": "am62l3"

soc-models:
am62l3-firmware:
tiboot3:
path: "<path_to_boot_binaries>/tiboot3.bin"
tispl:
path: "<path_to_boot_binaries>/tispl.bin"
u-boot:
path: "<path_to_boot_binaries>/u-boot.img"

am62l3-tasks:
- target-device: mmc0
fb-buffer-addr: 0x82000000
fb-buffer-size: 0x7000000

- task: gpt
args:
- name: rootfs
size: 15G

- task: reset

- task: flash
args:
- image: "<path_to_flash_binaries>/tiboot3.bin"
image-offset: 0x0
part: "hwpart 1"
- image: "<path_to_flash_binaries>/tispl.bin"
image-offset: 0x80000
part: "hwpart 1"
- image: "<path_to_flash_binaries>/u-boot.img"
image-offset: 0x280000
part: "hwpart 1"
- image: "<path_to_flash_binaries>/rootfs.ext4"
part: "rootfs"

**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.
Expand Down