Page Comparison

Attention!!:   AGL  AGL IC container integration update is under reviewing,  Please not use this document was merged only master. Please use master now.

This document describe how to build AGL instrument cluster with container integration.

...

No.	Type name	Detail of type	Required storage (SD card) size - board.	Build time AMD R9 5900HX /64GByte RAM	Required storage size-build.
1	Simple container host	This integration aim to core package definition for container host using LXC.  This integration is not include demo package. This integration aim to define starting point for downstream product development.	1G Byte		150GByte	Console only.
2a	Instrument cluster with four simple demo IVI install to one partition.	This integration aim to get most simple integration with demo feature.  This container runtime and management is constructed with LXC package only.  On the other hand, it has limitation for supported use case.  This integration support two demo guest run in one board (instrument cluster guest and momi IVI guest). This integration aim to learn drm lease and LXC container by developer.	2GByte	2h	300GByte
3a	Instrument cluster with demo IVI install to one by one partition.	This integration aim to get simple integration with demo feature.  This container runtime and management is constructed with container management daemon with liblxc.  This integration will improve to support many embedded use case.  This integration support two demo guest run in one board (instrument cluster guest and momi IVI guest). This integration aim to learn and develop AGL IC container integration by developer.	16GByte (Including pre-allocated partition for 3 guests.)	2h	300GByte
3b	Instrument cluster with four demo IVI install to one by one partition.	This integration aim to get full demo integration with AGL demo IVI.  This integration is extend from 3a integration.  This integration support instrument cluster guest and four IVI guest (momi, qt, flutter, html5).   This integration aim to use AGL demonstration in each event by developer.	16GByte	3a+6h	600GByte

We recommend to choice 3a.  It can extend to 3b.

...

6th step: Download the AGL Source Files

Recommend AGL version: Optimistic Octopus

cd $AGL_TOP
mkdir octopus
export AGL_TOP=$HOME/AGL/octopus
cd $AGL_TOP
repo init -b octopus -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
repo sync

Optional: Specify the master branch

...

4. Extra step for type 3b build.

Attention!!:

This step has some issue. This extra step can select 4a or 4b.  When you want to build AGL demo IVI guest shall use tested stable version or stable pre build image, shall not use same as IC side recipe tree.  Need to update section 4 procudere. Now discuss how to provide prebuild guestcontainer guest in myself, please select 4a work flow.  When you want to create AGL IC container demo quicly, please select 4b work flow.

Typically 4a step require long build time about 6h.  When you want to build AGL Ref HW/ SK+ Kinfgisher software, you can't select select 4b work flow that depend to Renesas propriety license limitation.

4a. Extra step for type 3b build myself.

1st step: Configure 2nd build tree.

We recommend to open new terminal to do this extra section.

Recommend AGL version: Optimistic Octopus

export AGL_TOP=$HOME/AGL/octopus
cd $AGL_TOP

Optional: Specify the master branch

...

source meta-agl/scripts/aglsetup.sh -f -m raspberrypi4 -b build-ivi-rpi4 agl-container-guest-demo agl-demo

2nd step: Build target images.

Type 3b integration need to build 3 image, these image are agl-ivi-demo-platform, agl-ivi-demo-platform-flutter and agl-ivi-demo-platform-html5.

bitbake agl-ivi-demo-platform
bitbake agl-ivi-demo-platform-flutter
bitbake agl-ivi-demo-platform-html5

3rd step: Set deploy path of AGL IVI Demo to IC side config.

Type 3b integration refer to IVI pre build image.  Please set IVI side deploy directory in ic side local.conf (or site.conf).

...

OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR = "/home/user/AGL/octopus/build-ivi-rpi4/tmp/deploy"

4th step: Build all in one image (3b).

Back to terminal for ic build.

bitbake agl-instrument-cluster-container-demo

...

4b. Extra step for type 3b using pre build image

...

.

The 4b can select Raspberry Pi 4 board only, this limitation depend to Renesas propriety license limitation.

1st step: Download stable

...

prebuild image from AGL site.

Download IVI guest images from this link.

Prebuild AGL Demo IVI container images for Raspberry Pi 4.

Extract download tar.bz2 archive to any directory.

cd /path/to/directory/
tar xvJf /path/to/download/agl-demo-ivi-container-guest-raspberrypi4-64.tar.bz2

2nd step:

...

 Set deploy path of AGL IVI Demo to IC side config.

Set extracted directory using OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR in local.conf (or site.conf).

5. Write imgae to SD card.

...

OUT_OF_TREE_CONTAINER_IMAGE_DEPLOY_DIR="/path/to/directory/prebuild/"

3rd step: Build all in one image (3b).

Back to terminal for ic build.

bitbake agl-instrument-cluster-container-demo

5. Write image to SD card.

The 3a and 3b image is constructed by wic image, that include partition table and each partition data into one image file.

In default setting, that wic image is compressed xz.  When that wic image write to SD card, you need to use xzcat ant dd command in build PC.

sudo bash -c "xzcat /path/to/image/directory/agl-instrument-cluster-container-demo-XXXXX.wic.xz | dd of=/dev/sdXXX bs=128M"

If you are missing to set SD card device "/dev/sdXXX", it cause SSD/HDD data break (only logical, not physical).

For example;

A /dev/sda is SSD for your PC.  A /dev/sdb is SD card.  You should use /dev/sdb, must not use /dev/sda.

When your PC has direct SD card interface not a use card reader, your SD card device is /dev/mmcblkX may be.

6. Power on.

7. How to use container exchange UI.

7a. Momi Web

The Momi web is a web interface for container exchange.  When you want to use Momi web, you must connect network between board and PC/Tablet/Phone.

The Momi web is completely demo feature, that open many security hole.  You shall not use out of standalone demo.

1st step: Check IP address in your board.

After booting, you check IP address in your board.

root@raspberrypi4-64:~# ifconfig
eth0      Link encap:Ethernet  HWaddr E4:XX:YY:ZZ:WW:VV
          inet addr:192.168.10.128  Bcast:192.168.10.255  Mask:255.255.255.0

In this case, this board set IP address by 192.168.10.128.

2nd step: Connect to board using web browser.

Open "http://a.b.c.d:8080".  When a board is set IP address 192.168.10.128, you open "http://192.168.10.128:8080".

When you success to connect to board, your web browser show these web UI.

PC View

Image Added

Mobile View

Image Added

7b. Keyboard Interface

Please refer to Appendix 3.

Appendix.1. 

...

Typical HW set.

AGL Ref HW.

Raspberry PI4

Appendix.2. Cluster with IVI Containers View.

Qt IVI

Image Added

Flutter IVI

Image Added

HTML5 IVI

Image Added

Momi IVI

Image Added

Appendix 3. How to configure Special Keyboard.

How to get configuration tool.

This description is targeting to this type of special keyboard. 

The usb-12key-kbd-prog is unofficial community tool of this key board that is possible to use linux.  Official windows tool is possible to get official site.

Usage of usb-12key-kbd-prog is please refer to upstream site.

Upstream:
https://github.com/NeoCat/usb-12key-kbd-prog

Key Map.