DART-SD410 Yocto Pyro 4.9.34 Download Packages

From Variscite Wiki
Revision as of 18:49, 15 November 2018 by Leonid (talk | contribs) (→‎Aplly HDMI Patch if HDMI support needed)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Download packages and build.

Download recepies

Create directory tree

Create the following directory tree:

$ mkdir -p ~/sd410-yocto/pyro
$ cd  ~/sd410-yocto/pyro

Download Linaro Release

$ repo init -u https://github.com/96boards/oe-rpb-manifest.git -b pyro
$ repo sync -j10

Download Variscite Patch Set

$ git clone https://github.com/varigit/DART-SD410-repo-patch.git
$ cd DART-SD410-repo-patch
$ git checkout -b yocto/pyro remotes/origin/yocto/pyro

Apply Variscite Patch

$ cd ../layers/meta-qcom
$ git checkout aa09d55d9a34e22e41759392a4f9cd93f6cf8e1c
$ git am ../../DART-SD410-repo-patch/meta-qcom/0001-dart-sd410-Variscite-DART-SD410-platform-support-add.patch

Aplly HDMI Patch if HDMI support needed

$ git apply ../../DART-SD410-repo-patch/meta-qcom/HDMI_Enable_patch.diff
$ cd ../..

Build

Select Target Machine

$ source setup-environment
You will be prompted to choose the target machine, pick dart-sd410
You will be prompted to choose the distro, choose:
           'rpb' for minimal, console-only image and for simple X11 image
           'rpb-wayland' for Wayland/Weston image
           'rpb-eglfs' for QT over EGLFS

The script setup-environment will create sane default configuration files in /conf, you can inspect them and modify them if needed.
Note that conf/local.conf and conf/bblayers.conf are symlinks.

NOTE:
When running the setup-environment script, you were asked to read/accept the Qualcomm EULA.
The EULA is required to access the proprietary firmware, such as the GPU firmware , WLAN, ...

If you accepted the EULA, when building an image for DART-SD410 all proprietary firmware are installed automatically in /lib/firmware,
and a copy of the EULA is added as '/etc/license.txt`.

If you did not accept the EULA, the firmware are not downloaded, and not installed into the image.

Build a minimal, console-only image

$ bitbake rpb-console-image

At the end of the build, your build artifacts will be found under tmp-rpb-glibc/deploy/images/dart-sd410/.
The two artifacts you will use to update your board are: rpb-console-image-dart-sd410.ext4.gz and boot-dart-sd410.img

Build a simple X11 image

$ bitbake rpb-desktop-image

At the end of the build, your build artifacts will be found under tmp-rpb-glibc/deploy/images/dart-sd410/.
The two artifacts you will use to update your board are: rpb-desktop-image-dart-sd410.ext4.gz and boot-dart-sd410.img

Build a Wayland/Weston image

$ bitbake rpb-weston-image

At the end of the build, your build artifacts will be found under tmp-eglibc/deploy/images/dart-sd410/.
The two artifacts you will use to update your board are: rpb-weston-image-sd410.ext4.gz and boot-dart-sd410.img

Flashing Images

Download Rescue Images from FTP site

Download the whole Pyro-Linaro-4.9.34 folder located in /dart-sd410/Software/ on Variscite FTP into ~/sd410/yocto directory The following files will be downloaded.

sd410
└── yocto
    └── Pyro-Linaro-4.9.34
        └── RescueImages
            ├── boot-dart-sd410-HDMI.img
            ├── boot-dart-sd410.img
            ├── dart-sd410_8016.bin
            ├── emmc_appsboot.mbn
            ├── flashall.bat
            ├── gpt_both0.bin
            ├── hyp.mbn
            ├── LICENSE
            ├── NON-HLOS.bin
            ├── rpb-console-image-dart-sd410-20170731160549.rootfs.ext4
            ├── rpb-desktop-image-dart-sd410-20170801081703.rootfs.ext4
            ├── rpm.mbn
            ├── sbl1.mbn
            └── tz.mbn
NOTE:
Please refer to support@variscite.com for obtaining FTP credentials.

Flash Images

Use fastboot to update the target eMMC.

$ ./flashall
NOTE:
To enter fastboot mode on the target the power should be cycled with the Back button pressed.

First time run

On first SOM boot the root file system partition is large enough to hold the contents of root file system.
In order to enlarge it to occupy the unallocated space the resize-helper.sh script should be run.
resize_helper.sh script can be downloaded from here.