2017-03-20T03:06:47Z

Karen:

Rockchip is working on upstream SoC support to Mainline kernel:

 

= Download Kernel =

Get the source code from the upstream mainline repository:
<pre>git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git</pre>

Alternatively you can use linux-rockchip instead which may with some patches not get in mainline:
<pre>git clone git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git</pre>

= Supported SoCs and Devices[[http://10.10.10.12:8444/index.php?title=Rockchip_Kernel&action=edit&section=2 edit]] =

Mainline kernel supports:

RV1108, RK3036, RK3066, RK3188, RK3228, RK3288, RK3368, RK3399

*RV1108 boards:
<ol style="margin-left: 40px;">
<li>EVB RV1108- use rk1108-evb.dts</li>
</ol>

*RK3036 boards:
<ol style="margin-left: 40px;">
<li>EVB RK3036 - use rk3036-evb.dts</li>
<li>Kylin RK3036- use rk3036-kylin.dts</li>
</ol>

*RK3066 boards:
<ol style="margin-left: 40px;">
<li>Marsboard - use rk3066a-marsboard.dts</li>
<li>Bqcurie2 - use rk3066a-bqcurie2.dts</li>
<li>Rayeager - use rk3066a-rayeager.dts</li>
</ol>

*RK3188 boards:
<ol style="margin-left: 40px;">
<li>Radxa Rock - rk3188-radxarock.dts</li>
</ol>

*RK3288 boards:
<ol style="margin-left: 40px;">
<li>EVB RK3288 - use rk3288-evb-rk808.dts or rk3288-evb-act8846.dts</li>
<li>Fennec RK3288 - use rk3288-fennec.dts</li>
<li>Firefly RK3288 - use rk3288-firefly.dts</li>
<li>Firefly beta RK3288 - use rk3288-firefly-beta.dts</li>
<li>Firefly reload RK3288 - use rk3288-firefly-reload.dts</li>
<li>Hisense Chromebook - use rk3288-veyron-jerry.dts</li>
<li>PopMetal RK3288 - use rk3288-popmetal.dts</li>
<li>MiQi RK3288 - use rk3288-miqi.dts</li>
<li>Radxa Rock 2 - use rk3288-rock2-square.dts</li>
</ol>

*RK3368 boards:
<ol style="margin-left: 40px;">
<li>Geekbok RK3368 - use rk3368-geekbox.dts</li>
<li>Orion r68 - use rk3368-orion-r68-meta.dts</li>
</ol>

*RK3399 boards:
<ol style="margin-left: 40px;">
<li>EVB RK3399 - use rk3399-evb.dts</li>
</ol>

 

= Configure and Build[[http://10.10.10.12:8444/index.php?title=Rockchip_Kernel&action=edit&section=3 edit]] =

You will need to use multi_v7_defconfig for armv7 SoCs:
<pre>make multi_v7_defconfig</pre>

configure for aarch64:
<pre>make ARCH=arm64 defconfig</pre>

The arm64 defconfig on upstream is more for server, we recommend you to use rockchip_linux_defconfig from Rockchip github
<pre>make ARCH=arm64 rockchip_linux_defconfig</pre>

After configure, build the kernel.

For armv7:
<pre>make CROSS_COMPILE=arm-linux-gnueabi-</pre>

For aarch64:
<pre>make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64</pre>

Then you can get Image/zImage and dtb files.

 

= Install Boot/kernel[[http://10.10.10.12:8444/index.php?title=Rockchip_Kernel&action=edit&section=4 edit]] =

We use distro boot in U-Boot, so we need to make a boot partition for U-Boot with kernel image and dtb inside.
<pre>mkdir boot
cp arch/arm64/boot/dts/rockchip/rockchip/rk3399-evb.dtb boot/rk3399.dtb
cp arch/arm64/boot/Image boot/</pre>

Add extlinux/extlinux.conf for distro boot.
<pre>mkdir boot/extlinux
vi boot/extlinux/extlinux.conf</pre>

 
<pre>lable kernel-mainline
kernel /Image
fdt /rk3399.dtb
append earlycon=uart8250,mmio,0xff1a0000 console=ttyS2,1500000n8 root=dev/mmcblk0p7 rootwait rootfstype=ext4 init=/sbin/init</pre>

You need to change the base address of debug UART, root partition for your board.

Pls reference to [http://10.10.10.12:8444/index.php?title=Partitions rockchip Linux parttion definition] for rootfs partition and where boot to flash.

After all these file prepare complete, we write the file to the boot partition

See [[Rockchip_Kernel|rockchip kernel]] for boot partition generate.

Boot option

2017-03-20T02:43:17Z

Karen:

= overview =
<pre>+--------+----------------+----------+-----------+
| Boot | Terminology #1 | Actual | Rockchip |
| stage | | program | Loader |
| number | | name | Name |
+--------+----------------+----------+-----------+
| 1 | Primary | ROM code | BootRom |
| | Program | | |
| | Loader | | |
| | | | |
| 2 | Secondary | u-boot | MiniLoader|
| | Program | SPL | |
| | Loader (SPL) | | |
| | | | |
| 3 | - | U-Boot | U-Boot |
| | | | |
| | | | |
| 4 | - | kernel | kernel |
| | | | |
| 5 | - | rootfs | rootfs |
+--------+----------------+----------+-----------+
</pre>

 

== Boot from eMMC ==

===  To get tool and firmware ===

[[Rkdevelptool|tools]]

=== Flash to the board by USB ===

In order to flash by USB,you must get your board into ROM boot mode, either by erasing your MMC or holding the maskrom button when you boot the board.

 

==== RK3288(upgrade_tool) ====

To create a suitable image and flash it to the board: default : with CONFIG_ROCKCHIP_SPL_BACK_TO_BROM
<pre>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin out cat u-boot-dtb.bin >> out sudo upgrade_tool db  ../rkbin/rk32/RK3288UbootLoader_V2.30.06.bin sudo upgrade_tool wl 64 out sudo upgrade_tool rd</pre>

 others : firefly（Recommend using sd card）

 

 

==== RK3036 ====

To create a suitable image and flash it to the board:
<pre>tools/mkimage -n rk3036 -T rksd -d spl/u-boot-spl-dtb.bin out
cat u-boot-dtb.bin >> out
sudo upgrade_tool db ../rkbin/rk30/RK3036MiniLoaderAll_V2.19.bin
sudo upgrade_tool wl 64 out
sudo upgrade_tool rd
</pre>

 

==== RK3399 ====
<pre>cd ..
./rkbin/tools/trust_merger ./rkbin/tools/RK3399TRUST.ini
cd uboot

../rkbin/tools/loaderimage --pack --uboot u-boot-dtb.bin uboot.img

sudo upgrade_tool UL ../rkbin/rk33/RK3399MiniLoaderAll_V1.05.bin
sudo upgrade_tool DI uboot uboot.img ../rkbin/tools/rk3399_parameter.txt
sudo upgrade_tool DI trust ../trust.img ../rkbin/tools/rk3399_parameter.txt
sudo upgrade_tool rd
</pre>

 

 

===  To flash kernel and rootfs ===

Enter into the uboot and issue the following command on uboot: (otg should be connected)
<pre>gpt write mmc 0 $partitions
ums 0 mmc 0
</pre>

 Now the board will act as an USB-drive. In host: (assuming sdb is ur device)
<pre>sudo mkfs.fat /dev/sdb6
</pre>

 Copy zimage and dts file to dev/sdb6
<pre>cp arch/arm/boot/zImage /media/chen/9F35-9565/
cp arch/arm/boot/dts/rk3288-fennec.dtb /media/chen/9F35-9565/rk3288-fennec.dtb
</pre>

Add extlinux/extlinux.conf to dev/sdb6 (Please notice "mmcblk2p7" and "115200n8" is decide on your chip, Please refer to  [[Linux_user_guide]])
<pre>label kernel-4.4
kernel /zImage
fdt /rk3288-fennec.dtb
append earlyprintk console=tty1 console=ttyS2,115200n8 rw root=/dev/mmcblk2p7 rootfstype=ext4 init=/sbin/init
</pre>

 To flash rootfs
<pre>sudo dd if=linaro-rootfs.img of=/dev/sdb7 conv=notrunc</pre>

== Boot from SD/TF Card ==

=== Creating Image ===

Follow [[Linux_user_guide|Linux user guide ]]to build kernel and U-Boot. get uboot-spl.img and u-boot-dtb.img
<pre>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin uboot-spl.img
</pre>

 

=== <var>build boot.img</var> ===
<pre>sudo dd if=/dev/zero of=boot.img bs=1M count=128
sudo mkfs.fat boot.img
mkdir boot
sudo mount boot.img boot
sudo cp zImage boot
sudo cp rk3288-fennec.dtb boot
sudo mkdir boot/extlinux
sudo cp extlinux.conf boot/extlinux
sudo umount boot
</pre>

Download rootfs image and rename it
<pre>mv linaro-rootfs.img rootfs.img
</pre>

 

=== Making a SD Card for updating ===

Download [https://github.com/wzyy2/rk-initrd-build ramdisk source] and build.
<pre>sh ./mk-initrd.sh
</pre>

Format SD card
<pre>chen@chen-HP-ProDesk-680-G1-TWR:~/work/linaro-alip/ramdisk/update$ sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y

Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-126613470, default = 2048) or {+-}size{KMGTP}: 8192
Last sector (8192-126613470, default = 126613470) or {+-}size{KMGTP}:
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdc.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
</pre>
<pre>sudo umount /dev/sdb1
sudo mkfs.fat /dev/sdb1
</pre>
<pre>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin out&&
sudo dd if=out of=/dev/sdb seek=64&&sudo dd if=u-boot-dtb.img of=/dev/sdb seek=256
</pre>

Copy zimage, dts and ramdisk to /dev/sdb1
<pre>cp arch/arm/boot/zImage /media/chen/9F35-9565/
cp arch/arm/boot/dts/rk3288-fennec.dtb /media/chen/9F35-9565/rk3288-fennec.dtb
cp ../rk-initrd-build/initrd.img /media/chen/9F35-9565/
</pre>

Add extlinux/extlinux.conf to /dev/sdb1
<pre>label kernel-4.4
kernel /zImage
fdt /rk3288-fennec.dtb
initrd /initrd.img
append earlyprintk console=ttyS2,115200n8 rw root=/dev/ram0 rootfstype=ext4 init=/sbin/init ramdisk_size=49152
</pre>

Copy u-boot-dtb.img uboot-spl.img boot.img rootfs.img and [https://github.com/wzyy2/rk-initrd-build/blob/master/update/update.sh update.sh] to /dev/sdb1
<pre>mkdir /media/chen/9F35-9565/update
cp u-boot-dtb.img /media/chen/9F35-9565/update
cp uboot-spl.img /media/chen/9F35-9565/update
cp boot.img /media/chen/9F35-9565/update
cp rootfs.img /media/chen/9F35-9565/update
cp update.sh /media/chen/9F35-9565/update
</pre>

=== Updating the board ===

Boot the board and it will flash image to eMMC

 

== Boot from USB-Disk ==

Same as [[#Boot_from_SD.2FTF_Card|boot-from-sdcard]], but please note that U-Boot aren't allowed to boot from usb-disk because of restrict of maskrom, only kernel and rootfs can load from USB-Disk.

Difference:
<pre>label kernel-4.4
kernel /zImage
fdt /rk3288-fennec.dtb
append earlyprintk console=ttyS2,115200n8 rw root=/dev/sda1 rootfstype=ext4 init=/sbin/init
</pre>
<pre>gpt write usb 0 $partitions
ums 0 usb 0
</pre>

= Boot from Network =

2017-03-17T08:06:49Z

Karen:

= overview =
<pre>+--------+----------------+----------+-----------+
| Boot | Terminology #1 | Actual | Rockchip |
| stage | | program | Loader |
| number | | name | Name |
+--------+----------------+----------+-----------+
| 1 | Primary | ROM code | BootRom |
| | Program | | |
| | Loader | | |
| | | | |
| 2 | Secondary | u-boot | MiniLoader|
| | Program | SPL | |
| | Loader (SPL) | | |
| | | | |
| 3 | - | U-Boot | U-Boot |
| | | | |
| | | | |
| 4 | - | kernel | kernel |
| | | | |
| 5 | - | rootfs | rootfs |
+--------+----------------+----------+-----------+
</pre>

== Boot from eMMC ==

===  To get tool and firmware ===

[http://rockchip.wikidot.com/tools tools]

=== Flash to the board by USB ===

In order to flash by USB,you must get your board into ROM boot mode, either by erasing your MMC or holding the maskrom button when you boot the board.

 

==== RK3288(upgrade_tool) ====

To create a suitable image and flash it to the board: default : with CONFIG_ROCKCHIP_SPL_BACK_TO_BROM
<pre>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin out cat u-boot-dtb.bin >> out sudo upgrade_tool db  ../rkbin/rk32/RK3288UbootLoader_V2.30.06.bin sudo upgrade_tool wl 64 out sudo upgrade_tool rd</pre>

 others : firefly（Recommend using sd card）

 

==== RK3036 ====

To create a suitable image and flash it to the board:
<pre><code>tools/mkimage -n rk3036 -T rksd -d spl/u-boot-spl-dtb.bin out
cat u-boot-dtb.bin >> out
sudo upgrade_tool db ../rkbin/rk30/RK3036MiniLoaderAll_V2.19.bin
sudo upgrade_tool wl 64 out
sudo upgrade_tool rd</code>
</pre>

==== RK3399 ====
<pre><code>cd ..
./rkbin/tools/trust_merger ./rkbin/tools/RK3399TRUST.ini
cd uboot

../rkbin/tools/loaderimage --pack --uboot u-boot-dtb.bin uboot.img

sudo upgrade_tool UL ../rkbin/rk33/RK3399MiniLoaderAll_V1.05.bin
sudo upgrade_tool DI uboot uboot.img ../rkbin/tools/rk3399_parameter.txt
sudo upgrade_tool DI trust ../trust.img ../rkbin/tools/rk3399_parameter.txt
sudo upgrade_tool rd</code>
</pre>

 

===  To flash kernel and rootfs ===

Enter into the uboot and issue the following command on uboot: (otg should be connected)
<pre><code>gpt write mmc 0 $partitions
ums 0 mmc 0</code>
</pre>

 Now the board will act as an USB-drive. In host: (assuming sdb is ur device)
<pre><code>sudo mkfs.fat /dev/sdb6</code>
</pre>

 Copy zimage and dts file to dev/sdb6
<pre><code>cp arch/arm/boot/zImage /media/chen/9F35-9565/
cp arch/arm/boot/dts/rk3288-fennec.dtb /media/chen/9F35-9565/rk3288-fennec.dtb</code>
</pre>

Add extlinux/extlinux.conf to dev/sdb6 (Please notice "mmcblk2p7" and "115200n8" is decide on your chip, Please refer to [http://rockchip.wikidot.com/linux-user-guide#toc1 config table])
<pre><code>label kernel-4.4
kernel /zImage
fdt /rk3288-fennec.dtb
append earlyprintk console=tty1 console=ttyS2,115200n8 rw root=/dev/mmcblk2p7 rootfstype=ext4 init=/sbin/init</code>
</pre>

 To flash rootfs
<pre><code>sudo dd if=linaro-rootfs.img of=/dev/sdb7 conv=notrunc</code></pre>

== Boot from SD/TF Card ==

=== Creating Image ===

Follow [http://rockchip.wikidot.com/linux-user-guide linux-user-guide] to build kernel and U-Boot. get uboot-spl.img and u-boot-dtb.img
<pre><code>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin uboot-spl.img</code>
</pre>

=== <var>build boot.img</var> ===
<pre><code>sudo dd if=/dev/zero of=boot.img bs=1M count=128
sudo mkfs.fat boot.img
mkdir boot
sudo mount boot.img boot
sudo cp zImage boot
sudo cp rk3288-fennec.dtb boot
sudo mkdir boot/extlinux
sudo cp extlinux.conf boot/extlinux
sudo umount boot</code>
</pre>

Download rootfs image and rename it
<pre><code>mv linaro-rootfs.img rootfs.img</code>
</pre>

=== Making a SD Card for updating ===

Download [https://github.com/wzyy2/rk-initrd-build ramdisk source] and build.
<pre><code>sh ./mk-initrd.sh</code>
</pre>

Format SD card
<pre><code>chen@chen-HP-ProDesk-680-G1-TWR:~/work/linaro-alip/ramdisk/update$ sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y

Command (? for help): n
Partition number (1-128, default 1): 1
First sector (34-126613470, default = 2048) or {+-}size{KMGTP}: 8192
Last sector (8192-126613470, default = 126613470) or {+-}size{KMGTP}:
Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300):
Changed type of partition to 'Linux filesystem'

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdc.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.</code>
</pre>
<pre><code>sudo umount /dev/sdb1
sudo mkfs.fat /dev/sdb1</code>
</pre>
<pre><code>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl-dtb.bin out&&
sudo dd if=out of=/dev/sdb seek=64&&sudo dd if=u-boot-dtb.img of=/dev/sdb seek=256</code>
</pre>

Copy zimage, dts and ramdisk to /dev/sdb1
<pre><code>cp arch/arm/boot/zImage /media/chen/9F35-9565/
cp arch/arm/boot/dts/rk3288-fennec.dtb /media/chen/9F35-9565/rk3288-fennec.dtb
cp ../rk-initrd-build/initrd.img /media/chen/9F35-9565/</code>
</pre>

Add extlinux/extlinux.conf to /dev/sdb1
<pre><code>label kernel-4.4
kernel /zImage
fdt /rk3288-fennec.dtb
initrd /initrd.img
append earlyprintk console=ttyS2,115200n8 rw root=/dev/ram0 rootfstype=ext4 init=/sbin/init ramdisk_size=49152</code>
</pre>

Copy u-boot-dtb.img uboot-spl.img boot.img rootfs.img and [https://github.com/wzyy2/rk-initrd-build/blob/master/update/update.sh update.sh] to /dev/sdb1
<pre><code>mkdir /media/chen/9F35-9565/update
cp u-boot-dtb.img /media/chen/9F35-9565/update
cp uboot-spl.img /media/chen/9F35-9565/update
cp boot.img /media/chen/9F35-9565/update
cp rootfs.img /media/chen/9F35-9565/update
cp update.sh /media/chen/9F35-9565/update</code>
</pre>

=== Updating the board ===

Boot the board and it will flash image to eMMC

 

== Boot from USB-Disk ==

Same as [http://rockchip.wikidot.com/boot-from-sdcard boot-from-sdcard], but please note that U-Boot aren't allowed to boot from usb-disk because of restrict of maskrom, only kernel and rootfs can load from USB-Disk.

Difference:
<pre><code>label kernel-4.4
kernel /zImage
fdt /rk3288-fennec.dtb
append earlyprintk console=ttyS2,115200n8 rw root=/dev/sda1 rootfstype=ext4 init=/sbin/init</code>
</pre>
<pre><code>gpt write usb 0 $partitions
ums 0 usb 0</code>
</pre>

= Boot from Network =

Display Server

2017-03-17T00:57:18Z

Karen:

= Introduction =

= Download =

Git repository：[https://github.com/rockchip-linux/xserver https://github.com/rockchip-linux/xserver]

= Supported Devices =

= Configuration/Environment =

== How to debug xserver ==

You should install a debugging package for xserver-core : xserver-xorg-core-dbg_1.18.4-1_armhf.deb.

Also, the Mesa/GL libraries might be involved, installing libgl1-mesa-dri-dbg and libgl1-mesa-glx-dbg might help too.
<pre><code>apt-get install gdb libc6-dbg
gdb -p $(pidof X)
(inside gdb)
set logging overwrite on
set logging on
break xorg_backtrace
continue
(X server is stopped from when gdb is attached until "continue" is typed)
(do whatever caused the problem)
bt full
set logging off
quit</code>
</pre>

After this, you get the gdb output in file gdb.txt in the directory where you started gdb (this is what the logging commands did, another solution is to copy-paste the output yourself). Add all this to your bug report, developers will appreciate it. If the backtrace is small, you probably miss several debugging packages, see above.

More info please see [https://www.x.org/wiki/Development/Documentation/ServerDebugging/ here].

==== Untrap signals ====

The X server will by default intercept signals and for instance trap its own crashes and dump a stack trace in /var/log/Xorg.0.log. However, this stack trace is modified by the signal handler itself. To disable this signal interception, add this to your /etc/X11/xorg.conf:
<pre><code>Section "ServerFlags"
Option "NoTrapSignals" "true"
EndSection</code>
</pre>

and restart your X server.

= Package =

= Install =

== To build xserver ==

We suggest that using the Debian build system to build our xserver or you would be too hard to solve dependence problem. You may reference to Debian Package Maintainer Manuel for more information. (Update: now we support build xserver with docker, see [https://github.com/rockchip-linux/docker-rockchip here] )

#Install all the build dependency for the xserver.
#Install the library mali and development files. You must use the version comes from Rockchip.
#Entry the xserver directory.
#Build with the Debian build tools.

= See also =

= References  =