Table of Contents

MBa93xxLA-Mini - YOCTO Linux BSP documentation

Overview

The TQMa93xxLA on MBa93xxLA-Mini provides a powerful embedded platform based on NXP’s i.MX93 CPU series. The Linux Board Support Package (BSP) is based on the Yocto Project using the ci-meta-tq and consists of a Bootloader (U-Boot), Linux kernel and a minimal RootFS configuration. All BSP sources which are created or customized by TQ are provided via GitHub.

TQ Yocto Layer

meta-tq

meta-tq layer is the TQ hardware support layer, it provides machine configuration, U-Boot and Linux kernel recipe and covers machine specific dependencies to cpu vendor yocto layer.
meta-tq on github

meta-dumpling

meta-dumpling is supporting layer for meta-tq and part it and provides Yocto image and distro example configurations.
meta-tq on github

For each Board Support Package (BSP), the corresponding modules are organized 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

TQ Systems provides comprehensive documentation on its embedded mini-module products to facilitate the evaluation and design phase with our products.

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 a Starter Kit and is released on request 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 MBa93xxCA REV.020x MBa93xxLA REV.020x MBa93xxLA-MINI REV.020x
RAM configs 1 / 1.5 / 2 GiB 1 / 1.5 / 2 GiB 1 / 1.5 / 2 GiB
CPU variants i.MX93 i.MX93 i.MX93
Fuses / OCRAM x x x
speed grade / temperature grade detection x x x
UART (console on UART1) x x x
GPIO
LED x x
Button x x
I2C
system EEPROM parsing x x x
PMIC x x x
eMMC / SD
Read x x x
Write x x x
Ethernet
GigE / FEC via Phy on MBa93xxCA x x x
GigE / EQOS via Phy on MBa93xxCA x x x
Bootdevices
SD-Card on USDHC2 x x x
eMMC on USDHC1 x x x
QSPI-NOR on FlexSPI x x see Known Issues
Serial Downloader x x
USB
USB 2.0 Host / Hub x x x
USB DRD (USB 2.0 Cable Detect, VBUS) x x x
QSPI NOR
Read with 1-1-4 SDR x x see Known Issues
PP / Erase with 1-1-4 SDR x x see Known Issues
Cortex M33
env settings for starting from TCM
examples with UART3 as debug console

NOTE: for MBa93xxLA-MINI REV.010x is only be used for IBPQ customers will get REV.020x or later

TODO or not tested / supported

  • CPU variants with single core and without NPU

Linux

Linux

Support matrix for MBa93xxCA REV.020x and MBa93xxLA REV.010x

Feature linux-imx-tq_6.1 linux-imx-tq_6.6 linux-tq_6.12
RAM configs 1 / 1.5 / 2 GiB 1 / 1.5 / 2 GiB 1 / 1.5 / 2 GiB
CPU variants i.MX93 i.MX93 i.MX93
Fuses / OCRAM x x x
speed grade / temperature grade detection x x
Frequency scaling x
UART
console on UART1 (via USB / UART converter) x x x
UART2/3/4 x x x
GPIO
LED x x x
Button x x x
I2C
EEPROMs x x x
PMIC x x x
RTC x x x
Temperature Sensors x x x
IMU / Gyroscope x x x
Port expander x x x
ENET
GigE / FEC via Phy on MBa93xxCA x x x
GigE / EQOS via Phy on MBa93xxCA x x x
USB
USB 2.0 Host / Hub x x x
USB DRD (USB 2.0 Cable Detect, VBUS) x x x
QSPI NOR
Read with 1-1-4 SDR x
Read with 1-4-4 SDR x x
PP / Erase with 1-1-4 SDR x
PP / Erase with 1-4-4 SDR x x
Display
LVDS x x x
CAN-FD
CAN-FD x x x
SPI
spidev at all CS x x
internal ADC
ADC x x x
Cortex M33
examples running from TCM see notes see notes
use UART3 as debug console (see issues) x x
LPB boot
NPU
Firmware for CORTEX M33 see issues
Demo
MIPI CSI (see Issues section)
Gray with Vision Components GmbH camera (Sensor OV9281)
Raw Bayer with Vision Components GmbH camera (Sensor IMX327)

NOTE LVDS support for linux-tq_6.12 on MBA93xxCA is missing.

I2C Devices

Onboard I2C Devices

I2C Bus - TQMa93xxLA
I2C1 0x1B
Tempsensor in EEPROM 		0x33
EEPROM SW Protect 		0x25
PMIC 		0x48
Plug & Trust Secure Element
(optional) 		0x51
RTC 		0x53
EEPROM 		0x5F
EEPROM (Identification Page) 		0x6A
Gyroscope
(optional)
I2C Bus - MBa93xxLA-Mini
I2C3 0x70
I2C Port expander 		0x71
I2C Port expander

Changelog

Changelog BSPs

scrathgap-next

Added

Abschnitt "Added" wurde in der Datei nicht gefunden.

Changed

Abschnitt "Changed" wurde in der Datei nicht gefunden.

Fixed

Abschnitt "Fixed" wurde in der Datei nicht gefunden.

Removed

  • linux-ti-tq-6.1

    linux-ti-tq-6.1 has been obsolete since scarthgap.TQ.ARM.BSP.0001 in favor of linux-ti-tq-6.6. With the addition of linux-ti-tq-6.12 as the new default kernel for TQMa62xx[L]/TQMa64xxL/TQMa67xx[L], the linux-ti-tq-6.1 recipe is removed.

  • u-boot-ti-tq-2023.04: remove recipe

    Only u-boot-tq-2025.07 is supported for the TQMa62xx[L], TQMa64xxL and TQMa67xx[L] in future BSP releases.

  • linux-tq-5.4

    • TQMLS102xA is now supported by linux-tq-6.12

  • linux-rt-tq-5.4

    • Currently there is no replacement for RT-enabled kernel on TQMLS102xA
    • Support for newer kernels can be added on request

  • linux-imx-tq-5.15

    • Both TQMLS1012AL and TQMLS10128A are now supported by linux-imx-tq-6.6

  • MBaX4XxL

    • The legacy Image kernel image has been removed from the root filesystem

      We boot the fitImage by default since kirkstone.TQMa64xxL.BSP.SW.0007. U-Boot versions older than that release need to be updated, or a custom BSP image including Image in KERNEL_IMAGETYPES needs to be built.

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.