Skip to content
Repo manifest and scripts for Linux microPlatform.
Shell Dockerfile
Branch: master
Clone or download
ricardosalveti default.xml: update meta-lmp layer
Relevant changes:
- 4194279 aktualizr: lite: fix incorrect storing of ecu hwid

Signed-off-by: Ricardo Salveti <>
Latest commit e50abf6 Aug 14, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
conf local.conf: add instructions for auto docker prune timer config Jul 26, 2019
Dockerfile Dockerfile: Move to latest LTS Mar 7, 2019
LICENSE LICENSE: clarify origin Oct 10, 2017 README: update supported hardware Aug 13, 2019
default.xml default.xml: update meta-lmp layer Aug 15, 2019
git-mirrors.yml Drop meta-96boards, not supported anymore Jul 25, 2019
setup-environment-internal setup-environment-internal: fix typo Jan 17, 2019

Linux microPlatform Manifest Linux microPlatform manifest.

This directory contains a Repo manifest and setup scripts for the Linux microPlatform build system. If you want to modify, extend or port Linux microPlatform to a new hardware platform, this is the manifest repository to use.

The build system uses various components from the Yocto Project, most importantly the OpenEmbedded build system, the bitbake task executor and various application and BSP layers.

To configure the scripts and download the build metadata, do:

mkdir ~/bin

curl > ~/bin/repo
chmod a+x ~/bin/repo

Run repo init to bring down the latest stable version of Repo. You must specify a URL for the manifest, which specifies the various repositories that will be placed within your working directory.

To check out the latest LMP subscriber continuous release:

repo init -u

A successful initialization will end with a message stating that Repo is initialized in your working directory. Your client directory should now contain a .repo directory where files such as the manifest will be kept.

To pull down the metadata sources to your working directory from the repositories as specified in the Linux microPlatform manifest, run:

repo sync

When downloading from behind a proxy (which is common in some corporate environments), it might be necessary to explicitly specify the proxy that is then used by repo:

export HTTP_PROXY=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>
export HTTPS_PROXY=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>

More rarely, Linux clients experience connectivity issues, getting stuck in the middle of downloads (typically during "Receiving objects"). It has been reported that tweaking the settings of the TCP/IP stack and using non-parallel commands can improve the situation. You need root access to modify the TCP setting:

sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo sync -j1

Setup Environment

Supported MACHINE targets (officially tested by FIO):

  • beaglebone-yocto
  • cl-som-imx7
  • colibri-imx7
  • cubox-i
  • freedom-u540
  • intel-corei7-64
  • qemuriscv64
  • raspberrypi3-64

Supported image targets:

  • lmp-mini-image
  • lmp-gateway-image

The default distribution (DISTRO) variable is automatically set to lmp, which is provided by the meta-lmp layer.

Setup the work environment by using the setup-environment script:

[MACHINE=<MACHINE>] source setup-environment [BUILDDIR]

If MACHINE is not provided, the script will list all possible machines and force one to be selected.

To build the Linux microPlatform gateway image:

bitbake lmp-gateway-image

Issues and Support

Please report any bugs, issues or suggestions at

You can’t perform that action at this time.