...
Build Steps to build RDKstarboard with Amlogic pre-builds(github) and non-drm :
- repo init -u https://code.rdkcentral.com/r/rdk/soc/amlogic/aml-manifests -b rdk-next -m aml_ipstb_google_rdk_starboard-open.xml
- repo sync -c
- For Amlogic UI:
source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --gst1-18 --ipclient --rdk-starboard
For RDK UI:
source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --gst1-18 --ipclient --rdk-starboard --use-rdk-ui - bitbake lib32-rdk-generic-mediaclient-image
|
|---|
IPSTB build on rdk-next stack:
Build steps with DRM:
- repo init -u https://code.rdkcentral.com/r/collaboration/soc/amlogic/aml-accel-manifests -b rdk-next -m ipstb-google-rdk-next.xml
- repo sync -j4 --no-clone-bundle
- source meta-rdk-aml/set-env.sh mesonsc2-5.4-lib32-ah212 --use-rdk-ui --enable-rdk-voice --playready --widevine --enable-fireboltcompliance --rdk-starboard --t4hremote --ipclient
(NOTE: Use --b12remote instead of --t4hremote if B12 remote is used) - bitbake lib32-rdk-generic-mediaclient-tdk-image
|
|---|
Amlogic meta layers are in AML collaboration zone and it need 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
Flashing Steps:
1) Using Burning tool:
...
