tooz

hello @sathish, please make sure to set your mass storage/ disk access if it's on fat filesystem, or run your file manager as root sudo cp /disk/directory/rtc.json /home/linaro/Desktop/

hello @sathish, it is not built in the tinker os, if you'd like to use dhcpcd: sudo apt-get install dhcpcd5 the dhcpcd.con will be locaed in /etc/ alternatively, you can use nmcli con mod to configure the ip network

--volume=VOLUME Set initial playback volume to VOLUME, where 0.0=silent and 1.0=unchanged

hello @sathish, perhaps you can use gst-play-1.0, command: gst-play-1.0 FILE|DIRECTORY|URI [FILE2|DIRECTORY2|URI2] https://gstreamer.freedesktop.org/documentation/frequently-asked-questions/using.html?gi-language=c#how-do-i-use-the-gstreamer-command-line-interface

hello @snk, which version of os you're using for tinker board r2.0? iw phy i tried to reproduce it on tinker board r2.0 with the latest os, and the band 1 information wasn't missing: Band 1: Capabilities: 0x1962 HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI RX STBC 1-stream Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT Max RX data rate: 150 Mbps HT TX/RX MCS rate indexes supported: 0-7

hello @ICE, you can use the gpio pins to implement MLX90640 IR Thermal Camera since it uses i2c to communicate instead of csi interface: https://github.com/melexis/mlx90640-library i don't have this camera module in hand right now, but cave education has done a demo using tinker board before: https://www.facebook.com/CAVEEducation/videos/1110440046181370/

hello @snk, to use iw commands you'll need to execute them with superuser priviledge: sudo iw phy

hello @sonyan11, for uvc option, the config has to be set with the command below before make menuconfig tinker board linux 4.19: make ARCH=arm64 tinker_board_2_defconfig and then make menuconfig

hello @sushil, to enable softap mode: Developer Guide · TinkerBoard/TinkerBoard Wiki (github.com) 1. for tinker board / tinker board r2.0, download https://github.com/TinkerBoard/TinkerBoard/files/8107749/SoftAP_debian10_20220127.zip and unzip the file 2. update packages and install dnsmasq and hostapd, then execute the shellscript to enable softap sudo apt-get update sudo apt install dnsmasq hostapd move to the SoftAP_debian10_20220127 directory, and execute the script (with root access) chmod 755 Enable_SoftAP.sh Disable_SoftAP.sh ./Enable_SoftAP.sh error rfkill: cannot open /dev/rfkill: No such file or directory can be ignored 1. to get wifi back to normal mode, please execute ./Disable_SoftAP.sh (otherwise it stays in softap mode after ./Enable_SoftAP.sh is executed) 2. when doing ./Enable_SoftAP.sh or ./Disable_SoftAP.sh if the error SIOCSIFFLAGS: Operation not possible due to RF-kill occurrs, please execute echo 1 > /sys/class/rfkill/rfkill0/state it is not recommended to use concurrent mode

hello @Henri / @brick, sudo dd BS=4M if=u-boot.imx of=/dev/mmcblk0boot0 sudo dd BS=4M if=partition-table-8gb.img of=/dev/mmcblk0 sudo dd BS=4M if=boot_arm64.img of=/dev/mmcblk0p1 sudo dd BS=4M if=home.img of=/dev/mmcblk0p3 sudo dd BS=4M if=rootfs_arm64.img of=/dev/mmcblk0p4 the partition table of tinker edge t: mmcblk0boot0 4M u-boot mmcblk0 179:0 0 7.3G 0 disk ├─mmcblk0p1 128M boot ├─mmcblk0p2 1M misc ├─mmcblk0p3 2G home └─mmcblk0p4 5.1G rootfs u-boot.imx -> mmcblk0boot0 boot_arm64.img -> mmcblk0p1 home.img -> mmcblk0p3 rootfs_arm64.img -> mmcblk0p4

