RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
Expand | ||
---|---|---|
| ||
SoC users can sign up at https://wiki.rdkcentral.com/signup.action to create a user account in RDK. For any issues faced, a mail can be sent to support@rdkcentral.com |
Expand | ||
---|---|---|
| ||
An INFRA ticket needs to be raised at https://jira.rdkcentral.com with the below details:
For any issues faced, a mail can be sent to support@rdkcentral.com |
Expand | ||
---|---|---|
| ||
An INFRA ticket needs to be raised at https://jira.rdkcentral.com to create a JIRA project for SoC. Once approvals are received along with required access restrictions, the project will be created. For any issues faced, a mail can be sent to support@rdkcentral.com |
Expand | ||
---|---|---|
| ||
To get a Git repository a request needs to be raised to CMF team using the CMFSUPPORT ticket at https://jira.rdkcentral.com. Once approvals are received along with required access restrictions, the repo will be created. Any changes in merge permissions can be requested in same ticket. For creating any specific branches in the repo, another ticket in the same CMFSUPPORT can be raised. For any issues faced, a mail can be sent to support@rdkcentral.com Once the git repo is created, it can be accessed at https://code.rdkcentral.com |
Expand | ||
---|---|---|
| ||
An INFRA ticket needs to be raised at https://jira.rdkcentral.com to get access to SDK Artifacts. Once approvals are received along with required access restrictions, the access should be in place. For any issues faced, a mail can be sent to support@rdkcentral.com |
Click here for more details such as creating collaboration zone, creating user accounts for SoC Members, creating a JIRA project for SoC etc.
Once the product features are decided, the device engineering can be started. SoC needs to decide on the hardware layout that incorporates components to the target board. Device will be categorized as Low Profile and High Profile device based on the hardware capabilities. In a low profile device 4k support might be optional but it is expected to have 4k support in high profile device.
<need to add table-discuss>
SoC can make use of the below details available to start developing a Yocto build to engineer the device firmware builds based on RDK Yocto build setup.
...
Yocto based RDK builds are flexible enough to easily accommodate SoC / OEM / MSO / third party changes. The starting point for the Yocto builds are a manifest file. The manifest file is an xml file that contains details of the different open embedded Yocto build layers, meta layers , rdk as well as open source components that needs to be fetched during initial stages ( than during bitbake time ) as well as the URL locations from where the data can be pulled. A set of sample manifests that can be used as a template for developing SoC specific manifests are given below Click
Expand | ||
---|---|---|
|
...
For more details on getting RDK-B ported to an OEM device, please refer the links RDK-B SoC Specific Porting and Guideline for SoC and OEM Vendors
SoC/OEM meta-layer creation
...
|
The default manifest repo in RDKM Git is at https://code.rdkcentral.com/r/#/c/manifests/ . SoC can use the 'collaboration' sub section in this repo to add their platform specific manifests which will be under collaboration zone restrictions . The location will be https://code.rdkcentral.com/r/collaboration/SoC/<platform>/<platform-manifests>
For more details on getting RDK-B ported to an OEM device, please refer the links RDK-B SoC Specific Porting and Guideline for SoC and OEM Vendors
SoC/OEM meta-layer creation
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>
The device (machine) configuration file shall include corresponding include (.inc) file to get machine configuration details.
Expand | |||
---|---|---|---|
| |||
Adding a new machine to Yocto involves the following:Create a new layer which will hold all the recipes and machine configurations for the new SoC/OEMyocto-layer command is not enabled by default, If you want to add a new layer using the "yocto-layer" script, you need to first download the poky and put it in your code base and run the script to create a new folder. You can download poky from git using :
Use the yocto-layer create sub-command to create a new general layer. $ yocto-layer create mylayer <specify the layer which you need to be created> Please enter the layer priority you'd like to use for the layer: [default: 6] 6 There shall be separate device (machine) configuration file (.conf) for each device for the particular chip family for which the layer is intended for. For Eg : A layer "meta-rdk-oem-OEM-X-SOC-Y" means this layer shall be able to build any devices manufactured by OEM "X" with all variants of SoC "Y" like Y-1,Y-2 etc The device (machine) configuration file shall include corresponding include (.inc) file to get machine configuration details. Adding the Machine Configuration File for the new SoC/OEMTo add a machine configuration, you need to add a .conf file with details of the device being added to the conf/machine/ file. The most important variables to set in this file are as follows:
You might also need these variables:
Adding a Kernel for the MachineThe OpenEmbedded build system needs to be able to build a kernel for the machine. We need to either create a new kernel recipe for this machine, or extend an existing recipe.We can find several kernel examples in the source The directory at meta/recipes-kernel/linux that you can use as references. If you are creating a new recipe, following steps need to be done,
If you are extending an existing kernel, it is usually a matter of adding a suitable defconfig file. The file needs to be added into a location similar to defconfig files used for other machines in a given kernel. A possible way to do this is by listing the file in the SRC_URI and adding the machine to the expression in COMPATIBLE_MACHINE:
Adding Recipe for SoC/OEMThe following kind of recipes can be added to SoC/OEM layer. The recipes shall be grouped as described in slide “BSP Reference Layer”
Creating packages for building imagesCreate a custom packagegroup for the SoC/OEM which shall list all the recipes that are required for this image. For example, the following recipe can be appended to the broadband package group.
Create a custom image for required SoC/OEM. For example:
Adding your own custom layerUse the yocto-layer create sub-command to create a new |
...
layer.
|
...
Add this to ./meta-rdk/conf/bblayers.conf.sample. Recipes can be placed inside recipes-< > folders. There can be a configuration file inside conf/ for layer specific configuration and classes folder for keeping information that is useful to share between metadata files. |
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>
The device (machine) configuration file shall include corresponding include (.inc) file to get machine configuration details.
...
...