.. include:: /keyword.rst

=======================
Other Boards and Images
=======================

There are other recipes in |IOT-YOCTO| that supports different development boards and also different software packages.
This section shows how to build for different boards and build a different image.

.. warning::

	The boards listed below contains 3rd party boards and boards under development. There is no guarantee that these combinations
	would work out-of-box.


.. _machine-name-for-bitbake:

Build for Other Boards
======================

You can use the ``MACHINE`` variable to assign the board you would like to build:

.. prompt:: bash

	DISTRO=rity-demo MACHINE=<machine> bitbake rity-demo-image

The available values for ``<machine>`` can be found in the ``$BUILD_DIR/conf/local.conf`` configuration file. A snip of the file is shown below:

.. code-block::

    # uncomment the line related to the target
	#MACHINE ??= "genio-1200-evk"
	#MACHINE ??= "genio-350-evk"
	#MACHINE ??= "genio-510-evk"
	MACHINE ??= "genio-700-evk"

You can also locate all the reference IoT board recipes in:

``src/meta-mediatek-bsp/conf/machine/``

For example, if the ``.conf`` files in the directory are:

.. code:: text

	genio-1200-evk.conf -> mt8395-evk.conf
	genio-1200-evk-p1v1.conf -> mt8395-evk-p1v1.conf
	genio-1200-evk-ufs.conf -> mt8395-evk-ufs.conf
	genio-350-evk.conf -> mt8365-evk.conf
	genio-510-evk.conf -> mt8370-evk.conf
	genio-700-evk.conf -> mt8390-evk.conf
	mt8183-evb.conf
	mt8183-pumpkin.conf
	mt8365-evk.conf
	mt8365-pumpkin.conf
	mt8365-sb35.conf
	mt8370-evk.conf
	mt8390-evk.conf
	mt8395-evb-ufs.conf
	mt8395-evk.conf
	mt8395-evk-p1v1.conf
	mt8395-evk-ufs.conf
	mt8516-pumpkin.conf

Note that ``genio-1200-evk.conf`` is an alias to ``mt8395-evk.conf``. In this case, the following ``<machine>`` names are available:

* ``genio-1200-evk``
* ``mt8395-evk``

For details, please refer to the `BSP documentation <https://mediatek.gitlab.io/aiot/rity/meta-mediatek-bsp/boards/index.html>`_.

Other Images
------------

The |IOT-YOCTO| bringup image (``rity-bringup-image``) is mostly used for BSP development and board bringup.
The image contains the some tools necessary to validate software and hardware.

`rity-bringup-image` is designed to be built with the ``DISTRO`` variable set
to the following:

.. code::

	DISTRO=rity-bringup

You can use the following command to build the `rity-bringup-image`:

.. prompt:: bash $

	DISTRO=rity-bringup MACHINE=<machine> bitbake rity-bringup-image

The resulting image is located in

.. code::

    $BUILD_DIR/tmp/deploy/images/<machine>

Please note that the same image directory may contain multiple distro images.

For example, if you build both ``rity-demo-image`` and ``rity-bringup-image`` for g350-EVK:

.. prompt:: bash $

	DISTRO=rity-demo MACHINE=g350-evk bitbake rity-demo-image
	DISTRO=rity-bringup MACHINE=g350-evk bitbake rity-bringup-image

The image directory ``$BUILD_DIR/tmp/deploy/images/g350-evk`` contains both images. 
You can use ``genio-flash-tool -i <image-name>`` to select the image you want to flash.
For example, to flash ``rity-bring-image``, use:

.. prompt:: bash $

	genio-flash -i rity-bringup-image

For more details, please refer to :doc:`/tools/genio-tools` page.