...
A table explaining the roles & responsibilities of SoC & RDKM in the collaboration zone is given below:
#
| Activity
| Owner
| Remarks
|
1
| SoC Collaboration zone creation
| RDKM
| RDKM will setup Collaboration space, access restrictions
|
2
| JIRA Project creation
| SoC
| JIRA project. SoC will be the owner for the JIRA project
|
3
| SoC meta-layer creation in collaboration zone
| SoC/RDKM
| RDKM will create the space and SoC push the code changes
|
4
| Device specific HAL repo creation
| SoC
| Create necessary device specific HAL implementation for porting RDK into Accelerator
|
5
| Share SoC SDK Artifacts
| SoC
| Which SDK version to be used. RDKM will support the integration with SoC libraries
|
6
| Manifest creation
| SoC
| Manifest for building the accelerator
|
7
| UI/UX(only for RDK licensee)
| RDKM/SoC
| Comes with pre-integrated UI’s, SoC and RDKM will discuss on the default UI
|
8
| Create RDK build from CMF GIT
| SoC/ RDKM
| Both teams work together to build Accelerator from CMF
|
9
| Provide Devices to RDKM team
| SoC
|
|
10
| Device flashing instructions / recovery mechanisms
| SoC
| SoC should share the device flashing instruction
|
11
| Sanity, Functionality Testing & automation tests
| RDKM/SoC
| RDK Certification Suite
|
12
| Monthly release & tagging
| SoC
| Monthly tagging and release with stakeholders along with test results
|
Click here for more details such as creating collaboration zone, creating user accounts for SoC Members, creating a JIRA project for SoC etc.
...
To match the layered structure of Yocto builds, a SoC specific layer is used to include SoC changes and additions. Use the yocto-layer create sub-command to create a new general layer.
$ yocto-layer create mylayer |
There shall be separate device (machine) configuration file (.conf) for each device for the particular chip family for which the layer is intended for. The general naming terminology for SoC layer is meta-rdk-SoC-<SoC name>
...