Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel3

...

Build Steps

...

Opensourced Manifest:

rdk/soc/amlogic/aml-manifestsnext
  • google-collab -m aml_ipstb_google_rdk_starboard-open.
xml 
  • xml
  • repo sync -
j4 --no-clone-bundle
  • c
  • source meta-rdk-
aml
  • amlogic/set-env.sh mesonsc2-5.4-lib32-ah212 --gst1-18 --ipclient --rdk-starboard --use-rdk-ui --rdk-cobalt23
  • bitbake lib32-rdk-generic-mediaclient-image

Above manifest hosts Amlogic pre-built libraries for kernel and other SoC components.


For latest Cobalt builds which included latest RDK and latest Amlogic BSP included, please reachout to Amlogic FAE or RDKM team(support@rdkcentral.com)

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.


For certified manifest with DRM: 

Check if you have access to Amlogic restricted repos.

...

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 --gst1-18 --rdk-ui --playready --widevine
bitbake lib32-rdk-generic-mediaclient-image

Note: This manifest is based on RDK 2022q1 based RDK and Amlogic BSP version is BSP866. This manifest is in RDKM restricted zone. 

Build Steps to

...

generate an image with RDKstarboard using Amlogic pre-builds(github)

...

, non-drm

...

and with DAB support enabled

Code Block
languagebash
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

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

...

languagebash

...

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

Code Block
languagebash
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:

Code Block
languagebash
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:

...

...

  •  -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

...

Build steps with non-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  t4hremote --ipclient
    (NOTE: Use --b12remote instead of --t4hremote if B12 remote is used)
  • bitbake lib32-rdk-generic-mediaclient-tdk-image

...

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.


Cobalt relative binaries location/path on the device :

Library: /usr/lib/libloader_app.so.
In evergreen enabled images we do not have separate libcobalt.so libraries.
Build path: build/tmp/work/armv7at2hf-neon-rdkmllib32-linux-gnueabi/lib32-libloader-app/23.lts.stable-3/image/usr/lib/libloader_app.so

In Amlogic the installation slots are present at /data/persistent/Cobalt-0/.cobalt_storage
/data/persistent/Cobalt-0/.cobalt_storage is created run-time.

root@AmlogicFirebolt:~# ls -l /data/persistent/Cobalt-0/.cobalt_storage
drwx------    2 root     root          4096 Aug  4 08:55 cobalt_updater
drwx------    4 root     root          4096 Aug  4 08:55 installation_1
drwx------    2 root     root          4096 Aug  4 08:48 installation_2
-rw-------    1 root     root            20 Aug  4 08:55 installation_store_aHR0cHM6Ly93d3cueW91dHViZS5jb20vdHY=.pb
root@AmlogicFirebolt:~#
root@AmlogicFirebolt:~# ls /usr/lib/libloader_app.so
/usr/lib/libloader_app.so
root@AmlogicFirebolt:~#


...

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.

...