Table of Contents

Embedded module TQMa8MPxS - YOCTO Linux BSP documentation

Overview

The TQMa8MPxS which is located on the MB-SMARC-2 provides a powerful embedded module platform based on NXPs i.MX8 series. The BSP is based on the Yocto Project using TQ’s meta-tq hardware support layer, with build host setup instructions and BSP sources provided via GitHub.

Please see the meta-tq repository on GitHub for further instructions. A list of supported Yocto images and example configurations is available in the BSP repository GitHub.

For each Board Support Package (BSP), the corresponding modules are versioned under the matching Git tag in our GitHub repository. Simply check out the tag that matches your BSP release, then open the module’s README file in the “doc” folder to find detailed information.

Documentation and Downloads

Documentation and Downloads

All TQ Systems products come with comprehensive documentation to help you get started and integrate our hardware into your designs.

Publicly Available User Manuals & Datasheets

The following documents can be downloaded directly from our Website (no login required) for the desired product:

User Manual (Baseboard)
Detailed hardware descriptions, installation steps, jumper settings, connector layouts and troubleshooting tips.
User Manual (Module)
Electrical specifications, interface overviews, software setup guides and reference tables.
Datasheets
Absolute maximum ratings, timing diagrams and ordering information.

Customer Info Archive (Starter Kit Customers)

The Customer Info Archive is provided upon purchase of an official Starter Kit and is released manually by TQ Support. To obtain it, please open a Support Ticket with your order details.

The archive includes:

  • Mainboard schematic & placement diagram
  • Module CAD files (native format)
  • Module mechanical dimensions (2D/3D drawings)
  • Pinmuxing configuration (recommended device tree fragments)
  • Pinout reference (signal assignments, voltage domains)
  • Design checklist (layout guidelines, EMI/ESD considerations)
  • Processing instructions (LGA Modules)

BSP Tagging and Revisioning

BSP Git Tagging and Revisioning

TQ manages all Board Support Package (BSP) releases in the meta-tq GitHub repository using annotated Git tags. This ensures each release is traceable to an exact source snapshot and clearly documents which Yocto branch, platform (module) and software revision it covers.

Tag Format:
<YoctoBranch>.<ModuleIdentifier>.TQ.ARM.BSP.<RevisionNumber>

Component Description
YoctoBranch Name of the Yocto Project release (e.g. kirkstone, scarthgap)
ModuleIdentifier Target module name when present; omitted entirely for “scarthgap” tags
TQ.ARM.BSP Literal marker for “Board Support Package – Software”
RevisionNumber Four-digit, zero-padded incrementing counter (e.g. 0001, 0002, …)

Examples:
kirkstone.TQMa64xxL.BSP.SW.0008
scarthgap.BSP.SW.0001 – here no module identifier is used

Supported Platforms Reference:
To see exactly which platforms (machines/boards) each BSP tag covers, open the meta-tq folder in that tag and view its README.md:
/tq-systems/meta-tq/tree/<git-tag>/meta-tq
Click on README.md there to find the full list of Yocto machine names, board variants, RAM options and support status.

Get Notified

Enable Notifications:
In order to be automatically notified of new BSP releases by e-mail, you must activate notifications in the corresponding Github repository.

1. Go to the desired repository in Github (e.g. meta-tq)
2. Click on the notification button in the top right corner.
3. Log in or create a Github account if you have not already done so.
4. Select “All activity” so that you will be notified of every new release.

Software Versions:
For the exact versions of U-Boot, Linux kernel and other components used in a BSP tag, view doc/README.SoftwareVersions.md in that tag.
tq-systems/meta-tq/blob/<git-tag>/meta-tq/doc/README.SoftwareVersions.md

Current BSP Information

U-boot

U-Boot

Feature REV.010x
RAM configs 1,2,4,8 GiB
CPU variants i.MX8MPQ
Fuses / OCRAM x
speed grade / temperature grade detection x
UART (console on UART3, X20) x
I2C
system EEPROM parsing x
PMIC x
eMMC / SD
Read x
Write x
Ethernet
GBE0 (X11) x
GBE1 (X10) x
Bootdevices
SD-Card on USDHC2 x
eMMC on USDHC3 x
QSPI-NOR on FlexSPI x
Serial Downloader (X4) x
USB
USB 3.0 Host / Hub (X7) x
USB 2.0 Host / Hub (X8) x
USB 3.0 Micro / Hub, (X3, host only)
USB DRD USB 2.0 (X4, peripheral only) x
QSPI NOR
Read with 1-4-4 SDR x
PP / Erase with 1-1-4 SDR x
Cortex M7
env settings for starting from TCM
examples with UART3 as debug console

