Page History

...

The default ARM build have been updated to include additional features such as  erouter0, Captive Portal and WebUI support.

The required PRs to be cherry-picked

 https://github.com/rdkcentral/ethernet-agent/pull/40
 https://github.com/rdkcentral/meta-rdk-bsp-arm/pull/4
 https://github.com/rdkcentral/meta-rdk-bsp-arm/pull/7
 https://github.com/rdkcentral/meta-rdk-bsp-arm/pull/8
 https://github.com/rdkcentral/webui/pull/81
 https://github.com/rdkcentral/meta-rdk-bsp-arm/pull/11

There are two types of build outputs:

...

To generate an image for another machine, specify the MACHINE environment variable when sourcing setup-environment:

MACHINE="raspberrypi64-rdk-broadband" source meta-rdk-bsp-arm/setup-environment

...

...

 All machine configurations for RDK-B inherit from armefi64-rdk-broadband.

Unless the machine configuration has specific overrides, the operating system image (kernel + rootfs + boot manager) generated by configurations like raspberrypi64-rdk-broadband will be identical to that of the generic machine. Only the platform firmware binaries will be different.

...

 You can then run the build cycle for each target:

$ bitbake mc:generic:rdk-generic-broadband-image && \
    bitbake mc:raspberrypi:rdk-generic-broadband-image

...

...

(Due to the way RDK-B components are built, it is not possible to do a "parallel" build for two targets at once, however, you will still save a significant amount of time and disk space by using multiconfig builds sequentially)

Build images for each target will be available in tmp/deploy:

...