64bit Arch support for dunfell build in RPI4

Host Setup

The OpenEmbedded build system should be able to run on Ubuntu 18.04 distribution/other compatible linux distribution with the following versions for Git, tar, and Python.

• Git 1.8.3.1 or greater
• tar 1.27 or greater
• Python 3.4.0 or greater
• Coreutils(E.g realpath)

Note: You should also have about 50 Gbytes of free disk space for building images.

The essential packages you need for a supported Ubuntu or Debian distribution are shown in the following command:

$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \
  build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \
  xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \
  pylint3 xterm bmap-tools


$ sudo apt-get install git cmake autoconf texinfo openjdk-8-jdk openjdk-8-jre \
  m4 libtool libtool-bin curl pkg-config lib32z1 doxygen

Repo Setup

In order to use Yocto build system, the repo tool must be properly installed on the machine.

To install Repo make sure you have a /bin directory in your home directory and that it is included in your path

$ mkdir ~/bin
$ PATH=~/bin:$PATH
Download the repo tool and ensure that it is executable
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Note: it is also recommended to put credentials in ~/.netrc when interacting with repo.

A sample ~/.netrc file is illustrated below

machine code.rdkcentral.com login YOUR_USERNAME password YOUR_PASSWORD

Yocto Build Steps

To build, follow below instructions

$ mkdir <workspace dir>
$ cd <workspace dir>
$ repo init -u https://code.rdkcentral.com/r/manifests -b dunfell -m rdkb-extsrc.xml
$ repo sync -j`nproc` --no-clone-bundle

$ cd ~/rdkb/components/opensource/ccsp/CcspPandM
$ git fetch https://code.rdkcentral.com/r/rdkb/components/opensource/ccsp/CcspPandM refs/changes/04/62804/3 && git cherry-pick FETCH_HEAD

Note : The above bug fixes changes are temporary given as instructions. This is not required once the change is gets merged into the appropriate repo.

$ MACHINE=raspberrypi4-64-rdk-broadband source meta-cmf-raspberrypi/setup-environment
$ bitbake rdk-generic-broadband-image

Flashing Procedure

Following command can be used to flash the RPI image to sd card using linux machine . bmap tool should be available in linux

bzip2 -d <path to ImageName.wic.bz2>
sudo -E bmaptool copy --nobmap <path to ImageName.wic> <path to SD card space>

Example:

$ bzip2 -d rdk-generic-broadband-image-raspberrypi4-64-rdk-broadband.wic.bz2
$ sudo -E bmaptool copy --nobmap rdk-generic-broadband-image-raspberrypi4-64-rdk-broadband.wic /dev/sdb

Errors and Challenges

Sanity Testing

1.  Sanity test cases are validated on 64bit aarch in RPI4. It includes,
   
   1.  All ccsp components are running on board
   2.  All ccsp components DM parameters are able to access properly
   3.  Able to connect the wireless clients
   4.  Able to access the WebUI via RM
   5.  Able to access the WebUI in connected clients using gateway ip
   6.  Internet is working on board
   7.  WAN connection is working on connected clients
   8.   iptables are loaded properly
   9.  Able to tab all the pages in WebUI without any crash
   10.  Able to get all the interfaces
   11.  Able to get the erouter0 IP address
   12.  Able to take ssh access via erouter0 IP Address
   13.  All ccsp component log files are generated under the /rdklogs/logs folder
   14.  Enabled rbus - all ccsp components are communicated via rbus
   15. udhcpc,dnsmasq,lighttpd process are running
   16. captiveportal page is loaded properly on wireless clients for initial connect

Known Issues

1.  E2E validation is not performed yet on 64bit aarch in RPI4 
2.  sometimes , rpi board is rebooting without giving reboot command
3.  Observing CR crash when we enabled the dbus only 
4.  None of the ccsp components are not started due to CR crash(if dbus only enabled)