tooz

hello @saeed soleimanifar, by boot logs, do you mean the console logs printed whist booting?

hello @Buchhalter, 1. was the usb camera working with the previous os releases? 2. what’s the usb camera you’re using? 3. what’s the output when you execute v4l2-ctl --list-devices

hello @Lucas32, this guide from toradex explains what device tree overlays are and how they work: https://developer.toradex.com/linux-bsp/os-development/build-yocto/device-tree-overlays-linux/ reboot is needed after you sudo vim /boot/config.txt what is the os version? the dtbo of dac hats in the qualified vendor list are already built out/ included in the os. you might want to an os that's later than v.2.1.6 Tinker Board 2 Debian 10 V2.1.6 Description Tinker Board 2 Debian 10 V2.1.6 Tinker OS default username is "linaro", password is "linaro". Release Notes: * Changelog 1. First Kernel 4.19.x release version 2. Merged kernel security patch 3. Audio: Support JustBoom DAC HAT/Digi HAT/Amp HAT 4. Audio: Support IQaudIO Pi-DAC+/Pi-DAC Pro/Pi-Digi+ 5. Audio: Support HiFiBerry DAC+ Light/Digi+ 6. USB: Enable USB printer in kernel config 7. Config: Default enable GPIO PIN37 as S/PDIF, for Type-C DP audio function.

hello @btwin, yes, tinker-config is also supported for tinker board r2.0, you can download v.3.0.11 here: Tinker Board S R2.0 Debian 10 V3.0.11 to disable auto-login using tinker-config: sudo tinker-config in ther terminal prompt: 1. select "3. Boot Options" 2. select "B1 Desktop" 3. select "B3 Desktop" 4. finish the prompt will ask you to reboot the board so the new setting comes in effect. i would suggest to power off the board and re-power it again, just in case.

