# Renesas R-Car M3 Starter Kit Pro

**URL:** <https://hub.mender.io/t/renesas-r-car-m3-starter-kit-pro/71>\
**Category:** Yocto Project\
**Tags:** yocto, sumo, rocko\
**Created:** [October 1, 2018, 9:27pm UTC](https://hub.mender.io/t/renesas-r-car-m3-starter-kit-pro/71 "2018-10-01T21:27:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [October 1, 2018, 9:27pm UTC](https://hub.mender.io/t/renesas-r-car-m3-starter-kit-pro/71/1 "2018-10-01T21:27:01Z")

</div>

# Board description

Renesas R-Car M3 Starter Kit Pro board is an evaluation board for the R-Car M3 SoC.

Renesas has developed R-Car starter kits for supporting automotive software development. These kits enable users to easily build automotive Linux platforms that are standardized by the Automotive Grade Linux (AGL) and GENIVI® open source communities and that are highly extensible and can be used for wide variety of applications.

![r-car-starter-kit-box](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/6beef82f28434815ba3bbcdbd041cf6cfa9be96c.jpeg)

URL: [https://www.renesas.com](https://www.renesas.com/us/en/solutions/automotive/adas/solution-kits/r-car-starter-kit.html)  
Wiki: [https://elinux.org/R-Car/Boards/M3SK#Introduction](https://elinux.org/R-Car/Boards/M3SK#Introduction)

# Test results

The Yocto Project releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other [Yocto Project releases](https://wiki.yoctoproject.org/wiki/Releases?target=_blank):

| Yocto Project | Build | Runtime |
| --- | --- | --- |
| sumo (2.5) | :test_works: | :test_unknown: |
| rocko (2.4) | :test_works: | :test_unknown: |

1. Have not had access to board earlier, but actually have now and will hopefully update above to green soon unless someone beats me to it.

**Build** Means that the Yocto Project build using this Mender integration completes without errors and outputs images.  
**Runtime** Means that Mender has been verified to work on the board. For U-Boot-based boards, the [integration checklist](https://docs.mender.io/devices/integrating-with-u-boot/integration-checklist?target=_blank) has been verified.

# Getting started

## Prerequisites

- A supported Linux distribution and dependencies installed on your workstation/laptop as described in the [Yocto Mega Manual](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#detailed-supported-distros)
  - NOTE. Instructions depend on which Yocto version you intend to use.

- Google repo tool [installed](https://hub.mender.io/t/google-repo/58/2) and in your `PATH` .

## Configuring the build

### Setup Yocto environment

Set the Yocto Project branch you are building for:

```auto
# set to your branch, make sure it is supported (see table above)
export BRANCH="sumo" 

```

Create a directory for your `mender-rcar-m3` setup to live in and clone the  
meta information.

```auto
mkdir mender-rcar-m3 && cd mender-rcar-m3

```

Initialize repo manifest:

```auto
repo init -u https://github.com/mendersoftware/meta-mender-community \
           -m meta-mender-renesas/scripts/manifest-renesas.xml \
           -b ${BRANCH}

```

Fetch layers in manifest:

```auto
repo sync

```

## Setup build environment

Initialize the build environment:

```auto
source setup-environment renesas

```

### Configure Mender server URL (optional)

This section is not required for a successful build but images that are generated by default are only suitable for usage with the Mender client in [Standalone deployments](https://docs.mender.io/architecture/standalone-deployments?target=_blank), due to lack of server configuration.

You can edit the `conf/local.conf` file to provide your Mender server configuration, ensuring the generated images and Mender Artifacts are connecting to the Mender server that you are using. There should already be a commented section in the generated `conf/local.conf` file and you can simply uncomment the relevant configuration options and assign appropriate values to them.

Build for Hosted Mender:

```auto
# To get your tenant token:
# - log in to https://hosted.mender.io
# - click your email at the top right and then "My organization"
# - press the "COPY TO CLIPBOARD"
# - assign content of clipboard to MENDER_TENANT_TOKEN
#
MENDER_SERVER_URL = "https://hosted.mender.io"
MENDER_TENANT_TOKEN = "<copy token here>"

```

Build for Mender demo server:

```auto
# https://docs.mender.io/getting-started/create-a-test-environment
#
# Update IP address to match the machine running the Mender demo server
MENDER_DEMO_HOST_IP_ADDRESS = "192.168.0.100"

```

### Building the image

You can now proceed with building an image:

```auto
MACHINE=m3ulcb bitbake core-image-base

```

Replace `core-image-base` with your desired image target.

### Using the build output

After a successful build, the images and build artifacts are:

- `tmp/deploy/images/m3ulcb/core-image-base-m3ulcb.sdimg`
- `tmp/deploy/images/m3ulcb/core-image-base-m3ulcb.mender`

The disk image (with `.sdimg` suffix) is used to provision the device storage for devices without Mender running already. Please proceed to [the official documentation on provisioning a new device](https://docs.mender.io/artifacts/provisioning-a-new-device?target=_blank)for steps to do this.

On the other hand, if you already have Mender running on your device and want to deploy a rootfs update using this build, you should use the [Mender Artifact](https://docs.mender.io/architecture/mender-artifacts?target=_blank) files, which have `.mender` suffix. You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client only in [Standalone deployments](https://docs.mender.io/architecture/standalone-deployments?target=_blank).

# References

- The Mender integration layer for Renesas R-Car M3 Starter Kit Pro and template files can be found in [meta-mender-community](https://github.com/mendersoftware/meta-mender-community/tree/sumo/meta-mender-renesas).
- The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is simply a board-specific complement to the official documentation.

* * *

_If this post was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!_