TODO or not tested / supported

  • CPU variants i.MX8MPD/S and Lite

Linux

Linux

Feature 6.12.y
RAM configs 1,2,4,8 GiB
CPU variants i.MX8MPQ
Fuses / OCRAM x
speed grade / temperature grade detection x
UART
SER0 on UART1 (X39) x
SER1 on UART3 (console, X20) x
SER2 on UART2 (X25) x
SER3 on UART4 (X40) x
I2C x
EEPROMs x
PMIC x
RTC x
Temperature Sensors x
ENET x
GBE0 (X11) x
GBE1 (X10) x
USB
USB 3.0 Host / Hub (X7) x
USB 2.0 Host / Hub (X8) x
USB 3.0 Micro / Hub, (X3, host only)
USB DRD (USB 2.0 Cable Detect, VBUS, X4) x
QSPI NOR
Read with 1-4-4 SDR x
PP / Erase with 1-4-4 SDR x
Graphic / Multimedia
GPU x
VPU x
Display
LVDS (X46, X48) x
Dual-Channel LVDS
HDMI (X6) x
DisplayPort using MIPI-DSI Bridge (X5) x
Audio
HDMI
Codec (Line IN / Line OUT) x
PCIe
wireless card at M.2 (X44) x
CAN-FD
CAN-FD (X29, X30) x
Cortex M7
examples running from TCM
use UART4 as debug console (see issues)
MIPI CSI (see Issues section)
Gray with Vision Components GmbH camera (Sensor OV9281)
Raw Bayer with Vision Components GmbH camera (Sensor IMX327)
NPU
NPU

Changelog

Changelog BSPs

Changelog Scarthgap PRE-Release

Added

  • linux-rt-tq-6.12: TQMLS10xxA / TQMLX2160A:

    Mark recipe as compatible for these machines

  • TQMa8MPxS: add board support for SoM on MB-SMARC-2

  • TQMLX2160A: Add Secure Boot support

    See the TQMLX2160A README for more information. The current implementation only secures the boot process up to the bootloader. The kernel and userspace are not verified.

Changed

  • imx-atf-tq: TQMa8 / TQMa9:

    Include NXP fixes up to tag lf-6.6.52-2.2.1 and adjustments for Layerscape.

  • linux-rt-tq-6.6: TQMa6 / TQMa6UL[L]x[L] / TQMa7 / TQMa8Mx / TQMa8MxML / TQMa8MxNL:

    Include stable fixes up to v6.6.101 and stable-rt fixes up to v6.6.101-rt59

  • linux-tq-6.6: TQMa6 / TQMa6UL[L]x[L] / TQMa7 / TQMa8Mx / TQMa8MxML / TQMa8MxNL:

    Include stable fixes up to v6.6.102

  • linux-imx-tq-6.6: TQMa8 / TQMa9:

    Include NXP fixes up to tag lf-6.6.52-2.2.1 and stable fixes up to 6.6.101 from linux-fslc

  • linux-[rt-]tq-6.12: TQMa335x / TQMa93 / TQMa8MP / TQMLS10xx / TQMLX2160:

    • Include linux-stable fixes up to 6.12.41
    • configure STMMAC as built-in to support NFS root on boards with MDIO on STMMAC

  • machines: use require for machine config includes

  • alsa-state: enable IN3_L / Left Mixer input path (prepare MicIn support) for i.MX base SoM

  • layer.conf: add LAYERRECOMMENDS

Fixed

  • u-boot-lsdk-tq-2019.04: TQMLS1028A: Fix PCIe initialisation flow

    Backport some fixes to the initalisation flow, limit to Gen2 and add wait for link polling. Both the limitation and the polling loop improve compatibility to more cards, since bootloader support is crucial for working PCIe under Linux.

  • tq-bootconf: add reproducible default for 'FIT_CONF_PREFIX'

    When adding support to machines a reproducible default is needed to keep boot configurations and fitImages in sync.

  • TQMLS1012AL: Fix build with Secure Boot support

    Secure Boot on the TQMLS1012AL is build-tested only.

  • qoriq-atf: Fix hash calculation on all Layerscape platforms

    Fixes validation failure when Secure Boot is enabled.

Removed
  • u-boot-tq_2018.07: remove recipe after TQMLS10xxA was upgraded to v2022.04

The information provided on this wiki page is subject to change due to circumstances beyond our control. While we strive to keep all details as accurate and up-to-date as possible, it is possible that certain updates or changes may go unnoticed for some time. As a result, some sections of this page may contain outdated information. If you notice any mistakes in the documentation, we kindly ask you to inform the TQ Support through our ticket system.