Preface

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 @mod_name@.

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 @yocto_rel_branch_rev@
meta-tq release @yocto_rel_branch@.@mod_name_mtq@.BSP.SW.@bsp_rev@
Yocto Project / Poky Release @yocto_rel_ver_major@.@yocto_rel_ver_minor@ - @yocto_rel_name@
Target machine1) @mtq_machines@
U-Boot @uboot_version@
Linux Kernel @linux_kernel@
The goal of these wiki pages is to get you started using ci-meta-tq with the @stk_name@, so instead of reinventing the wheel we will adhere to the very compact Yocto Project Quick Start and supply details specific to the @stk_name@ where necessary.

For further details regarding Yocto Project @yocto_rel_ver_major@.@yocto_rel_ver_minor@ - @yocto_rel_name@ please refer to its official documentation.

Prerequisites

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 @host_os_name@ @host_os_version@ (@host_os_bits@) 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 BSP Build Instructions

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/@yocto_rel_branch@.@yocto_rel_branch_module@.BSP.SW.@yocto_rel_branch_rev@
cd ~/workspace/@yocto_rel_branch@.@yocto_rel_branch_module@.BSP.SW.@yocto_rel_branch_rev@

2. Create a local copy of @mtq_repos@ 

$ 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 @yocto_rel_branch@.@yocto_rel_branch_module@.BSP.SW.@yocto_rel_branch_rev@ -b @yocto_local_branch_name@

4. Update git submodules: 

$ git submodule sync
$ git submodule update --init

5. Setup local branch to track the remote branch. 

git branch -u origin/@yocto_remote_branch_name@

6. Export the environment DISTRO and MACHINE3) variable: 

$ export DISTRO=@distro_env@
$ export MACHINE=@machine_env@

7. Configure the Build: 

$ source setup-environment @mod_name_code@_build @ci_mtq_build_cfg@
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 @mod_name_code@_build

8. Build an Image for @stk_name@:

Image with debug features and packages

$ bitbake @mtq_image@-debug

Image without debug features and root login

$ bitbake @mtq_image@


9. Write the Image6)7) 

$ sudo dd if=tmp/deploy/images/@mtq_machine_default@/@mtq_image@-@mtq_machine_default@.wic of=/dev/<TARGET_DEVICE>

10. Boot the @stk_name@ from SD card (cf. @mb_name@ DIP switch settings) |

Old Yocto Release Build Instructions

Yocto Zeus BSP

1. Create a local copy of @mtq_repos@ 

$ 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 @yocto_zeus_rel_branch@.@yocto_zeus_rel_branch_module@.BSP.SW.@yocto_zeus_rel_branch_rev@ -b @yocto_zeus_local_branch_name@

3. Update git submodules: 

$ git submodule update --init
$ git submodule sync

4. Setup local branch to track the remote branch. 

git branch -u origin/@yocto_zeus_remote_branch_name@

5. Configure the Build8): 

$ source imx-setup-release.sh -b @mod_name_code@_build -e wayland
$ echo 'MACHINE = "@mtq_machine_default_zeus@"' >> 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 @stk_name@: 

$ bitbake @mtq_image@


7. Write the Image11)12) 

$ sudo dd if=tmp/deploy/images/@mtq_machine_default_zeus@/@mtq_image_zeus@-@mtq_machine_default_zeus@.wic of=/dev/<TARGET_DEVICE>

8. Boot the @stk_name@ from SD card (cf. @mb_name@ 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) , 4) , 5) , 6)
valid machines are
@mtq_machines@
7) , 12)
TARGET_DEVICE has to be an SD card
8) , 9) , 10) , 11)
valid machines are
@mtq_machines_zeus@