All Activity
This stream auto-updates
- Last week
-
Marc joined the community
- Earlier
-
treefsdaf joined the community
-
kimallen joined the community
-
I have mistaken when downloading old source code. After trying with latest source code, Audio works normally now. Please ignore. Thank you !
-
Hi everyone ! I have tried to build Debian for Tinker Board 3s by following the guide at https://github.com/TinkerBoard/TinkerBoard/wiki/Tinker-Board-3-&-3S After building and flashing image, Debian can boots up and most of features function properly. But I can not play audio via 3.5 mm port: Some debug information: root@linaro-alip:/# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 root@linaro-alip:/# dmesg | grep sound [ 4.011331] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.013325] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.015123] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.621126] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.623107] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.625071] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.637447] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.639581] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.641652] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.649570] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.653490] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.656981] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.738595] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.740769] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.744236] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.751415] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.754619] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.758382] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.833968] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.836622] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.839072] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 5.043269] rk-multicodecs rk809-sound: Failed to get ADC channel [ 5.045282] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 5.048308] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 5.668399] rk-multicodecs rk809-sound: Failed to get ADC channel [ 5.670634] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 5.672530] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 7.484887] rk-multicodecs rk809-sound: Failed to get ADC channel [ 7.516061] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 7.516070] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 7.555597] rk-multicodecs rk809-sound: Failed to get ADC channel [ 7.555795] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 7.555798] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 7.639002] rk-multicodecs rk809-sound: Failed to get ADC channel [ 7.761508] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 7.763343] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 9.902650] rk-multicodecs rk809-sound: Failed to get ADC channel [ 9.904733] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 9.906440] rk-multicodecs rk809-sound: Audio routing invalid/unspecified When try to flash official image from https://tinker-board.asus.com/download-list.html?product=tinker-board-3, I can play audio via 3.5 port normally. Did any one face the same issue ? Please help me !!!
-
felix_vu joined the community
-
denchakapon changed their profile photo
-
Acadmiac joined the community
-
Tom1 joined the community
-
Lucas Smith joined the community
-
That’s an impressive milestone for the Armbian team — they’ve managed to balance performance improvements with community-driven innovation, which isn’t easy in open-source projects of this scale.
-
cursorman joined the community
-
KarstenT66 joined the community
-
Hi, I follow the wiki to flash Android OS to Tinkerboard 3S devices and then install my app that need manage storage permission, but every time I reboot the device, the manage storage permission is revoked. Then I check the install app permission of "Files" app, the same thing happens. Image flashed: Tinker Board 3/3S Android 14 (kernel 6.1) V.1.0.9 Reproduce steps: Setting -> Apps -> Files -> Permission -> allow install other app permission. Reboot the device. Check permission again, you can see the install permission is revoked. BTW, I also tried flash latest image Tinker Board 3/3S Android 14 (kernel 6.1) V.1.0.19, but it also happens.
-
quenchjian joined the community
-
hello @LucD, sorry to hear that. could you provide a screencap of the failure so we can further investigate the issue?
-
Replying to this old thread because I had the same problem this week on the Tinker Board (not S) R2.0: I tried both of the Android 11 images with the same issue as @AJofre - after running adb reboot-bootloader the logo screen appears but the device gets stuck on that screen and the device is not visible when I run fastboot devices Tinker Board R2.0 /Tinker Board S R2.0 Android 11 V1.0.6 Tinker Board S R2.0 Android 11 V1.0.0 However, I was able to work around the problem as follows: Reboot the device to boot normally (I had to power off the Tinker Board, remove the SD card, power it on again, power off, reinsert SD card, power on again) adb shell su dd if=/storage/emulated/0/Download/magisk_patched-XXX.img of=/dev/block/by-name/boot adb reboot After the reboot, I'm able to grant root permissions to apps that request them.
-
@TzuWen_Chang Hello. Thank you so much for your kind advice. I will try. Best regards,
-
WIFI Module Affects USB Connection with Tinker 3S
TzuWen_Chang replied to sonyan11's topic in Hardware
Hi, Here are a few ways to reduce radio frequency interference (RFI): 1. Disable USB 3.0. In your case, you can directly use a USB 2.0 port to connect the camera. 2. Improve signal shielding. Try adding metal shielding (grounded) between the Wi-Fi network card and the motherboard. 3. Switch to a USB Wi-Fi card and use a USB extension cable to move the USB Wi-Fi card away from the USB 3.0 port. -
Cliff changed their profile photo
-
Dear, I try to activate i2s on my thinkerboard 3S. Situation: Tinker Board 3/3S Debian 11 (kernel 5.10) V.1.0.7 Updated: /boot/config.txt intf:i2s3_2ch=on Direct connected i2s MEMS microphone, custom build on PCB, worked on tinkerboard S R2.0. Pins, power and ground Mic BCLK to pin 12 Mic DOUT to pin 38 Mic LRCL to pin 35 Updated the asound.conf to (based on chatGPT): pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 } alsa installed aplay -l doesn't list capture devices What am I missing?
-
How to Normal Boot with USB-TypeC connected to PC
danfoxley replied to grv2025's topic in General Discussion
I don't seem to have this file on Armbian 25 Noble with a Tinker Board S R 2.0. Please help with any suggestions. /boot/config.txt . Any suggestions? -
HI, Thanks for the tip, but both options, remove/change were not succesfull. Is there another option (manually update?) Greetings, L.
-
Hello, please modify the /etc/apt/sources.list file. Remove the following lines: deb http://mirrors.ustc.edu.cn/debian/ bullseye-backports main contrib deb-src http://mirrors.ustc.edu.cn/debian/ bullseye-backports main contrib Or, change them to: deb https://archive.debian.org/debian/ bullseye-backports main contrib non-free deb-src https://archive.debian.org/debian/ bullseye-backports main contrib non-free This will allow apt update to work correctly.
-
Dear @tooz, I deeply appreciate for your support. We have confirmed that the impact is reduced when using 5GHz. When using 2.4GHz, is it possible to mitigate the impact through driver tweaks or similar measures? Or would hardware modifications (antenna positions) be necessary? Best regards，
-
Hello, Back in business. I downloaded the Tinker Board 3/3S Debian 11 (kernel 5.10) V.1.0.7 release from the download area (this section for empty before). Succesfully installed, but I encouter the following problem: sudo apt-get update and sudo apt update both fail 'cannot initiate connection on...' any the the automatic options (debian.org, ustc.edu.cn,...) while a simple sudo ping google.com works. So the internet connection is OK, but I am stuck because I can't perform the apt update... Solution? Greetings, Luc
-
Hello, I use Tinker 3S with latest Tinker OS. I connected a high-power USB 3 camera module (800 mA). At the same time, my Tinker board is periodically accessed over Wi-Fi by a web client (it runs a web server). When I cut the power to the Wi-Fi router, the USB camera capture suddenly starts failing in bursts. This is reproducible. If I disable Wi-Fi power saving mode (see attached code), the problem disappears. echo "options 8822ce rtw_power_mgnt=0 rtw_ips_mode=0 rtw_lps_level=0 rtw_low_power=0" \ | sudo tee /etc/modprobe.d/8822ce.conf However, I would like to avoid disabling power saving mode if possible. What do you think is happening here?
-
hello @tooz thank you for your response and sorry for my response delay. As I wanted to prepare the steps for you to reproduce the problem I did some tests and I figured out that it is actually dhcpcd5 apllication that's making the problem and not hostapd. I dont know if you can rename the topic to use dhcpcd5 app name instead of hostapd. Regarding the problem with dhcpcd5 app, I'm not providing the logs because you can reproduce the problem very easily in few steps and it works always. You just need to flash Tinker Board 2S with fresh TinkerOS image version 3.0.25 and do next two commands: sudo apt update and then sudo apt install dhcpcd5. When everything is installed, you can reboot the tinker board and then next time wifi interface has the name wlan0. If you disable dhcpcd5 service starting at the start using command sudo systemctl disable dhcpcd5, wifi interface gets correct name of wlp1s0 from the next OS start. So the problem is that if dhcpcd5 service is installed and it is set to start at the OS startup, wifi interface gets wlan0 as a name and you cannot use wifi. If dhcpcd5 service is not set to start at the OS startup, wifi interface gets name wlp1s0 and everything is fine. Also One note though of what I noticed to happen. When Tinker Board is started for the first time after OS is flashed, if you just login to the OS and do one reboot, then the wifi interface gets the name of wlan0. And with every next OS start everything works as normal (wifi gets name wlp1s0), so only at 2nd OS start wifi gets wrong name. Also, this first time OS is started after fresh install, updating apt list doesnt work immediatelly. I had to repeat the command few times and maybe use apt update command without sudo to trigger something what will allow sudo apt update the next time. -
hello @jovanpn, could we have the logs and/ or steps to repro the issue?
-
Hi, we are using Tinker Board 2S for quite some time already and also been using it with hostapd software to use it as hotpost AP at some point. But we noticed with last 2 or 3 OS versions that we have a problem with this setup. The problem seems to appear, in more than 95% of cases, when hostapd application is enabled to run after the OS is started up. When this is set, then wireless interface name is not being renamed wo wlp1s0 but it remains as wlan0 and in this case hostapd cannot run properly. What could be the cause of this problem and how I could fix it? Thanks in advance!
-
@TzuWen_Chang Thank you so much for your response. It works! Thank you!
-
hello @sonyan11 For TB3 use the following commands Reset usb 2.0 hub: echo 1 > /sys/kernel/debug/usb/fd800000.usb/hub_reset Power off and power on usb 2.0 hub device: echo off > /sys/kernel/debug/usb/fd800000.usb/hub_vbus echo on > /sys/kernel/debug/usb/fd800000.usb/hub_vbus Power off and power on usb 3.0 hub device: echo off > /sys/kernel/debug/usb/fd000000.dwc3/hub_vbus echo on > /sys/kernel/debug/usb/fd000000.dwc3/hub_vbus
- 9 replies
-
- 1
-
-
- usb 3.0 vbus power
- usb3.0
- (and 1 more)
-
Hello. Since Tinkerboard3 has been released, I've migrated my development environment to Tinker3. Can I still control USB power delivery with Tinker3? Best regards,
-
Hi everyone, I'm trying to use docker on the Tinker System 3N, but it's not work properly. If possible, could you please provide any solutions you might have? [What I'd like to do] To use latest verion of docker on the Tinker System 3N [Systems Information] System: Tinker System 3N Tinker OS: Tinker System 3N/Tinker Board 3N Debian 11 (Kernel 5.10) V1.0.31 docker-ce: v28.4.0 iptables: v1.8.7 [Problems Encountered] Problem 1: When the docker daemon is started, the following error is recorded, and docker daemon does not work properly. failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to add jump rules to ipv4 NAT table: failed to append jump rules to nat-PREROUTING: (iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables v1.8.7 (nf_tables): Couldn't load match 'addrtype':No such file or directory Try 'iptables -h' or 'iptables --help' for more information (exit status 2)) Assumed Cause: The mach 'addrtype' is not loaded on kernel/iptables(nftables). Problem 2: When I tried to run docker container, the following error is recorded, and docker container does not work properly. docker: Error response from daemon: failed to set up container networking: failed to create endpoint nifty_wilbur on network bridge: unableto enable DIRECT ACCESS FILTERING - DROP rule: (iptables failed: iptables --wait -t raw -A PREROUTING -d 172.17.0.2 ! -i docker0 -j DROP: iptables v1.8.7 (legacy): can't initialize iptables table 'raw': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. (exit status 3)) Assumed Cause: CONFIG_IP_NF_RAW seems to be required for docker v28.0.0 or later, but CONFIG_IP_NF_RAW is not provided by the kernel. Ref: https://docs.docker.com/engine/release-notes/28/ [Possible Solutions] Solution A: 1. Use iptables-legacy: $ sudo update-alternatives --set iptables /usr/sbin/iptables-legacy $ sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy 2. Disable CONFIG_IP_NF_RAW: $ sudo systemctl edit docker.service And add following configration: [Service] Environment="DOCKER_INSECURE_NO_IPTABLES_RAW=1" Result: docker will work. --------------------------------- Solution B: 1. Use iptables-legacy: $ sudo update-alternatives --set iptables /usr/sbin/iptables-legacy $ sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy 2. Downgrade docker to v27.5.1: $ sudo apt-get install docker-ce=5:27.5.1-1~debian.11~bullseye docker-ce-cli=5:27.5.1-1~debian.11~bullseye Result: docker will work. --------------------------------- Solution C: 1. Disalbe the use of iptables in docker: $ sudo vim /etc/docker/daemon.json And add following configration: { "iptables": false } Result: docker will work. [Conclusion] Each possible solution resolves the issue; however, there are still security concerns. Does anyone have any other solutions?
-
Dear Tinker Board Team, I am interested in your product ASUS Tinker Board 2S and would like to clarify information about its production plans. In particular, I am interested in how long this model will be in active production and available for purchase?
-
hello @a_s_hari, the ideal way would be creating a .xml for resulation configurations and push the .xml to make the configuration available in settings > display > hdmi what's the resolution of the display you're using? please follow the steps and provide logs: 1. dmesg -c $echo 0x0c > /sys/module/drm/parameters/debug 2. disconnect and then reconnect the hdmi cable 3. dmesg
