...
Build environment
Please register to code.rdkcentral.com and share to RDKM to enable Amlogic repo access. (Need Amlogic to approve access to the request).
On build machine, add code.rdkcental.com login in your netrc file.
ie vi ~/.netrc
Update ~/.ssh/config for Amlogic openlinux.
To access, Amlogic DRM, need to share ssh private key to Amlogic and get it enable for Openlinux access for Widevide,Playready,Secmem repos.
Configure it accordingly in ~/.ssh/config
Build Steps for rdk-next (Master)
Build Steps:
...
rdknext aml_ipstb_google_rdk_starboard.xml - rdkv-aml-open-va-google.xml
- repo sync -j4 --no-clone-bundle
- source ./meta-rdk-aml/set-env.sh mesonsc2-5.
4- 15-lib32-ah212 --use-rdk-ui --playready --
ipclient - widevine --rdk-starboard --enable-evergreen-full --enable-rialto --enable-webkit238 --enable-wper4 -
rdkui lib32genericmediaclient |
|---|
Note: To enable build with DRM(Playready & Widevine), Please
...
reach out to Amlogic for Openlinux access for DRM libraries. Need to have below repository access.
NOTE: Both Amlogic and RDKM teams enable MS12 audio on the build. To enable MS12 audio in the build, need to enable build option "--enable-dv-ms12" .
This may effect some of YTS tests with respect to partial audio to fail if no MS12 audio(though ms12 is not directly needed, due to audio path, it may need ms12 audio to enable).
Check if you have access to Amlogic restricted repos.
...
...
Please contact your Amlogic
...
sales or FAE teams
...
to get restricted DRM repo access if you do not have yet.
Build Steps for a stable Feature branch
...
|
rdk |
next |
aml_ipstb_google_rdk_starboard.xml - feature-rdkv-aml-open-va-google.xml
- repo sync -j4 --no-clone-bundle
- source ./meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --use-rdk-
|
ipclient - ui --playready --widevine --rdk-starboard --enable-evergreen-full --enable-rialto --enable-
|
gst1 |
18 |
rdk |
ui |
lib32 |
generic |
mediaclient
Build |
|---|
...
steps with ACK 5.15 branch |
|---|
u rdk aml_ipstb_google_rdk_starboard-open.xml- rdkv-aml-va-ack515rel-dunfell.xml
- repo sync
|
|---|
-c- -j4 --no-clone-bundle
- source ./
|
|---|
For Amlogic UI:source - meta-rdk-aml/set-env.sh mesonsc2-5.
|
|---|
4-gst1-18 --ipclient --rdk-starboard For RDK UI:source - use-rdk-ui --playready --widevine --rdk-starboard --enable-evergreen-full --enable-rialto --enable-webkit238 --enable-wper4 --ipstb --ipclient
- bitbake lib32-rdk-ipstb-oss-image
|
|---|
Note: To enable build with DRM(Playready & Widevine), Please reach out to Amlogic for Openlinux access for DRM libraries. Need to have below repository access.
Steps to build libloader-apps:
- Libloader-app recipe path: meta-rdk-video/recipes-extended/cobalt/libloader-app_24.lts.stable.bb
- Libloader-app append path: meta-rdk-aml
...
- /recipes-extended/cobalt/libloader-app_24.lts.stable.bbappend
- Cobalt plugin recipe path: meta-rdk-video/recipes-extended/cobalt/cobalt-plugin_git.bb
- RDK Starboard path: build/tmp/work/armv7at2hf-neon-rdkmllib32-linux-gnueabi/lib32-libloader-app/24.lts.stable+gitAUTOINC+ecdcfdb8e5_8e7fcc2fe2-40/git/third_party/starboard/rdk/shared/
- To build libloader-app or cobalt-plugin modules individually:
- bitbake lib32-libloader-app
- bitbake lib32-cobalt-plugin
- To make changes in Starboard module:
- Navigate to the starboard path - build/tmp/work/armv7at2hf-neon-rdkmllib32-linux-gnueabi/lib32-libloader-app/24.lts.stable+gitAUTOINC+ecdcfdb8e5_8e7fcc2fe2-40/git/third_party/starboard/rdk/shared/
- Make necessary changes
- Come back to build folder
- Re-compile and build again - bitbake lib32-libloader-app -c compile && bitbake lib32-libloader-app
Cobalt library path:
- Evergreen libloader-app library: build/tmp/work/armv7at2hf-neon-rdkmllib32-linux-gnueabi/lib32-libloader-app/24.lts.stable+gitAUTOINC+ecdcfdb8e5_8e7fcc2fe2-40/image/usr/lib/libloader_app.so
- Cobalt plugin library: build/tmp/work/armv7at2hf-neon-rdkmllib32-linux-gnueabi/lib32-cobalt-plugin/git+gitAUTOINC+8e7fcc2fe2-r0/image/usr/lib/wpeframework/plugins/libWPEFrameworkCobaltImpl.so
IPSTB Flashing Steps
Locate the Image file from build directory
The reference device Image shall be created under ${BUILDDIR}/tmp/deploy/images/<machine>/aml_upgrade_package.img which can be used to flash the device using below methods.
...
1) Using Burning tool:
Download AMlogic Burning tool from the link Amlogic Video Accelerator Collaboration).
NOTE: Please reachout to Amlogic to get USB Burning tool if no access to the wiki page.
How to flash X4-SC2 image
...
Connect all necessary cables to AH212 box as below. It’s easy to do with place AH212 up-side-down.
...