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. Changes go through basic build & run testing before ending up and the master branch, and we try to keep GDP Master relatively stable. It is therefore recommended to use Master for your development and trials on GDP. Most of the time this is your best choice!
Master is designed for;
Developers who want to develop automotive software components.
Developers who want to contribute to the GDP project itself.
Master policies can be summarized in these points:
There is one main branch on the repository, master, supporting all hardware targets.
- We may use feature branches, temporarily, to prepare a larger work before merging to master.
Most things go to Master directly, after having been provided as a Pull Request, and tested.
- We also use release/maintenance branches. The README and the next chapter clarifies the extent of backports.
- Released versions are tagged. Remember that using master is most of the time recommended.
Releases and support
GDP is a community project and all adopters will get out of it what you put into it. Based on current contribution levels and contracted developers the following is the expected "support level" for processing bugs and change requests, and for backporting fixes to older versions. The main focus is on the latest Master development at any time, not on supporting older releases. With your community input, any of those things can be changed of course.
With the current resources we can only fully support the most recent full release plus GDP Master development, with critical bug fixes introduced also into the previous release.
In other words after release "n" has been officially released:
- GDP <n-1> – critical bugfixes only. Limited testing (those that still depend on n-1 need to support the testing efforts and report results)
- GDP <n> – supported
- GDP <n+1> – under current development = GDP Master
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
Renesas R-Car (Gen 3) M3 Starter Kit
Renesas R-Car (Gen 3) H3 Starter Kit
Renesas R-Car (Gen 3) M3 Salvator-X
Renesas R-Car (Gen 3) H3 Salvator-X
Raspberry Pi 2
Raspberry Pi 3
Intel Minnowboard Max/Turbot
Qualcomm DragonBoard 410c
Renesas R-Car M2 Porter (supported on GDP 11 but not GDP 12)
Renesas R-Car E2 Silk (supported on GDP 11 but not GDP 12)
Renesas R-Car M2 Koelsch (supported on GDP 11 but not GDP 12)
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 created as JIRA tickets in the GDP project, with the Feature type. It might be useful to first explain your proposal on the relevant mailing list
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.