hello @Kajan001, for hardware encoding you can use mpph264enc plugin: gst-launch-1.0 videotestsrc num-buffers=512 ! video/x-raw,format=NV12,width=1920,height=1080,framerate=30/1 ! queue ! mpph264enc ! queue ! h264parse ! mpegtsmux ! filesink location=/home/linaro/Desktop/h264.ts

hello @sushil, is this the library you're using? mattjlewis/diozero: Java Device I/O library that is portable across Single Board Computers and microcontrollers. Tested with Raspberry Pi, Odroid C2, BeagleBone Black, Next Thing CHIP, Asus Tinker Board and Arduinos / Pico. Supports GPIO, I2C, SPI as well as Serial communication. Also known to work with Udoo Quad. (github.com)

hello @Rich, to install teamviewer on tinker board r2.0 with debian os: 1. download teamviewer.deb (armhf, 32bit) on the teamviewer official website: https://www.teamviewer.com/en/download/raspberry-pi/ 2. sudo apt-get update sudo apt-get install libqt5gui5 libqt5qml5 libqt5quick5 libqt5webkit5 libqt5qml5 libqt5core5a qml-module-qtquick-controls qml-module-qtquick2 libqt5widgets5 libqt5x11extras5 qml-module-qtquick-dialogs sudo dpkg -i teamviewer_15.40.8_armhf here is a tutorial video for your reference:

hello @Ridham, for mipi csi cameras that tinker board 2s supports are 5mp and 8mp: https://tinker-board.asus.com/doc_tb2.html#qvl/

hello @Kajan001, you can use python with gstreamer -- there are python packages that can be used for motion detection https://gstreamer.freedesktop.org/documentation/opencv/motioncells.html?gi-language=c

hello @lbispo, we've verified with tinker edge t mendel os when using two cameras, both cameras can be recognised. please give it a try.

hello @Kajan001, i'd suggst to use gstreamer and v4l2-ctl as they are more compatible on rockchip-based platforms sudo vi /boot/config.txt edit Line 60 overlay=CSI0-IMX219: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink and then reboot -- reference: rpicamsrc (gstreamer): https://gstreamer.freedesktop.org/documentation/rpicamsrc/index.html?gi-language=c

hello @jjj44, here are the commands to install ros (ros-noetic-desktop) -- verified it can be installed in debian 10 v.2.1.6 / 2.0.14 wget http://ftp.us.debian.org/debian/pool/main/g/gmp/libgmp10_6.1.2+dfsg-4+deb10u1_arm64.deb wget http://ftp.us.debian.org/debian/pool/main/n/nettle/libhogweed4_3.4.1-1+deb10u1_arm64.deb wget http://ftp.us.debian.org/debian/pool/main/n/nettle/libnettle6_3.4.1-1+deb10u1_arm64.deb wget http://security.debian.org/debian-security/pool/updates/main/g/gnutls28/libgnutls30_3.6.7-4+deb10u10_arm64.deb sudo dpkg -i libgmp10_6.1.2+dfsg-4+deb10u1_arm64.deb sudo dpkg -i libhogweed4_3.4.1-1+deb10u1_arm64.deb sudo dpkg -i libnettle6_3.4.1-1+deb10u1_arm64.deb sudo dpkg -i libgnutls30_3.6.7-4+deb10u10_arm64.deb sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list' sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-key C1CF6E31E6BADE8868B172B4F42ED6FBAB17C654 sudo apt update sudo apt install ros-noetic-desktop *notices like these are expected and can be ignored: ldconfig: file /usr/lib/mali/libmali.so is truncated ldconfig: file /usr/lib/mali/libmali.so.1.9.0 is truncated ldconfig: file /usr/lib/mali/libmali.so.1 is truncated ldconfig: file /usr/lib/mali/libmali-midgard-t86x-r18p0-x11.so is truncated ldconfig: file /usr/lib/libmali.so.1 is truncated

hello @asteele, does the issue persist if you're using other monitors? with the information provided, the other solution i can think of for now is to re-burn the sd card (or get another sd card to burn even) does the board work ok with emmc?

hello @realstuffie, yes, debian 11 image release is in the tinker board 2s os support roadmap

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.