Embedded module TQMa8MxML - YOCTO Linux BSP documentation



The meta-tq layer extends the Yocto Project's reference system Poky to provide support for a selection of TQ Embedded CPU Modules, including the TQMa8MxML.

It uses the same codebase as the PTXdist based TQ Linux BSPs and therefore provides the same versions of U-Boot and Linux kernel, but doesn't define a specific root filesystem configuration.

Because of the dependencies to the other yocto layers we recommend to use ci-meta-tq which already provides all required yocto layers as git submodules instead of meta-tq to build this BSP release.

The instructions on this page refer to the BSP and ancillary tools listed in the following table:

BSP Revision 0080
meta-tq release hardknott.TQMa8MxML.BSP.SW.0080
Yocto Project / Poky Release 3.3.3 - Hardknott
Target machine1) tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
U-Boot v2020.04_imx_5.4.47_2.2.0
Linux Kernel fslc-5.10-2.1.x-imx
The goal of these wiki pages is to get you started using ci-meta-tq with the STKa8MxML, so instead of reinventing the wheel we will adhere to the very compact Yocto Project Quick Start and supply details specific to the STKa8MxML where necessary.

For further details regarding Yocto Project 3.3.3 - Hardknott please refer to its official documentation.

Build Host

Yocto Project / Poky requires a Linux build host, so first of all you need a development workstation (or a virtual machine2)) with a Linux distribution installed.

Please refer to section Compatible Linux Distribution of the Yocto Project Quick Start for supported linux distributions and section Build Host Packages for required build host packages for those distributions.

The instructions on this page have been tested on Ubuntu 18.04 (64 bit) in a VMWare virtual machine.

Although not required by Yocto Project / Poky, we also recommend to configure and run a tftp server (for image download / update) and an nfs server (for network mounted root filesystem) on your development host.

Yocto Hardknott BSP

1. Open a new terminal and create a directory for the BSP build e.g. in the home directory and navigate to that directory.

mkdir -p ~/workspace/hardknott.TQMa8MxML.BSP.SW.0080
cd ~/workspace/hardknott.TQMa8MxML.BSP.SW.0080

2. Create a local copy of ci-meta-tq

$ git clone --recurse-submodules https://github.com/tq-systems/ci-meta-tq.git

3. Checkout BSP release on new local branch.

$ cd ci-meta-tq
$ git checkout hardknott.TQMa8MxML.BSP.SW.0080 -b hardknott-tqma8mxml

4. Update git submodules:

$ git submodule sync
$ git submodule update --init

5. Setup local branch to track the remote branch.

git branch -u origin/hardknott

6. Export the environment DISTRO and MACHINE3) variable:

$ export DISTRO=dumpling-wayland-nxp
$ export MACHINE=tqma8mxml-2gb-mba8mx

7. Configure the Build:

$ source setup-environment tqma8mxml_build imx
Each time a new terminal is opened, the build environment must be reinitialised. The command described above is intended for the initial build space initialisation. To return to an existing buildspace open up a new terminal and navigate to the ci-meta-tq folder and execute the following command:
source setup-environment tqma8mxml_build

8. Build an Image for STKa8MxML:

Image with debug features and packages

$ bitbake tq-image-weston-debug

Image without debug features and root login

$ bitbake tq-image-weston


9. Write the Image6)7)

$ sudo dd if=tmp/deploy/images/tqma8mxml-2gb-mba8mx/tq-image-weston-tqma8mxml-2gb-mba8mx.wic of=/dev/<TARGET_DEVICE>

10. Boot the STKa8MxML from SD card (cf. MBa8Mx DIP switch settings) |

Yocto Zeus BSP

1. Create a local copy of ci-meta-tq

$ git clone --recurse-submodules https://github.com/tq-systems/ci-meta-tq.git

2. Checkout BSP release on new local branch.

$ cd ci-meta-tq
$ git checkout zeus.TQMa8MxML.BSP.SW.0057 -b zeus-tqma8mxml

3. Update git submodules:

$ git submodule update --init
$ git submodule sync

4. Setup local branch to track the remote branch.

git branch -u origin/zeus-tqma8

5. Configure the Build8):

$ source imx-setup-release.sh -b tqma8mxml_build -e wayland
$ echo 'MACHINE = "tqma8mxml-2gb-mba8mx"' >> conf/local.conf
Each time a new terminal is opened, the build environment must be reinitialised. The command described above is intended for the initial build space initialisation. To return to an existing buildspace open up a new terminal and navigate to the ci-meta-tq folder and execute the following command:
source setup-environment tqma8mpxl_build

6. Build an Image for STKa8MxML:

$ bitbake tq-image-weston


7. Write the Image11)12)

$ sudo dd if=tmp/deploy/images/tqma8mxml-2gb-mba8mx/tq-image-weston-tqma8mxml-2gb-mba8mx.wic of=/dev/<TARGET_DEVICE>

8. Boot the STKa8MxML from SD card (cf. MBa8Mx DIP switch settings) |


1)
i.e. value for MACHINE variable
2)
for testing purposes Yocto Project provides a ready to use virtual machine called Build Appliance
3)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
4)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
5)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
6)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
7) , 12)
TARGET_DEVICE has to be an SD card
8)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
9)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
10)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx
11)
valid machines are
tqma8mxml-1gb-mba8mx
tqma8mxml-2gb-mba8mx