Mistake on this page? Email us

Production images

Tip: If you downloaded an evaluation image, you can skip the build stage and go directly to writing.

Compared to the development image, the production image has fewer packages and applications: it does not include tools and configurations used to help development and debugging.

Configuring production images

Production images include the following extra security features (compared to the development image):

  • Root user login with password only enabled on the Kernel Linux serial console interface: You must provide a file containing the plain text password (minimum 12 characters) to run-me.sh. Use the parameter --root-passwd-file PASSWD_FILE.

  • Only the Ethernet debug interface accepts the following: SSH connections (and only with key-pair authentication, because password logins are disabled), Link Local IPv6 addressing and mDNS Responder traffic.

    • This feature is controlled by the variable MBL_PRODUCTION_ETH_DBG set in the mbl-production configuration file (meta-mbl/meta-mbl-distro/conf/distro/include/mbl-distro-production.inc). The gadget Ethernet is used by default for platforms that include the usbgadget (imx7d-pico-mbl, imx6ul-pico-mbl and imx8mmevk-mbl). Otherwise, you must use a USB-to-Ethernet adapter.
    • Pass an SSH authorized_keys file for each user to run-me.sh. The format of the SSH public key filename is username_something. The username is mandatory; it allows the installing function to identify which user's home directory the public key should be copied to. To generate the SSH key-pair for the root user, you can use ssh-keygen -t rsa -f root_id_rsa -C'' and pass the parameter --ssh-auth-keys root_id_rsa.pub to run-me.sh.
  • System log level messages output and configuration: The following variables are set in the mbl-production configuration file (meta-mbl/meta-mbl-distro/conf/distro/include/mbl-distro-production.inc):

    • ATF_PRODUCTION_CFG: Affects ATF log level messages. The only possible value is silent (set by default) - only error messages are printed out to the console.

    • OPTEE_PRODUCTION_CFG: Affects OPTEE-OS log level messages. The only possible value is silent (set by default) - only error messages are printed out to the console.

    • UBOOT_PRODUCTION_CFG: Affects both U-Boot and Linux Kernel log level messages. The possible values are:

      • silent (default): Disables both U-Boot and kernel message output.
      • noconsole: Disables only U-Boot message output.

      Note that silent and noconsole are mutually exclusive.

      • minimal (default): Disables network booting, fastboot, USB mass storage and device firmware upgrade (DFU) message output.

    You can set the log level variables by:

    • Manually editing the local.conf file inside the BitBake build directory. For example: ./build-pico7/machine-imx7d-pico-mbl/mbl-manifest/build-mbl-production/conf/local.conf.

    • Setting these variables in one of your repositories' configuration files:

      • In your layer.conf file in your meta layer repository.
      • In your local.conf file in your config repository.

      See the help on creating an example project for more information on these repositories.

    • Passing the --local-conf-data STRING parameter to build.sh.

      For example:

      ./mbl-tools/build/run-me.sh --builddir ./build-pico7 --outputdir ./artifacts-pico7 --root-passwd-file PASSWD_FILE --ssh-auth-keys root_id_rsa.pub -- --machine imx7d-pico-mbl --branch mbl-os-0.10 --distro mbl-production --local-conf-data "UBOOT_PRODUCTION_CFG=\"noconsole\"\nATF_PRODUCTION_CFG=\"\""
      

      Note that --local-conf-data needs to be passed every run.

Building the production image

To build production images, set the Yocto DISTRO to mbl-production (pass the --distro mbl-production parameter to build.sh).

Production image build examples

The following are examples of build commands to produce development images for supported platforms.

The examples assume:

  • You have an output directory for your machine, for example:
    • ./artifacts-pico7
    • ./artifacts-nxpimx8
    • ./artifacts-pico6
    • ./artifacts-rpi3
  • You have an SSH agent to access your own private repositories. For more information, see the GitHub SSH documentation.

PICO-PI with IMX7D

./mbl-tools/build/run-me.sh --builddir ./build-pico7 --outputdir ./artifacts-pico7 --root-passwd-file PASSWD_FILE --ssh-auth-keys root_id_rsa.pub -- --machine imx7d-pico-mbl --branch mbl-os-0.10 --distro mbl-production

PICO-PI with IMX6UL

./mbl-tools/build/run-me.sh --builddir ./build-pico6 --outputdir ./artifacts-pico6 --root-passwd-file PASSWD_FILE --ssh-auth-keys root_id_rsa.pub -- --machine imx6ul-pico-mbl --branch mbl-os-0.10 --distro mbl-production

NXP 8M Mini EVK

./mbl-tools/build/run-me.sh --builddir ./build-nxpimx --outputdir ./artifacts-nxpimx --root-passwd-file PASSWD_FILE --ssh-auth-keys root_id_rsa.pub -- --machine imx8mmevk-mbl --branch mbl-os-0.10 --distro mbl-production

Raspberry Pi 3

./mbl-tools/build/run-me.sh --builddir ./build-rpi3 --outputdir ./artifacts-rpi3 --root-passwd-file PASSWD_FILE --ssh-auth-keys root_id_rsa.pub -- --machine raspberrypi3-mbl --branch mbl-os-0.10 --distro mbl-production
Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.