All Activity
This stream auto-updates
- Last week
-
Ogost joined the community
-
Is there any update on this? I am still considering getting the board. I am not sure if it matters much when the board will be embedded inside a machine that will be sold. So it's probably fine for me to just use the userdebug Android build. But why is this not offered in any other builds out of the box? Or has this changed. Because CAN bus, afaiu, is becoming more and more popular in industrial systems.
-
Can I apply power to the Tinker Board 3 through the two VCC5V_SYS pins on the GPIO Header rather than through the USB power connector.
-
rock joined the community
- Earlier
-
Axel joined the community
-
Dexz joined the community
-
Raman joined the community
-
Amine joined the community
-
hello @Frank, To set up the environment: Install docker and asus-docker-env Follow GitHub - asus-iot/asus-docker-env to run asus_docker_env_run 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 Use build.sh to build code base
-
hello @Frank, sorry for the confusion, that's correct. the latest version is v.3.0.27
-
@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....
-
hello @Frank Disable auto login for the uart console and the dekstop environment. Force the user linaro to change its password at the linaro's next login Eable ROCKCHIP_EFUSE config for u-boot to set cpuid from efuse to fix the issue that all CPU has the same ID
-
Akihiro Nakamura joined the community
-
Jon Bernard joined the community
-
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 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
-
hello @Frank, were you able to use buildroot? may i have the full log please?
-
@tooz Same result when i try to build the image using an Ubuntu 20.04 host machine (same as docker container) Please help
-
Hello? I'm developing Android 11 OS debugging with Tinkerboard 2s. The environment I was developing is using Tinkerboard 2S R1.02, and it's Android 11 - 4.19.172 kernel version. But this time, I received Tinkerboard 2S R1.03. This product does not recognize USB-C type on Android 11 OS under development. When I installed the OS, I recognized USB-C without any problems, so I was able to confirm that there was a problem with Android OS. So when I installed the latest version of Android 11 - 4.19.219, I found out that USB-C is recognized normally. In my opinion, the OS update would have added drivers related to USB. You must proceed with the project with Android 11 - 4.19.172 kernel version. If there is a way, please let me know the solution in some way. -
Benun joined the community
-
I test it on the device, I can see how the servo is moving.
-
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
-
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
-
Oso Tama joined the community
-
The file "qemu-arm-static" is present under /usr /bin on the host system and inside the docker container....
-
My host system is x86_64 (Ubuntu 24.04 on Windows 11 - wsl)
-
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
-
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"
-
hello @Frank, 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
-
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
-
I want to stop the display of logs etc. at startup.
tooz replied to syse-miya's topic in General Discussion
hello @syse-miya, you'll need to disable it through dtoverlay, similar to: which os are you using? debian 11? -
Hi everyone, I'm trying to see if it's possible to stop the display of logs etc. at startup. I added console= to /boot/cmdline.txt and the logs stopped appearing, but I can't get rid of the image that appears in the upper left. Please tell me how to get rid of this image.
-
hello @Frank, yes, please refer to wiki: Developer Guide · TinkerBoard/TinkerBoard Wiki · GitHub >change the boot logo yes
-
Is it possible to use v3.0.27 für the TinkerBoard S too?
-
@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
