Please enable javascript, or click here to visit my ecommerce web site powered by Shopify.
Jump to: navigation, search

Difference between revisions of "RockpiE/dev/kernel-4.4"

< RockpiE‎ | dev
(Troubleshooting)
(FAQs)
 
Line 74: Line 74:
 
==== FAQs ====
 
==== FAQs ====
  
===== 1.With an USB to TTL serial cable connected with UART2 pins (pin#10, pin#8, ping#6 on 40-PIN Header) on ROCK Pi E, system log is shown as follows. =====
+
===== 1.I have built one ROCK Pi E system image using rockchip-bsp SDK. With an USB to TTL serial cable connected with UART2 pins (pin#10, pin#8, ping#6 on 40-PIN Header) on ROCK Pi E, the last one line of system logs is shown as follows. =====
  
     [    0.001996] Console: colour dummy device 80x25
+
     [    0.932225] bootconsole [uart0] disabled
    [    0.002413] console [tty0] enabled
+
    [    0.002743] bootconsole [uart0] disabled
+
  
In fact the system starts up with no system log information shown on screen. If your ROCK Pi E system supports Ethernet/WiFi and SSH, you can access ROCK Pi E by SSH.
+
In fact the system starts up. If your ROCK Pi E system supports Ethernet/WiFi and SSH, you can access ROCK Pi E via SSH.
  
The FIQ Debugger is disabled by default. If you want to use debugger console, you can modify ROCK Pi E device tree, rk3328-rock-pi-e.dts to enable fiq_debugger node.
+
If you read the kernel command line of system log, you will find that the default console is ttyS2 (1500000n8). But due to uart2 is disabled by default in file rk3328-rock-pi-e.dts, there will be no more system logs on the screen.
  
    fiq_debugger: fiq-debugger {
+
To enable console ttyS2, you need to enable uart2 node. Add the following lines at the end of file rk3328-rock-pi-e.dts.
        compatible = "rockchip,fiq-debugger";
+
 
        rockchip,serial-id = <2>;
+
    &uart2 {
        rockchip,signal-irq = <159>;
+
        rockchip,wake-irq = <0>;
+
        /* If enable uart uses irq instead of fiq */
+
        rockchip,irq-mode-enable = <0>;
+
        rockchip,baudrate = <1500000>;  /* Only 115200 and 1500000 */
+
        interrupts = <GIC_SPI 127 IRQ_TYPE_LEVEL_LOW>;
+
 
         status = "okay";
 
         status = "okay";
 
     };
 
     };

Latest revision as of 03:38, 28 May 2020

    ROCK Pi E >  Development >  Build vendor kernel(Rockchip 4.4)

Build verdor kernel (Rockchip 4.4)

This guide describes how to build verdor kernel (Rockchip 4.4).
The vendor kernel is based on the Rockchip 4.4 kernel with hardware support for ROCK Pi E. Below is how to build it on a X86 Linux host PC.

Get the kernel source

Branch stable-4.4-rockpie supports ROCK Pi E board.

   git clone -b stable-4.4-rockpie https://github.com/radxa/kernel.git
   cd kernel

Install toolchain from Linaro

   wget https://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/aarch64-linux-gnu/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz
   sudo tar xvf gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu.tar.xz  -C /usr/local/
   export ARCH=arm64
   export CROSS_COMPILE=/usr/local/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-

Build kernel

   make rockchip_linux_defconfig

If you need to build kernel modules that are not in the default config, you can select it in menu config

   make menuconfig    #(optional)

Now build it

   make -j8

The built targets we are interested are arch/arm64/boot/Image and dtb file arch/arm64/boot/dts/rockchip/rk3328-rock-pi-e.dtb.

Build kernel deb package

The kernel package build can pack the kernel, device tree, modules and firmware into Debian packages, which makes it easier to install on the ROCK Pi E.

First, setup the version number, make sure the format is right.

   export build_id="999"             # make sure it's big enough so that our kernel is the newest.
   export lv="-$build_id-rockchip"
   export kv=$(make kernelversion)
   export debv="$kv$lv"
   make  bindeb-pkg -j8    LOCALVERSION=$lv    KDEB_PKGVERSION=$debv

The generated packages are(the kernel revision name maybe different):

   ls ../*.deb
   
   ../linux-firmware-image-4.4.194-999-rockchip-58823-g67ab7d4_4.4.194-999-rockchip_arm64.deb
   ../linux-headers-4.4.194-999-rockchip-58823-g67ab7d4_4.4.194-999-rockchip_arm64.deb
   ../linux-image-4.4.194-999-rockchip-58823-g67ab7d4_4.4.194-999-rockchip_arm64.deb
   ../linux-image-4.4.194-999-rockchip-58823-g67ab7d4-dbg_4.4.194-999-rockchip_arm64.deb
   ../linux-libc-dev_4.4.194-999-rockchip_arm64.deb

copy linux-image-4.4.194-999-rockchip-*_arm64.deb and linux-firmware-image-4.4.194-999-rockchip-*_arm64.deb to your ROCK Pi E.

Install it on ROCK Pi E.

   rockpie# dpkg -i linux-image-4.4.194-999-rockchip-*_arm64.deb linux-firmware-image-4.4.194-999-rockchip-*_arm64.deb

Reboot and you will have the new kernel booting.

FAQs

1.I have built one ROCK Pi E system image using rockchip-bsp SDK. With an USB to TTL serial cable connected with UART2 pins (pin#10, pin#8, ping#6 on 40-PIN Header) on ROCK Pi E, the last one line of system logs is shown as follows.
   [    0.932225] bootconsole [uart0] disabled

In fact the system starts up. If your ROCK Pi E system supports Ethernet/WiFi and SSH, you can access ROCK Pi E via SSH.

If you read the kernel command line of system log, you will find that the default console is ttyS2 (1500000n8). But due to uart2 is disabled by default in file rk3328-rock-pi-e.dts, there will be no more system logs on the screen.

To enable console ttyS2, you need to enable uart2 node. Add the following lines at the end of file rk3328-rock-pi-e.dts.

   &uart2 {
       status = "okay";
   };

Troubleshooting