Kernel compiling for Tinker Board S Debian 10 V3.0.23

[Frank 0]

Hey there,

 

i want to compile a kernel for the Tinker Board S version V3.0.23. But i can't find the kernel code for that version....

On GitHub the latest kernel code data is for Tinker Board Debian 10 V3.0.11

Could you please provide the kernel cod for your latest version?

 

Frank

[tooz 54]

hello @Frank, 

 

https://tinkerboard.github.io/docs/tinker_os-releases/tinker_board

the branch is: linux4.4-rk3288-tinker_board

manifest: tinker_board-debian-3.0.23.xml

if you'd like to use the latest: 

repo init -u https://github.com/TinkerBoard-Linux/rockchip-linux-manifest.git -b REVISION

 

[Frank 0]

@tooz thanks for the link. I will have a look into this.

Is it still possible to remove the TinkerBoard bootimage when recompiling the kernel with an empty black image?

 

Frank

[Frank 0]

Is it possible to use v3.0.27 für the TinkerBoard S too?

[tooz 54]

hello @Frank, 

12 minutes ago, Frank said:

Is it still possible to remove the TinkerBoard bootimage when recompiling the kernel with an empty black image?

 

yes, please refer to wiki: Developer Guide · TinkerBoard/TinkerBoard Wiki · GitHub >change the boot logo

 

6 minutes ago, Frank said:

Is it possible to use v3.0.27 für the TinkerBoard S too?

yes

[Frank 0]

I was able to setup the docker build environment container. But when i try to build the image i get the following error after some time...

I: Extracting liblzma5...
I: Extracting zlib1g...
P: Running debootstrap second stage under QEMU
chroot: failed to run command '/usr/bin/env': Exec format error
P: Begin unmounting filesystems...
P: Saving caches...
if [ -f binary-tar.tar.gz ]; then \
        tar -jcf linaro-buster-alip-`date +%Y%m%d`-1.config.tar.bz2 auto/ config/ configure; \
        sudo mv binary.contents linaro-buster-alip-`date +%Y%m%d`-1.contents; \
        sudo mv chroot.packages.live linaro-buster-alip-`date +%Y%m%d`-1.packages; \
        sudo mv binary-tar.tar.gz linaro-buster-alip-`date +%Y%m%d`-1.tar.gz; \
        md5sum linaro-buster-alip-`date +%Y%m%d`-1.build-log.txt linaro-buster-alip-`date +%Y%m%d`-1.config.tar.bz2 linaro-buster-alip-`date +%Y%m%d`-1.contents linaro-buster-alip-`date +%Y%m%d`-1.packages linaro-buster-alip-`date +%Y%m%d`-1.tar.gz > linaro-buster-alip-`date +%Y%m%d`-1.md5sums.txt; \
        sha1sum linaro-buster-alip-`date +%Y%m%d`-1.build-log.txt linaro-buster-alip-`date +%Y%m%d`-1.config.tar.bz2 linaro-buster-alip-`date +%Y%m%d`-1.contents linaro-buster-alip-`date +%Y%m%d`-1.packages linaro-buster-alip-`date +%Y%m%d`-1.tar.gz > linaro-buster-alip-`date +%Y%m%d`-1.sha1sums.txt; \
fi
 Failed to run livebuild, please check your network connection.
