tooz

another thing to check is whether the jumper's attached or not -- if it's attached the board stays in maskrom mode

hello @asteele, it's likely that you're using an inadequate power supply that's not providng enough power to the board. the partitions seem correct though

somebody reported the issue to ffmpeg: [FFmpeg-user] Can FFmpeg Record Video On Linux Using V4L2 in V4L2_CAP_VIDEO_CAPTURE_MPLANE Mode? Looks that the mplane format is currently not supported when capturing from a v4l2 device at the moment. If you have time, please create a ticket on https://trac.ffmpeg.org/report

hello @Kajan001, which command did you execute for using the cameras?

hello @Subbu, →it varies. not all HAT DACs i2s DAC, tinker-40pin-i2s is one of the methods for using DAC → it depends on the circuit design of the DAC you're using. we'd also suggest you to use perhaps 2 or 3 pieces of extansion headers(the heatsink is tall) in case you connect to the wrong pins →different DACs all have different hardware design and chips, their dts files should be configured and enabled. using one of the DACs from the QVL (Tinker Board (asus.com)) would be a good way to avoid most of the compatibility issues.

hello @WorapolBuraphan, TinkerBoard2/kernel (github.com) are the source codes of tinker os, which is debian based. the kernel compile process is pretty common and standard. have you faced any difficulties in terms of compiling?

hello @CommandLine726, sorry for the very late reply. unfortunaly if you're using a dsi panel there's no way to rotate the screen; however if you're using a hdmi monitor, you cand rotate the screen by editing the /etc/X11/xorg.conf.d/20-modesetting.conf 1. sudo su 2. cat /etc/X11/xorg.conf.d/20-modesetting.conf (if the configuration exisits, you will see the last section: Section "Monitor" Identifier "Default Monitor" Option "Rotate" "normal") 3. vim /etc/X11/xorg.conf.d/20-modesetting.conf change the Option "Rotate" "normal" to "inverted" "normal" 4. reboot now

hello @Justus, here are the windows drivers that i installed before flashing, please give it a try: https://www.asuswebstorage.com/navigate/a/#/s/9A9AE0E3C26F478CBD0DCE44A26226E54

hello @CubanAzcuy, 1. does it crash only when you connect it to the macbook? 2. were the other usb ports plugged to other peripherals when the issue occurred? 3. what is the power supply you're using?

hello @Fuchsy, x11vnc is giving me some on-and-off disconnections that can be fixed by reconnecting (not perfect, but does the job) i have used teamviewer and anydesk very briefly. what is your setup? tinker board r2.0 as vnc server, it connect to a hdmi monitor and a waveshare lcd panel, and a laptop as vnc client?

#docker engine installation on tinker board r2.0 #OS: Debian 10 v.3.0.11 (kernel 4.4) #docker engine version: server 23.0.1 (updated/ easier way to install) sudo apt-get update sudo apt-get upgrade sudo apt-get remove -y docker docker-engine docker.io containerd runc sudo apt-get install ca-certificates curl sudo echo insecure >> $HOME/.curlrc curl -fsSL https://get.docker.com -o get-docker.sh && sh get-docker.sh sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy #reboot the board so the new iptables/ ip6tables come effective sudo reboot now sudo usermod -aG docker $USER sudo docker run hello-world (a slightly outdate way to install) sudo apt-get update sudo apt-get upgrade sudo apt-get install ca-certificates curl gnupg lsb-release sudo mkdir -m 0755 -p /etc/apt/keyrings sudo echo insecure >> $HOME/.curlrc sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://downlaod.docker.com/linux/debian stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null | printf "%s\n" "deb [arch=amd64] https://download.docker.com/linux/debian buster stable" | sudo tee /etc/apt/sources.list.d/docker.list curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - sudo modprobe ip_tables sudo su echo ip_tables >> /etc/modules sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin ##result sudo docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world 04341b189be6: Pull complete Digest: sha256: Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (arm32v7) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ sudo docker info Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.10.2 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.16.0 Path: /usr/libexec/docker/cli-plugins/docker-compose Server: Containers: 1 Running: 0 Paused: 0 Stopped: 1 Images: 1 Server Version: 23.0.1 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: runc version: v1.1.4-0-g5fd4c4d init version: de40ad0 Security Options: seccomp Profile: builtin Kernel Version: 4.4.194 Operating System: Debian GNU/Linux 10 (buster) OSType: linux Architecture: armv7l CPUs: 4 Total Memory: 1.944GiB Name: linaro-alip ID: Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false ##if you're not able to execute sudo apt-get update afterwards, please do the following: sudo rm /var/cache/apt/archives/lock sudo rm /var/lib/dpkg/lock

