...

Build Steps

...

Default with out DRM enabled with RDK reference UI

...

repo init -u https://code.rdkcentral.com/r/rdk/soc/amlogic/aml-manifests -b rdk-next -m aml_ipstb_google_rdk_starboard.xml  repo sync -j4 --no-clone-bundle source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --ipclient --rdk-starboard --rdk-ui bitbake lib32-rdk-generic-mediaclient-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.

Check if you have access to Amlogic restricted repos.

...

Execute below command to check if  you have PlayReady access git clone ssh://git@openlinux.amlogic.com/vendor/playready.git   Execute below command to check if you have Widevine access git clone ssh://git@openlinux.amlogic.com/yocto/vendor/widevine

...

Please contact your Amlogic

...

sales or FAE teams

...

to get restricted DRM repo access if you do not have yet.

If Widevine and PlayReady access is available, please pass additional arguments as

repo init -u https://code.rdkcentral.com/r/rdk/soc/amlogic/aml-manifests -b rdk-next -m aml_ipstb_google_rdk_starboard.xml  repo sync -j4 --no-clone-bundle source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --ipclient --playready --widevine --rdk-starboard --gst1-18 --rdk-ui --playready --widevine bitbake lib32-rdk-generic-mediaclient-image

Refer IPSTB Flashing Steps to flash the image after build has been finished successfully.

Build Steps to build RDKstarboard with Amlogic pre-builds(github) and non-drm:

Refer IPSTB Flashing Steps to flash the image after build has been finished successfully.

Build Steps to generate an image with RDKstarboard using Amlogic pre-builds(github), non-drm and with DAB support enabled

repo init -u https://code.rdkcentral.com/r/rdk/soc/amlogic/aml-manifests -b rdk-next -m aml_ipstb_google_rdk_starboard-open-dab.xml
repo sync -j4 --no-clone-bundle

For Amlogic UI:
source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --gst1-18 --ipclient --rdk-starboard --enable-dab-bridge

For RDK UI:
source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --gst1-18 --ipclient --rdk-starboard --enable-dab-bridge --use-rdk-ui



bitbake lib32-rdk-generic-mediaclient-image

Note: If you are seeing following error while bitbake parse happens; please enable meta-rust manually after "source" step before "bitbake".

ERROR: ParseError at /home/amadha013/codebase/ah212-rdknext-dab/meta-dab/dab-rs/dab-bridge_0.4.0.bb:3: Could not inherit file classes/cargo.bbclass

Edit $BUILDDIR/conf/bblayers.conf to enable meta-rust manually by adding below change:

BBLAYERS += "${RDKROOT}/meta-rust"

Refer IPSTB Flashing Steps to flash the image after build has been finished successfully.

IPSTB build on rdk-next stack:

Build steps with DRM:

Build steps with non-DRM:

Note: Amlogic meta layers and components are in AML collaboration zone and it need Amlogic collaboration zone. Need to be Amlogic collab-zone approved member to be able to get access.

RDK uses rdkcentral artifactory to place AlexaSmartScreenVoiceChrome-1.1.0.tar. Removed this depending upon ipclient distro. During build we need to place the tar file in downloads folder

...

Refer IPSTB Flashing Steps to flash the image after build has been finished successfully.

...

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.

...