* Microsoft® Windows® CE * Microsoft® Windows® Embedded * QNX® Neutrino® * Android (coming soon)
The TQMa64xxL debug UART is connected via a Silicon Labs USB-to-Serial converter to X16 (micro-USB) on the MBaX4XxL. A micro-USB/USB-A cable is part of the STKa64xxL accessory set. Depending on the host operating system, a driver may need to be installed.
I2C bus | TQMa64xxL | ||||
---|---|---|---|---|---|
I2C0 | 0x4A Temperature Sensor | 0x48 SEC (optional) | 0x50 Manufacturer EEPROM | 0x51 RTC | 0x54 Customer EEPROM |
Feature | BSP Revision | Remarks | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
TQ Product | Chip | Interface | Function | 0001 | 0002 | 0003 | 0004 | 0005 | 0006 | |
TQMa64xxL | AM64xx | GPIO | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
I2C0 | Bus access | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
MCU_UART0 | TTL | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
MMC0 | eMMC | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
MMC1 | SD Card | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
PRG1_RGMII1 | GBE | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
PRG1_RGMII2 | GBE | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
RGMII1 | GBE | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
UART0 | TTL | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
USB0 | USB 3.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
TQ Product | Chip | Interface | Function | 0001 | 0002 | 0003 | 0004 | 0005 | 0006 | Remarks |
---|---|---|---|---|---|---|---|---|---|---|
TQMa64xxL | AM64xx | GPIO | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
I2C0 | Bus access | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
MCU_UART0 | TTL | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
MMC0 | eMMC | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
MMC1 | SD Card | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
PRG1_RGMII1 | GBE | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
PRG1_RGMII2 | GBE | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
RGMII1 | GBE | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
UART0 | TTL | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
USB0 | USB 3.0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
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 |
BSP Revision | ci-meta-tq release | Yocto Project / Poky Release | Target machine1) | U-Boot | Linux Kernel |
---|---|---|---|---|---|
0006 | Kirkstone | 4.0.13 - Kirkstone | tqma64xxl-mbax4xxl | ti-u-boot 2021.01 | ti-rt-linux-5.10.y |
0005 | Kirkstone | 4.0.13 - Kirkstone | tqma64xxl-mbax4xxl | ti-u-boot 2021.01 | ti-rt-linux-5.10.y |
0004 | Kirkstone | 4.0.9 - Kirkstone | tqma64xxl-mbax4xxl | ti-u-boot 2021.01 | ti-rt-linux-5.10.y |
0003 | Kirkstone | 4.0.6 - Kirkstone | tqma64xxl-mbax4xxl | ti-u-boot 2021.01 | ti-rt-linux-5.10.y |
0002 | Kirkstone | 4.0.6 - Kirkstone | tqma64xxl-mbax4xxl | ti-u-boot 2021.01 | ti-rt-linux-5.10.y |
0001 | Hardknott | 3.3.6 - Hardknott | tqma64xxl-mbax4xxl | ti-u-boot 2021.01 | ti-rt-linux-5.10.y |
TQMa64xxL | MBaX4xxL | |||
---|---|---|---|---|
BSP Rev. | Rev.01xx | Rev.02xx | Rev.01xx | Rev.02xx |
0001 | ✔ | ✔ | ||
0002 | ✔ | ✔ | ||
0003 | ✔ | ✔ | ✔ | ✔ |
0004 | ✔ | ✔ | ✔ | ✔ |
0005 | ✔ | ✔ | ✔ | ✔ |
0006 | ✔ | ✔ | ✔ | ✔ |
Size | Usage |
---|---|
0x0001 sector / 512 Byte | MBR / Partition Table |
This affects the TQMa6411L variant, which does not support PRU Ethernet, so only a total of 2 instead of 5 MAC addresses are assigned per module.
All series variants of the AM64x are HS-FS, the GP variants only exist as prototypes. Change the default sysfw variant for future BSP releases, so our images will work on series modules without changes. For prototype modules with AM64x SR1.0 or SR2.0 GP, the following options are available:
U-Boot
* Enable SDHC controller quirk to fix SD card access on TQMa64xxL REV.010x SoMs.
BSP
U-Boot
Linux
Details | |
---|---|
Issue | The EEPROM for the module data (MAC, Serial Number, variant identification) does not work reliably yet. The MAC addresses must therefore be set manually in the UBoot. These can be taken from the label on the module. |
Affected Revisions | |
Module | TQMa64xx: Rev. 0100, Rev. 0101 |
Solution | |
Fix | The MAC addresses can be set via the Uboot: setenv ethaddr “eth-address from label” setenv eth1addr “eth-address from label +1” setenv eth2addr “eth-address from label +2” |