tooz

hello @michiksdjfklsdjfl, 1. please open the terminal, execute the command below and send us the screenshot: lsusb 2. please provide us steps to duplicate the issue and the audio file used; we have not observed the issue on our side and would like to reproduce the issue 3. does the hissing sound linger when occurs or does it only happen when you play the audio? if it's possible, could you send us the audio record with the hissing sound so we can narrow down the rootcause

hello @michiksdjfklsdjfl, 1. what's the hardware version of the boards? (it's printed on the back of the product e.g. 'Tinker Board S R2.0 REV 0.1') 2. what's the audio firmware version you've updated to? 3. what's the os version you're using? (debian/ android/ ?)

hello @lloydhussell, for more about can-utils: https://github.com/linux-can/can-utils it's supported on android debug build, it's not available on user build

hello @wahaha, bootargs can specify the location of the ramdisk (initrd); however, for initramfs, you need to load the initramfs into memory and pass its address to the kernel. If the initramfs is built into the kernel image, then there is no need for separate loading or bootargs configuration

hello @ryo, since you have sd image ready, you can flash tinker board 3's emmc in ums mode. please keep the sd card in the board and 1. switch all the dip switches to off 2. connect tinker board 3 and laptop with micro usb cable 3. power on, open device manager and see if the board is recognised as 'ASUS Tinker UMS USB Device' 4. use balena etcher to flash it

hello @wahaha, unfortunately there's no specific config to define ramdisk partition. verifying and loading kernel and ramfs both by default start from fit image. to load ramfs only you will need to use a command such as ex2load or fatload manually.

hello @ryo, have you adjusted the dip switches to 1 and 2 so the board is in emmc mode? (on the other hand if you set them to 'on', it would be in sd card mode)

hello @shizimi, no, it will not be able to power since it needs 12v - 19v power via dc jack. please refer to the block diagram ch.1.6.1 on page 12: E22692_Tinker_Board_3_UM_WEB.pdf (asus.com)

hello @shizimi, the user manual/ quick start guide of tinker board 3 & tinker board 3s is released: https://tinker-board.asus.com/download/E22692_Tinker_Board_3_UM_WEB.pdf

hello @wahaha, please add the overlay to /boot/config.txt, save and reboot and see if the overlay comes effective sudo vi /boot/config.txt overlay=console-uart0-overlay

hello @shizimi, we're planning to update the documentation next week, i'll put the link on here once it's ready. sorry for the inconvenience

hello @Dominik, 1. did the panel: go completely blank or show 'no signal'? 2. what's the powering sequence? is it panel ->tinker board 3n, or the other way round? was the hdmi cable connected between the panel and tinker board 3n the whole time? 3. could you collect logs via adb so we can have a little big more information for debugging, to collect logs using adb commands: ./adb root ./adb shell dmesg > dmesg.log ./adb shell "echo 0x0c > /sys/module/drm/parameters/debug" ./adb shell dmesg -C ##please unplug and re-plug the hdmi cable## ./adb shell dmesg > dmesg_drm.log

hello @shizimi, for tinker board 3 & 3s: Tinker Board 3 & 3S · TinkerBoard/TinkerBoard Wiki · GitHub there's also a github page for tinker series (in the works) Hello from ASUS Tinker Board Series Documentation | ASUS Tinker Board Series Documentation

hello @wahaha, the commands are correct, for the actual ddr bin and miniloader bin used for the project, please refer to rkboot/rk3399miniall.ini https://github.com/TinkerBoard/rockchip-linux-rkbin/blob/linux4.19-rk3399-debian10/RKBOOT/RK3399MINIALL.ini

hello @wahaha, in short: yes. idbloader is different from uboot, and you will need to dd dbloader in order to boot into uboot idbloader will need to be located in seek 0x64 in emmc whether the individual partition exists or not

hello @wahaha, from what you've decribed it's likely that the board isn't booting to either first loader or uboot. please be sure that the idbloader is located in 0x64 instead of 0x40 dd if=$IMAGES/idbloader.bin of=$DEVICE seek=64 conv=nocreat

hello @Cha.JH, android 12 is supported on tinker board 2s and the image can be downloaded here: Tinker Board 2 /2S Android 12 V3.0.2

hello @Augusto Hertz, yes, we're planning to have the first release of android image for tinker board 3 soon

hello @Kebin.h, if you must use csi cameras, we'd suggest you to stick to the existing products that are csi-enabled, or stay tuned for the future product updates

hello @Nige, i guess the hotkey you're looking for is ctrl+alt+L (xflock); xflock calls light-locker to lock the screen

hello @hisataro, sure, and in case you want to try on debian -- modify /boot/config.txt and reboot sudo vi /boot/config.txt intf:i2c7=on overlay=i2c7_egalax

hello @hisataro, you can enable egalax touch driver through overlay in tinker config app 1. open tinker config app > interface > set 'i2c7' to on 2. open tinker config app > overlay > check 'i2c7_egalax' and then reboot to make the changes come effective

hello @Didjya7, please contact the distributor (where the board was purchased) or customer service through: https://www.asus.com/support/service-center-location/

hello @esperal, my bad, i thought you're talking about tinker board and tinker board 2s, please try cat /proc/boardid this command instead:

hello @Shin, 1. for kernel 5.10, please replace files in gpio_lib_c_rk3399 with https://www.asuswebstorage.com/navigate/a/#/s/3059D9ACD7AF4D849E68AB69661499C84 2. and then rebuild and install wiringpi libraries: cd /usr/local/share/gpio_lib_c_rk3399 sudo ./build clean sudo ./build uninstall sudo ./build