\033[36m Run mk-base-debian.sh first \033[0m
 Extract image
tar: linaro-buster-armhf.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
umount: binary/dev: no mount point specified.
ERROR: Running build_debian failed!
ERROR: exit code 32 from line 642:
    VERSION=${VERSION} VERSION_NUMBER=${VERSION_NUMBER} ARCH=$ARCH ./mk-rootfs-buster.sh

What i'm doing wrong? How to fix this?

 

Frank

[tooz 54]

hello @Frank, 

34 minutes ago, Frank said:

chroot: failed to run command '/usr/bin/env': Exec format error

did this happen when you run ./build.sh? you might want to install qemu-user-static and then copy it to the mounted point e.g. /mnt/usr/bin 

sudo apt install qemu-usr-static
sudo cp /usr/bin/qemu-arm-static /path/to/mount/usr/bin

and then restart the system

systemctl restart systemd-binfmt.service

 

[Frank 0]

Yes the error occured when i try to run ./build.sh

Should i install "qemu-user-static" inside the docker container or on the host system (Ubuntu 24.04)?

Inside the container it was installed already. What mountpoint do you mean? I haven't mounted anything....

I just synced the repository and installed docker on the host system. After that is startetd the docker run cmd "docker-builder-run.sh"

When the container was ready i tried to build with "./buils.sh"

[tooz 54]

hello @Frank, 

is your host machine an x86 host? if so, the steps above is to set up the right environment as tinkerboard is arm based

[Frank 0]

My host system is x86_64 (Ubuntu 24.04 on Windows 11 - wsl)

[Frank 0]

The file "qemu-arm-static" is present under /usr /bin on the host system and inside the docker container....

[tooz 54]

if you're using a x86 wsl there might be something relates to architecture similar to: https://askubuntu.com/questions/1006846/chroot-onto-arm-based-image it's necessary to have qemu supported in aarch64/ arm64. some reference: https://www.cnx-software.com/2016/05/10/how-to-run-ubuntu-16-04-aarch64-64-bit-arm-cloud-images-on-your-intelamd-linux-computer/ 

the easiest way to cross compile would be having a ubuntu host machine

[Frank 0]

Hi @tooz,

i switched to an Ubuntu 24.04 native machine. The problem from yesterday did not appear on this machine. But i get another error after some time when i try to build the image with ./build.sh

ake: Leaving directory '/source/buildroot'
====Start build rockchip_rk3288_recovery====
2025-04-03T10:24:23 >>> host-bison 3.0.4 Extracting
Done in 5s  (error code: 2)
Command exited with non-zero status 2
you take 0:05.22 to build recovery
ERROR: Running build_recovery failed!
ERROR: exit code 2 from line 719:
    /usr/bin/time -f "you take %E to build recovery" $COMMON_DIR/mk-ramdisk.sh recovery.img $RK_CFG_RECOVERY

Can you please help me to solve this issue? Tanks.

 

Frank

[Frank 0]

@tooz

Same result when i try to build the image using an Ubuntu 20.04 host machine (same as docker container)

 

Please help

[tooz 54]

hello @Frank, 

were you able to use buildroot? may i have the full log please?

[Frank 0]

@tooz

Finaly i got it running. Some packages are not available anymore on the defined sources. So we need to download them from other websites.

After reading a lot of logfiles and catching all packages it was working.

But i have still some questions. 

1. Do you have some kind of documentation for the commands of the asus-docker-env. We were not able to find something.

2. The other question is if there is a documentation about the changes from the v3.0.27 to the latest manifest?

 

Frank

[Frank 0]

BTW

Building the Image under Windows 11 using WSL with Distro Ubuntu 20.04 is working too

Ubuntu 20.04 seems to be the last supported OS version for the asus-docker-env

GitHub - asus-iot/asus-docker-env

[tooz 54]

hello @Frank 

22 hours ago, Frank said:

2. The other question is if there is a documentation about the changes from the v3.0.27 to the latest manifest?

 

1. Disable auto login for the uart console and the dekstop environment.
2. Force the user linaro to change its password at the linaro's next login
3. Eable ROCKCHIP_EFUSE config for u-boot to set cpuid from efuse to fix the issue that all CPU has the same ID

[Frank 0]

@tooz

You don't get me. I want to know what are the changes between the v3.0.27 build (current releas from Asus) and the version i can build with manifest "latest". Is it the same?

The changes from v3.0.23 to v3.0.27 are clear to me....  

[tooz 54]

hello @Frank, 

sorry for the confusion, that's correct. the latest version is v.3.0.27

[tooz 54]

hello @Frank, 

On 4/10/2025 at 8:14 PM, Frank said:

1. Do you have some kind of documentation for the commands of the asus-docker-env. We were not able to find something.

 

To set up the environment: 

1. Install docker and asus-docker-env
2. Follow GitHub - asus-iot/asus-docker-env to run asus_docker_env_run
3. Install necessary packages below :

sudo apt-get install libgmp-dev
sudo apt-get install libmpc-dev
sudo apt-get install bsdmainutils
sudo apt-get remove live-build
git clone https://salsa.debian.org/live-team/live-build.git --depth 1 -b debian/1%20230131
cd live-build
rm -rf manpages/po/
sudo make install -j8

4. Use build.sh to build code base