hello @Suntech, the easiest way would be using the dd command to clone everything out of the board then use flashtools such as balena etcher to flash the .img to other boards. 1. connect tinker board 2s to an ubuntu machine 2. to check if tinker board 2s has been recognised, use lsblk 3. to clone the eMMC: sudo dd if=/dev/sdb of=(filename).img bs=1G this will take a while, i've waited for around 35 minutes or so 4. once the cloning is finished, copy the .img file and use flashtools such as balenaetcher to flash the os to other boards *if you don't have an ubuntu machine, you can plug a flash drive to tinker board 2s, and save the output file to the flashdrive (please ensure it's got enough space) change #3 to: sudo dd if=/dev/sdb of=of=/dev/<USB device_name> bs=1G **if you're using a windows pc, you can use win32 disk imager: Win32 Disk Imager - Download [Official Site] 1. connect tinker board 2s to the pc 2. whilst tinker board 2s is in ums mode, use win32 disk imager to copy the emmc Using dd to clone eMMC OS.pdf

hello @giseleznev, 1. which adc are you using? do you have a product link so i can check the spec? 2. may i have a look at how the sound card is connected to tinker board 2s?

hello @Lucas32, the sensor setting for imx219 is 1920x1080 by default, you can change it to 3840x2160 with commands: media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":0[fmt:SRGGB10_1X10/3840x2160]' media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":0[crop:(0,0)/3840x2160]' media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":2[fmt:YUYV8_2X8/3840x2160]' media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":2[crop:(0,0)/3840x2160]' media-ctl -d /dev/media0 --set-v4l2 '"m00_b_imx219 1-0010":0[fmt:SRGGB10_1X10/3840x2160]' v4l2-ctl -d /dev/video0 --set-fmt-video=width=3840,height=2160,pixelformat=NV12 --set-crop=top=0,left=0,width=3840,height=2160

hello @giseleznev, this is the qualified vendor list of tinker board 2s: https://tinker-board.asus.com/images/doc/download/Tinker_Board 2_QVL_Devices 20210324.pdf

hello @giseleznev, we use this one for dac hat capability testing: https://teac.jp/int/product/ha-p50/top

hello @btwin, please refer to the instruction: Developer Guide · TinkerBoard/TinkerBoard Wiki (github.com)

hello @hisataro, what are the error messages/ logs? i'll check if there's anything been changed

hello @giseleznev, should be there once you repo sync if you're not using docker, run ./build.sh if you're using docker then ./docker_builder/docker-builder-run.sh build.sh

hello @hisataro, updated to the developer guide, thank you for the reminder Developer Guide · TinkerBoard/TinkerBoard Wiki (github.com)

hello @giseleznev, what is the os version you're using and can we have the screenshot of the aplay -l result for checking? the 'hdmi-dp-sound' is an old structure that does not exist anymore, i don't have a pisound but if its chip is pcm5102a then 'overlay=hifiberry-dac' may work. please use v.2.1.6 (debian 10, kernel 4.19) or later versioin Tinker Board 2 Debian 10 V2.1.6

hello @Mahesh-BRICOM, you can use alsa to check the list of playback hardware devices with command a play -l playing music using commandline: aplay /directory/to/file reference: https://wiki.debian.org/ALSA

hello @giseleznev, these are included in the sources: TinkerBoard2/debian (github.com) please be sure to download them too

hello @giseleznev, the cause might be the build enviornment, the filesystem you're compiling kernel on has to be case-sensitive (such as ubuntu), if you're using mac os for compiling it's likely to fail. what is your build enviornment? reference: https://lkml.org/lkml/2020/5/6/1301

hello @giseleznev, please download the complete source code: execute the following command in the terminal to download source code from github: $ repo init -u https://github.com/TinkerBoard2/manifest.git -b linux4.19-rk3399-debian10 $ repo sync

hello @giseleznev, https://github.com/TinkerBoard2/docker_builder

hello @giseleznev, you need to set up the build enviornment first: Install Docker environment Uninstall old versions $ sudo apt-get remove docker docker-engine docker.io containerd runc Install Docker Engine – Community $ sudo apt-get update $ sudo apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common $ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - $ sudo apt-key fingerprint 0EBFCD88 $ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" $ sudo apt-get update $ sudo apt-get install docker-ce docker-ce-cli containerd.io $ sudo docker run hello-world Reference: https://docs.docker.com/engine/install/ubuntu/ Manage Docker as a non-root user $ sudo groupadd docker $ sudo usermod -aG docker $USER $ newgrp docker $ docker run hello-world Reference: https://docs.docker.com/engine/install/linux-postinstall/ Code compiling Go to the directory where you have downloaded the code base and execute the script. This will take a while to install the necessary packages on the host and build the Docker image. $ ./docker_builder/docker-builder-run.sh Once the above is done, you are in the shell of the newly started Docker container as the following. You can start to issue commands as usual. Successfully built 702bff5a9b3f Successfully tagged asus/tinker_2-linux-builder:latest Options to run docker: --privileged --rm -it --volume /DIRECTORY_PATH_TO_SOURCE:/source your_usernmae@292c696527f6:/source$ You can issue the following command to build all the images for Debian. All the images will be saved in the directory rockdev. $ ./build.sh It will generate a file which named sdboot.img and located at [source tree]/rockdev/sdboot.img Compiling u-boot/Kernel/Debian separately u-boot $ ./build.sh uboot It will generate a file which named uboot.img and located at [source tree]/u-boot/uboot.img Kernel $ ./build.sh kernel It will generate a file which named boot.img and located at [source tree]/kernel/boot.img Debian $ ./build.sh debian It will generate a file which named linaro-rootfs.img and located at [source tree]/debian/linaro-rootfs.img

hello @sathish, i'm not aware of this, does this happen 100/100 or once in a while? which os version are you using? are you running any application etc?

hello @giseleznev, kernel build process instruction for tinker board 2s can be found here: Developer Guide · TinkerBoard/TinkerBoard Wiki (github.com)

hello @giseleznev, these can be found here, directory is /kernel/sound/soc/rockchip: kernel/sound/soc/rockchip at linux4.19-rk3399-debian10 · TinkerBoard2/kernel · GitHub

hello @Vincent123, good to hear that the installation error's been solved and thanks for letting me know

hello @mrorange, these packages are marked held by rockchip -- some packages have been modified and have to be kept in certain versions for compatibility reasons. it's not suggested to do dist-upgrade from debian repository as some functions might not work as they should be after the upgrade. however, if you must upgrade these packages, you can do it through aptitude apt-get install aptitude sudo aptitude once the caches and configs are loaded, you will see a little console, look for '---Upgradable Packages' and press g to preview; press g again to upgrade all the packages. (you will have to press return to continue during the process) once the upgrade is finished, press q to leave aptitude (as mentioned in other posts, the ldconfigs can be ignored)