tooz

hello @Ethan_Lin, to change the i2c speed in android 11 is similar to debian: adb root adb remount adb pull /dtoverlay/config.txt (#uncomment intf:i2c6=on, and add overlay=i2c6_100k) adb push i2c6_100K.dtbo config.txt /dtoverlay/overlays the dtbo file can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/258BFBD7E61045C9BECB7DA044378A844

hello @SecureBooter, enabling/ modifying security boot will invole hardware modifications. these changes are unalterable once they're made and the product (herein tinker board 2s) will no longer be warranted. please drop the inquiry via https://tinker-board.asus.com/contact.html and my colleague will get back to you as soon as possible

hello @Vaa, it's strange because it should work on v.3.0.11. does the same problem persist when you use v.3.0.6?

hello @Jovan, we've made some changes for uboot, please download it and have a try: https://www.asuswebstorage.com/navigate/a/#/s/78E2E316F9754A788E254369757136FD4 to update uboot: 1. download and unzip the file (uboot.img) 2. use the following commands to replace uboot sudo dd if=uboot.img of=/dev/mmcblk1p1 status=progress && sync sudo reboot

hello @Vaa, we tested and confirmed that v4l2loopback can be installed. install header: sudo dpkg -i linux-headers-5.10.160_5.10.160-1_arm64.deb sudo apt update sudo apt-get -y install v4l2loopback-dkms logs of v4l2loopback installation: root@linaro-alip:/# sudo apt-get -y install v4l2loopback-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: liba52-0.7.4 libdca0 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: dctrl-tools dkms Suggested packages: debtags menu v4l2loopback-utils Recommended packages: fakeroot linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers The following NEW packages will be installed: dctrl-tools dkms v4l2loopback-dkms 0 upgraded, 3 newly installed, 0 to remove and 26 not upgraded. Need to get 215 kB of archives. After this operation, 835 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian bullseye/main arm64 dctrl-tools arm64 2.24-3 [101 kB] Get:2 http://deb.debian.org/debian bullseye/main arm64 dkms all 2.8.4-3 [78.2 kB] Get:3 http://deb.debian.org/debian bullseye/main arm64 v4l2loopback-dkms all 0.12.5-1 [36.2 kB] Fetched 215 kB in 0s (579 kB/s) Selecting previously unselected package dctrl-tools. (Reading database ... 87411 files and directories currently installed.) Preparing to unpack .../dctrl-tools_2.24-3_arm64.deb ... Unpacking dctrl-tools (2.24-3) ... Selecting previously unselected package dkms. Preparing to unpack .../archives/dkms_2.8.4-3_all.deb ... Unpacking dkms (2.8.4-3) ... Selecting previously unselected package v4l2loopback-dkms. Preparing to unpack .../v4l2loopback-dkms_0.12.5-1_all.deb ... Unpacking v4l2loopback-dkms (0.12.5-1) ... Setting up dctrl-tools (2.24-3) ... Setting up dkms (2.8.4-3) ... Setting up v4l2loopback-dkms (0.12.5-1) ... Loading new v4l2loopback-0.12.5 DKMS files... It is likely that 5.10.160 belongs to a chroot's host Building for 5.10.160, hci_uart.ko and rtk_btusb.ko Building initial module for 5.10.160 Done. v4l2loopback.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.10.160/updates/dkms/ depmod..... DKMS: install completed. Module build for kernel hci_uart.ko was skipped since the kernel headers for this kernel does not seem to be installed. Module build for kernel rtk_btusb.ko was skipped since the kernel headers for this kernel does not seem to be installed. Processing triggers for man-db (2.9.4-2) ... root@linaro-alip:/# however we didn't see this warning -- have you modified the sourcelist?

hello @Vaa, it's indeed unexpected. what are the installation/ error logs? in the meantime i deleted and put the file back again just in case https://www.asuswebstorage.com/navigate/a/#/s/55EBC3A2F121400C90174358AC520AF94

hello @Vaa, you're right, re-up the linux header for kernel 5.10.160 in the web folder: https://www.asuswebstorage.com/navigate/a/#/s/55EBC3A2F121400C90174358AC520AF94

hello @sonyan11, what's the image version you're using? if it's not on the list then the function might not have been added -- my bad. i have updated my previous post with versions that support usb vbus control. for debian 10 kernel 4.4, please use v.2.0.20 or later

hello @Vaa, the linux header (kernel 5.10) can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/4A6FF93C2E304C2598FB3D74DE583F824

hello @Jovan, wifi uses pcie interface instead of uart console, and cfg80211 is one of the build-in kernel modules so it's expected to see logs like [ 10.023354] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 10.026024] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 10.026366] cfg80211: failed to load regulatory.db what's the setup? is there anything modified apart from adding intf:fiq_debugger=off to the /config.txt?

hello @Jovan, modifying /boot/config.txt only allows the function to be enabled these are uart driver init loggings baud rates can be changed in user space

hello @ttquattroman, when the tinker edge t is connected to the windows pc: in device manager, is tinker edge t recognised as 'asus android bootloader interface'?

hello @DutchDev, aicc can be removed using command: sudo apt purge aiccagent no

hello @captain kirk, also please use sudo tinker-config

hello @captain kirk, imx219 is supported on tinker board r2.0, i don't think you need to add an overlay, but if you must, try modify the last line: overlay=CSI0-IMX219 save and then reboot to test and see if the camera works: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink reference: Tinker Board (asus.com)

hello @Ethan_Lin, 1. from what you've described i'd suggest to check the devices (the dac, adc) 2. please collect the logs when the issue occurs, you can use adb with the command: adb shell su -c dmesg > dmesg.log

hello @Ethan_Lin, what's the os/ version and i2c bus you're using? did you connect it to other peripherals?

hello @sinoj, you will still have to build from sources uploaded by asus: Android for ASUS Tinker Board Series · GitHub but the tinker os (android) is integrated from aosp and you can change the configurations if you need

hello @gavin67890, for csi cameras, the coral camera is the only camera module supported on tinker edge t thus far: https://tinker-board.asus.com/download/Tinker_Edge_T_Device_QVL.pdf though there's no qvl for the uvc cameras, we use logictec c930e for testing

hello @wahaha, sorry for the delay -- the sources of debian 11 for tinker board 2s have been uploaded repo init -u https://github.com/TinkerBoard-Linux/rockchip-linux-manifest.git -b linux5.10-rk3399-debian11 repo sync

hello @wahaha, looks like the driver isn't initialised, please try: sudo modprobe 8822ce uname -a

hello @wahaha, not sure if it's a hardware or driver issue, to get a little further: 1. what is the image version you're using? is it debian 11 v.3.0.6? 2. what are the results when you execute the commands: ifconfig -a sudo lspci sudo lsmod

hello @aki, the @800000000Hz here means the gpu frequency is set to 800mhz, 0 means the gpu usage = 0 is the gpu governor set to performance? and please use these commands to check gpu when you're running applications that might be using gpu to accelerate -- for exmaple, you can use the commands while running glmark2-es2 and the gpu usage should not be 0. if the apis you are using support gpu accelerating then it (gpu usage = 0) should not be the case

hello @aki, the embedded gpu uses GLES instead of GL please use the commands below to check the gpu loading/ usage instead of glxinfo: cat /sys/devices/platform/ff9a0000.gpu/utilisation cat /sys/devices/platform/ff9a0000.gpu/devfreq/ff9a0000.gpu/load

hello @wahaha, we'll upload the codes by the end of this week, i'll leave a comment with the url once it's done. sorry for the inconvenience.