Difference between revisions of "IoTGateway/BSP/Linux/APQ8016/BSP User Guide V1"
Daniel.hung (talk | contribs) |
Daniel.hung (talk | contribs) |
||
Line 33: | Line 33: | ||
You have two methods to put BSP into Docker container. | You have two methods to put BSP into Docker container. | ||
− | ==== <font color="#0070c0">1 | + | ==== <font color="#0070c0">[1] Download BSP from GitHub</font> ==== |
The [https://github.com/ADVANTECH-Corp/oe-rpb-manifest oe-rpb-manifest] @GitHub is our manifest repository for Qualcomm APQ8016 projects. You can use '''repo init''' & '''repo sync''' to get the entire BSP we put on GitHub. | The [https://github.com/ADVANTECH-Corp/oe-rpb-manifest oe-rpb-manifest] @GitHub is our manifest repository for Qualcomm APQ8016 projects. You can use '''repo init''' & '''repo sync''' to get the entire BSP we put on GitHub. | ||
Line 39: | Line 39: | ||
Checking the steps in [https://github.com/ADVANTECH-Corp/oe-rpb-manifest#bsp-source oe-rpb-manifest] to get a specific version of BSP or a latest one. | Checking the steps in [https://github.com/ADVANTECH-Corp/oe-rpb-manifest#bsp-source oe-rpb-manifest] to get a specific version of BSP or a latest one. | ||
− | ==== <font color="#0070c0">2 | + | ==== <font color="#0070c0">[2] Copy BSP tarball into Container</font> ==== |
You can use docker cp to do this. | You can use docker cp to do this. | ||
Line 89: | Line 89: | ||
=== <font color="#0070c0">Pre-built Images</font> === | === <font color="#0070c0">Pre-built Images</font> === | ||
− | + | ||
In '''LIV''' tarball file, you can get binary images. For example, | In '''LIV''' tarball file, you can get binary images. For example, | ||
− | '''boot-Image--4.4-r0-rsb-4760-20170426102349-52.img : '''Boot Image | + | '''boot-Image--4.4-r0-rsb-4760-20170426102349-52.img : '''Boot Image |
− | '''rpb-desktop-image-rsb-4760-20170426102349-52.rootfs.img : '''Root filesystem | + | '''rpb-desktop-image-rsb-4760-20170426102349-52.rootfs.img : '''Root filesystem |
| | ||
Line 102: | Line 102: | ||
'''advantech_bootloader_emmc_linux-72/''' | '''advantech_bootloader_emmc_linux-72/''' | ||
− | '''cdt_1.1_MT52L256M32D1PF.bin : '''DDR CDT parameters | + | '''cdt_1.1_MT52L256M32D1PF.bin : '''DDR CDT parameters |
− | ''' emmc_appsboot.mbn : '''Little Kernel (LK) responsible to load Linux kernel | + | ''' emmc_appsboot.mbn : '''Little Kernel (LK) responsible to load Linux kernel |
− | ''' flashall : '''Shell script to flash bootloader binaries | + | ''' flashall : '''Shell script to flash bootloader binaries |
− | ''' gpt_both0.bin : '''GPT partition table | + | ''' gpt_both0.bin : '''GPT partition table |
− | ''' hyp.mbn : '''Trust Zone / QHEE | + | ''' hyp.mbn : '''Trust Zone / QHEE |
− | ''' rpm.mbn : '''Resource and Power Management (RPM) | + | ''' rpm.mbn : '''Resource and Power Management (RPM) |
− | ''' sbl1.mbn :''' Secondary Boot Loader (SBL) | + | ''' sbl1.mbn :''' Secondary Boot Loader (SBL) |
− | '''tz.mbn : '''Trust Zone / QSEE | + | '''tz.mbn : '''Trust Zone / QSEE |
− | |||
== <font color="#0070c0">Build Instructions</font> == | == <font color="#0070c0">Build Instructions</font> == |
Revision as of 05:02, 23 June 2017
Contents
Getting Started
Conventions
${BSP_HOME}: home directory of the BSP
${BDIR} : build directory (e.g. build/)
${MACHINE} : available target boards list below
- rsb-4760 / epc-r4761
${DISTRO} : Linux distribution
- rpb / rpb-wayland
${RPB-IMAGES} : meta-rpb provides the following images
- rpb-console-image / rpb-desktop-image / rpb-minimal-image / rpb-qt5-image / rpb-weston-image
Build Environment on Host
Currently, we adopt Docker as build environment.
You can get the latest version of advrisc/u14.04-410clbv1 Docker image for developing Qualcomm APQ8016 projects.
If you don't know much about Docker, please refer to IoTGateway/Docker for details.
BSP
BSP Source
You have two methods to put BSP into Docker container.
[1] Download BSP from GitHub
The oe-rpb-manifest @GitHub is our manifest repository for Qualcomm APQ8016 projects. You can use repo init & repo sync to get the entire BSP we put on GitHub.
Checking the steps in oe-rpb-manifest to get a specific version of BSP or a latest one.
[2] Copy BSP tarball into Container
You can use docker cp to do this.
// Copy BSP source code into container $ docker cp 410cLBV1050_2017-05-19.tgz <your container id>:/home/adv
Or Use docker run with -v options to enable data volume. Then, you are able to put the BSP into the data volume folder.
For example, you can put the BSP into /home/root/workspace folder.
$ docker run -it --name docker_test -v /home/root/workspace:/home/adv/BSP advrisc/u14.04-410clbv1:20170605/bin/bash
BSP Content
The descriptions of some important folders in BSP are listed below:
bitbake/ : Yocto build command
bootloader/ : Bootloader binaries including of CDT, SBL, RPM, LK, etc.
layers/ : Sources for meta-layers
meta-96boards/ : meta layer of 96Boards definitions
meta-advantech/ ':' meta layer by Advantech
meta-qcom/ : meta layer for APQ8016 configurations
meta-rpb/ : meta layer for RPB distro
setup-environment : to set up build environment for Yocto
Naming Rule
The tarball/prebuilt image name consists of the model name followed by "LB" or "LI" plus version number and released date.
For example, BSP file name: 410cLBV1050_2017-05-19.tgz
Which "410c" means Dragonboard410c which a demo board for APQ8016 we use
"LB" is acronym of Linux BSP,
"V1050" stands for Version 1.050.
Another example, Yocto image name: 4760LIV1040_2017-04-20.tgz
which "4760" stands for RSB-4760
"LI" is acronym for prebuilt Linux Image.
Pre-built Images
In LIV tarball file, you can get binary images. For example,
boot-Image--4.4-r0-rsb-4760-20170426102349-52.img : Boot Image
rpb-desktop-image-rsb-4760-20170426102349-52.rootfs.img : Root filesystem
In BSP tarball file, you can see a zip file in bootloader/ folder. It is bootloader binary images.
advantech_bootloader_emmc_linux-72/
cdt_1.1_MT52L256M32D1PF.bin : DDR CDT parameters
emmc_appsboot.mbn : Little Kernel (LK) responsible to load Linux kernel
flashall : Shell script to flash bootloader binaries
gpt_both0.bin : GPT partition table
hyp.mbn : Trust Zone / QHEE
rpm.mbn : Resource and Power Management (RPM)
sbl1.mbn : Secondary Boot Loader (SBL)
tz.mbn : Trust Zone / QSEE
Build Instructions
Create New Build Environment
$ MACHINE=${MACHINE} DISTRO=${DISTRO} source setup-environment <Your build folder>
Load Existed Build Environment
$ source setup-environment <Your build folder>
Build Images
Ref: oe-rpb-manifest
Build Toolchain Installer
$ bitbake ${RPB-IMAGES} -c populate_sdk
Build Bootloader
Refer to Debian_16.09 " How to get and customize the bootloader "
$ git clone git://codeaurora.org/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8.git -b LA.BR.1.1.3.c4-01000-8x16.0 $ git clone http://git.linaro.org/landing-teams/working/qualcomm/lk.git -b debian-qcom-dragonboard410c-LA.BR.1.2.4-00310-8x16.0-linaro2 $ cd lk $ make -j4 msm8916 EMMC_BOOT=1 TOOLCHAIN_PREFIX=<path to arm-eabi-4.8 tree>/bin/arm-eabi-
Build Linux Kernel
Ref: oe-rpb-manifest
Flash Pre-built Images
USB Download Tools
1. Install DragonBoardUpdateTool 32 bit, 64 bit
2. Switch USB Download Mode (SW1: 1,1), power on and then connect with USB Cable
3. Open Command Prompt on PC
> cd C:\Program Files\Qualcomm\DragonBoardUpdateTool
4. Check COM port
> emmcdl.exe -l
5. Flash
> emmcdl.exe -p [Your COM Port] -f mbns\8916\prog_emmc_firehose_8916_ddr.mbn -x rawprogram0.xml
if it is success, it will show
Status: 0 The operation completed successfully.
6. Flash
> emmcdl.exe -p [Your COM Port ] -f mbns\8916\prog_emmc_firehose_8916_ddr.mbn -x rawprogram2.xml
7. Finally, switch to SW1:(0,1), boot from EMMC or SD Card
Fastboot Tool
1. Check device id
$ sudo fastboot devices
2. Flash device
$ sudo ./flashall [Devices ID]
3. Erase boot / rootfs partitions
$ sudo fastboot erase boot
$ sudo fastboot erase rootfs
4. Flash images to boot /rootfs partitions
$ sudo fastboot flash boot <Your boot image>
$ sudo fastboot flash rootfs <Your boot image>
Installation SD Card
1. Boot from installation SD Card, and Click "Install"
2. Flash all partitions
3. Installing
4. Finish and Reboot
Customization
Set Up SDK
Create Debian Images
In this section, we will show you how to generate a Debian image based on the same Yocto kernel.
Customize the kernel source code
In Yocto BSP, you can build kernel easily. To learn how to build kernel, you can refer to oe-rpb-manifest.
Then, we need three output files in your build artifacts.
- Kernel image (Image-MACHINE.bin)
- DTS image (dt-Image-MACHINE.img)
- Modules (modules-MACHINE.tgz)
Now you need to create a valid boot image with your own kernel build.
On your host PC, we need to install the following tools:
$ git clone git://codeaurora.org/quic/kernel/skales
To create the boot image, you also need a ramdisk image, and you can get one from the 96Boards release:
$ wget https://builds.96boards.org/snapshots/dragonboard410c/linaro/debian/227/initrd.img-4.9.21-linaro-lt-qcom
The tool mkbootimg is a standalone application that will process all files and create the boot image that can then be booted on the target board, or flash into the on-board eMMC. The boot image also contains the kernel bootargs, which can be changed as needed in the next command:
$ ./skales/mkbootimg --kernel Image-MACHINE.bin \ --ramdisk initrd.img-4.9.21-linaro-lt-qcom \ --output boot-MACHINE-debian.img \ --dt dt-Image-MACHINE.img \ --pagesize 2048 \ --base 0x80000000 \ --cmdline "root=/dev/disk/by-partlabel/rootfs rw rootwait console=ttyMSM0,115200n8"
After this step, you will get a boot image for Debian called boot-MACHINE-debian.img.
Revise Debian Rootfs
Basically, we can adopt Linaro's Debian rootfs directly with a little modifications for kernel modules. First, you can get the Debian rootfs from the 96Boards release:
$ wget https://builds.96boards.org/snapshots/dragonboard410c/linaro/debian/227/linaro-stretch-alip-qcom-snapdragon-arm64-20170427-227.img.gz
Second, unzip the file and transform it from sparse image to raw image.
$ gunzip linaro-stretch-alip-qcom-snapdragon-arm64-20170427-227.img.gz $ simg2img linaro-stretch-alip-qcom-snapdragon-arm64-20170427-227.img rootfs.raw
Then, you are able to mount the raw rootfs, and update with your kernel modules.
$ sudo mount -o loop rootfs.raw /mnt $ sudo rm -rf /mnt/lib/modules/ // Copy firmware & modules into /lib $ tar zxf modules-MACHINE.tgz $ sudo cp -a lib/* /mnt/lib $ sudo umount /mnt
Finally, make the rootfs into sparse image.
$ ext2simg -v rootfs.raw linaro-stretch-alip-qcom-snapdragon-arm64-20170427-227-MACHINE.img
Flash Debian Images
Now, you have both boot & rootfs images. You can easily flash them into eMMC via fastboot utility.
$ sudo fastboot erase boot $ sudo fastboot flash boot boot-MACHINE-debian.img $ sudo fastboot erase rootfs $ sudo fastboot flash rootfs linaro-stretch-alip-qcom-snapdragon-arm64-20170427-227-MACHINE.img
Note: After booting up, you have an important thing to do! You have to generate modules.dep and map files.
$ depmod -a
After reboot, the Debian system should work well!