GENIVI Development Platform GDP
Space shortcuts
Page tree
ConfigureSpace tools
Skip to end of metadata
Go to start of metadata

What is GDP Master?

The GDP Master is essentially a rolling release that holds the layers, recipes, and source code to build the GENIVI Development Platform. It is the "latest and greatest" software that is the basis for the versioned releases happening twice a year. These versioned releases are supported from the date of release to following release. The "Master" rolling release is largely unstable and used for development work. It is designed for;

  1. Developers who want to contribute to the development of automotive software components.

  2. Developers who want to contribute to the GDP project itself.

Master policies can be summarized in three points:

  1. There is only one working repository, that is Master. (Think of it as a 'head' on a git repo.)

  2. Everything goes to Master first.

  3. Only branches from Master are allowed. Branches are for testing, stabilization, release, maintenance, not for development.

To know more about Master maintenance please visit GDP Management wiki page.

The next planned release is GDP 12 and everything merged in Master will appear in GDP 12.

Master structure

  • The GENIVI GitHub account contains two code repositories relating to GDP:Branches: a branch is created in the top level of each repository for each release (and pre-release). Branches relating to a pre-release are removed when the next phase of that release is issued. All changes are pushed to master and not the branches.

    • genivi-dev-platform which contains the top level code for GDP.
    • meta-genivi-dev a git submodule of genivi-dev-platform supporting cross-architecture application development.

Generic Preparation

For all targets, the build needs the following preparation.

  • Install the required development tools on the host by executing the following command (or equivalent on your distro.  More information in Yocto Docs)
    $ sudo apt-get install gawk wget git diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev xterm

  • Clone genivi demo platform
    $ git clone https://github.com/GENIVI/genivi-dev-platform.git
    $ cd genivi-dev-platform

Now execute per-target instructions below and then come back here:

  • After executing bitbake of the image successfully, try your image. 

  • You can connect with SSH.  You may need to figure out the IP address assigned via DHCP by using your network router, or scanning, etc.

  • You can also usually connect with a serial link (see hardware specific instructions).
  • Remember that the initial user / password is root / root

Per-target instructions

QEMU x86_64

 Click here to expand...

For QEMU the build instructions are as follows:

Follow the generic instructions above.  For the init step do the following:

$ cd genivi-dev-platform
$ source ./init.sh qemux86-64

Bitbake the image:

$ bitbake genivi-dev-platform

To try the image, follow the Hardware and Software Setup instructions.

Renesas R-Car (Gen 3) M3 Starter Kit

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

At the moment, the following extra package also needs to be on your build machine:

    $ sudo apt-get install ImageMagick
 
Proceed as follows:
  • $ cd genivi-dev-platform
$ source ./init.sh r-car-m3-starter-kit
  • Obtain and Install Renesas Graphics Drivers

    Download the Click-through licensed Linux Drivers and Gfx/MMP packages for YBSP v2.17 (valid for GDP 12) from here and unzip them into a folder.

    $ cd <folder containing the two zip files>
    $ unzip -o R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip
    $ unzip -o R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip

    To install them into the correct place in the Yocto BSP a copy script is used.

    $ cd ../renesas-rcar-gen3

    If you have the click-through packages (no NDA):

    $ sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh <path to the folder containing the packages>

    If you have the Evaluation packages (with NDA):

    $ sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh <path to the folder containing the packages>

 

   Bitbake the image:

     $ bitbake genivi-dev-platform

 

 

Renesas R-Car (Gen 3) M3 Salvator-X

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

At the moment, the following extra package also needs to be on your build machine:

    $ sudo apt-get install ImageMagick
 
  • Initialise build environment
    $ cd genivi-dev-platform
$ source ./init.sh r-car-m3-starter-kit
  • Configure the build for M3 Salvator-X
    Until Salvator-X support is added to the GDP board template mechanism it is straight forward to reconfigure a M3 Starter Kit build (the target you passed as a parameter in the previous step) to build for M3 Salvator-X instead by editing the Yocto local.conf.

    To do that simply edit gdp-src-build/conf/local.conf to set the following MACHINE variable: 
    MACHINE = "salvator-x"
  • Obtain and Install Renesas Graphics Drivers

    Download the Click-through licensed Linux Drivers and Gfx/MMP packages for YBSP v2.17 from here and unzip them into a folder.

    $ cd <folder containing the two zip files>
    $ unzip -o R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip
    $ unzip -o R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip

    To install them into the correct place in the Yocto BSP a copy script is used.

    $ cd ../renesas-rcar-gen3

    If you have the click-through packages (no NDA):

    $ sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh <path to the folder containing the packages>

    If you have the Evaluation packages (with NDA):

    $ sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh <path to the folder containing the packages>

 

Renesas R-Car (Gen 3) H3 Salvator-X

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

At the moment, the following extra package also needs to be on your build machine:

    $ sudo apt-get install ImageMagick

  • Initialise build environment
    $ cd genivi-dev-platform
$ source ./init.sh r-car-m3-starter-kit
  • Configure the build for H3 Salvator-X
    Until Salvator-X support is added to the GDP board template mechanism it is straight forward to reconfigure a M3 Starter Kit build (the target you passed as a parameter in the previous step) to build for H3 Salvator-X instead by editing the Yocto local.conf.

    To do that simply edit gdp-src-build/conf/local.conf to set the following SOC_FAMILY and MACHINE variables: 
    # Select the H3 SoC
    SOC_FAMILY = "r8a7795"
    # Select the Salvator-X board
    MACHINE = "salvator-x"

  • Obtain and Install Renesas Graphics Drivers

    Download the Click-through licensed Linux Drivers and Gfx/MMP packages for YBSP v2.17 from here and unzip them into a folder.

    $ cd <folder containing the two zip files>
    $ unzip -o R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-*.zip
    $ unzip -o R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-*.zip

    To install them into the correct place in the Yocto BSP a copy script is used.

    $ cd ../renesas-rcar-gen3

    If you have the click-through packages (no NDA):

    $ sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh <path to the folder containing the packages> 

    If you have the Evaluation packages (with NDA):

    $ sh meta-rcar-gen3/docs/sample/copyscript/copy_proprietary_softwares.sh <path to the folder containing the packages>

Raspberry Pi 2

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

  • Initialise build environment
    $ cd genivi-dev-platform
    $ source ./init.sh raspberrypi2

Raspberry Pi 3

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.


  • Initialise build environment
    $ cd genivi-dev-platform
    $ source ./init.sh raspberrypi3

Intel Minnowboard Max

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

  • Initialise build environment
    $ cd genivi-dev-platform
$ source ./init.sh minnowboard

Qualcomm DragonBoard 410c

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.


  • Initialise build environment, making sure to read and accept the terms of the EULA first.
    $ cd genivi-dev-platform
$ source ./init.sh dragonboard-410c accept-eula

Renesas R-Car M2 Porter (supported on GDP 11 but not GDP 12)

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

Renesas R-Car E2 Silk  (supported on GDP 11 but not GDP 12)

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.


 

Renesas R-Car M2 Koelsch (supported on GDP 11 but not GDP 12)

 Click here to expand...

Follow the generic preparation instructions above.  Once you reach the init step do the following.

  • Correct meta-genivi-dev bug

   Apply the following patch

 

What will I find in Master?

GDP components are described in GDP in Detail wiki page.

Requests

Requests for the next GDP version, should be listed in GDP-154 - GDP Master requests TO DO . The requests will be processed and added first to GDP Master and then, according to the GDP policy, to the next release.