The TI Sitara AM64x CPU provides the option to boot from USB (host and device).
1. Format a USB flash drive with FAT32 filesystem.
2. Copy the files listed below from the Yocto buildspace deploy directory to the USB flash drive prepared with FAT32:
3. Connect the USB flash drive with the USB 3.0 the USB-OTG interface.
4. Set the STKa64xxL DIP switches to boot from USB host (mass storage).
S4
S5
S6
S7
5. Connect host PC with STKa64xxL connector X2 and setup the terminal program.
Please see the terminal_emulator section how to setup a serial debug connection.
6. Power on the STKa64xxL to boot from USB.
Please check that dfu-util is installed the Linux host.
1. Copy the files below from the Yocto buildspace deploy directory deploy e.g. the home folder:
2. Connect STKa64xxL X1 and X2 with a mirco USB cable to the Host PC.
3. Set the STKa64xxL DIP switches to boot from USB device (dfu-util).
S4
S5
S6
S7
4. Power up the STKa64xxL.
5. Open a second terminal for the serial debug connection with e.g. Minicom
Please see the terminal_emulator section how to setup a serial debug connection.
6. Open terminal (shell) on Linux host and execute the commands below to boot the STKa64xxL via USB device.
sudo dfu-util -a bootloader -D tiboot3.bin
sudo dfu-util -R -a bootloader -D tiboot3.bin sudo dfu-util -R -a tispl.bin -D tispl.bin sudo dfu-util -R -a u-boot.img -D u-boot.img
System Images
Boot Device | Symlink | File |
---|---|---|
SD Card/eMMC | tq-image-weston-debug-tqma64xxl-mbax4xxl.wic | tq-image-weston-debug-tqma64xxl-mbax4xxl-<build_timestamp>.rootfs.wic |
Bootloader Binaries
Please refer to the Secure Device Processor SDK documention for more information on the High Security CPU variants. This documentation must be obtained directly from TI. To select the variant to use, set the SYSFW_DEFAULT_VARIANT variable to “am64x-gp”, “am64x_sr2-hs-fs” or “am64x_sr2-hs” (in local.conf or a custom machine definition), to match the used AM64x CPU variant and security enforcement status. The default value is “am64x-gp”. The selected variant will be installed to the boot partition of the generated WIC images as tiboot3.bin. It is possible to change an existing image to boot on a different CPU variant by mounting the boot partition and renaming one of the bootloader binaries to tiboot3.bin.
Boot Device | Symlink | File |
---|---|---|
SD/eMMC | u-boot.img | u-boot-tqma64xxl-mbax4xxl-2021.01+<git_commit_id>-r0.img |
tispl.bin | tispl.bin-tqma64xxl-mbax4xxl-2021.01+<git_commit_id>-r0 | |
tiboot3.bin | tiboot3-am64x-gp-evm.bin |
Linux Kernel Image
Symlink | File |
---|---|
Image | Image–5.10.152+<git_commit_id-r0-tqma64xxl-mbax4xxl-<timestamp>.bin |
Devicetree Blobs
Symlink | Description |
---|---|
k3-am642-tqma64xxl-mbax4xxl-tqma64xxl-mbax4xxl.dtb | Default |
k3-am64-tqma64xxl-mbax4xxl-sdcard.dtbo | SD Card Devicetree overlay |
k3-am64-tqma64xxl-mbax4xxl-wlan.dtbo | WLAN Devicetree overlay |
Rootfs images
Symlink | File |
---|---|
tq-image-weston-debug-tqma64xxl-mbax4xxl.tar.gz | tq-image-weston-debug-tqma64xxl-mbax4xxl-<build_timestamp>.rootfs.tar.gz |