hello @Fuchsy, it sounds more like a vnc issue than a waveshare lcd panel issue to me. i've tried to reproduce it with x11vnc v.0.9.13, tinker board os: debian 10 v.2.0.14 x11vnc config: [Unit] Description=Start x11vnc at startup. Requires=display-manager.service After=syslog.target network-online.target Wants=syslog.target network-online.target [Service] Type=simple ExecStart=/usr/bin/x11vnc -display :0 -forever -loop -noxdamage -repeat -rfbauth /etc/x11vnc.pwd -rfbport 5900 -shared -capslock -nomodtweak ExecStop=/usr/bin/x11vnc -R stop Restart=on-failure [Install] WantedBy=multi-user.target client: vnc viewer v.7.0.1 i did encounter delays and random disconnection several times but looks like it's expected: https://forums.linuxmint.com/viewtopic.php?t=277139 can we have a look at the logs under /var/log ? (please rm -rf /var/log before you copy the logs)

hello @ANDESSE, i'm afraid that the only way to upgrade it to 2.1.6 is to download the os and use software such as balena etcher to flash the whole system. apt update && upgrade will only update the related debian packages

hello @Fuchsy, sounds like it's system hang to me from what you've described (even vnc is not working), we've not had this issue before, could you check the following: 1. if this hdmi panel is connected to usb touch, does the issue persist withouth usb touch? 2. does the issue persist without connecting to vnc? 3. does this issue happen when you're using other hdmi monitors? 4. does the mouse work when the issue occurrs?

hello @RichUK, there's no audiojack on tinker board 2s so i guess you're not using buttons on wired headphones for voice control? are you using wireless headphones or usb peripherals? volume control should work though

hello @hyewon, from the data you've provided, looks like you will need a MIPI converter board, also the panel has to meet the sequencing requirement; from software perspective, we don't know the ic chip so it's really hard to tell whether this panel is compatible with tinker board 2s or not. here are some of the supported panels:

hello @Justus, 1. download any of the tinker edge t os from: Tinker Board (asus.com) here i downloaded the latest version, which is mendel-eagle v.3.0.7 2. all the tools needed (android usb windows driver, adb, fastboot script ...) are located in the folder 'tools' >>Tinker_Edge_T-Mendel-Eagle-V3.0.7-20210610.zip\Tinker_Edge_T-Mendel-Eagle-V3.0.7-20210610\tools

hello @Aladonn, which tinker os did you use? and what version of anydesk have you installed? https://anydesk.com/en/downloads/linux?dv=deb_64

hello @stevenragy, these logs are common and can be ignored. we've checked with the chip vendor and are told that EGL are the ARM based OpenGL expansions for x window system, that's similar to glx on x86. Xorg uses Driver modelsettings to load libglx.so by default, libglx.so then looks up dri libs. however Xorg 2D accelerator uses DRM not dri libs so it prints the errors that you mentioned. i don't think the app can ever be executed if it's a GPU related issue, but it also depends on the mode the app's excuted (normal mode/ CLI mode) is it possible for use to have a look at the camera codes and dmesg?

hello @Mortis1369, sorry about the inconvenience, will check with team and get back to you shortly. are you developing an android 11 based os? Tinker Board 2 - Android (github.com)

to compile boot.img: source build/envsetup.shlunch WW_Tinker_Board_2-userdebug./build.sh -CKA it'll be located in directory: rockdev/Image-WW_Tinker_Board_2/

hello @shenouda, please refer to page 46, ch.8.13 "run with multi rknn tools" in Rockchip_Trouble_Shooting_RKNN_Toolkit_V1.7.3_EN.pdf rknn-toolkit/Rockchip_Trouble_Shooting_RKNN_Toolkit_V1.7.3_EN.pdf at master · rockchip-linux/rknn-toolkit (github.com)

hello @stevenragy, please try: sudo su cec-ctl --playback -o TinkerBoard2 cec-ctl -m and press the remote control keycode'd then show in the console

hello @joseph, libgpio requires gpio charcter device structure and it's only in kernel 5.0+ releases it's not supported on tinker edge r as its kernel version is 4.4 libgpiod - C library and tools for interacting with the linux GPIO character device (gpiod stands for GPIO device) Since linux 4.8 the GPIO sysfs interface is deprecated. User space should use the character device instead. This library encapsulates the ioctl calls and data structures behind a straightforward API. to build communications between tinker edge r and the 3d printer board, please refer to the '40 pin mapping table', sudo vim /boot/config.txt set the pin to =on, save, and reboot

hello @Fred, to run a shellscript at startup indeed you can edit rc.local, instead /home/linaro/start.sh, please try adjust it to: sudo bash /home/linaro/start.sh exit 0