tooz

hello @marco@bigsis.tech, for your refernce:

hello @Poko-san, we've used v.2.1.6 & v.2.0.14 for uvc testing, using cheese: you will have to switch to usb camera first, to do so, please use the "Camera Product Name" 1. you can check the Product Name with the following command in lxterminal: $ udevadm info /sys/class/video4linux/video5 | grep ID_V4L_PRODUCT ID_V4L_PRODUCT=Logitech Webcam C930e in this case the Camera Product Name is "Logitech Webcam C930e" 2. then you can open the camera with the command: $ cheese -d “Logitech Webcam C930e” we've tested 1080p/480p MJPG & YUYV configs with qv4l2 and both configs work. may we know which usb cam you're using and the configs? we've used another unknown branded usb web cam and have noticed that unstable connection can lead to failure such as cheese:1291): cheese-WARNING **: 10:17:11.512: Failed to allocate required memory.: gstv4l2src.c(658): gst_v4l2src_decide_allocation (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin29/GstV4l2Src:v4l2src2: Buffer pool activation failed

hello @Sauer, thanks for the info, to further the analysis it would be helpful to know: 1. When the problem occurred, were display and touch both not working? 2. When you rebooted the board, did it fix the issue? Or did it still persist? 3. Have you tried reboot the board or unplug/ replug hdmi and usb cable instead of changing to another board when it’s not working? from the logs we’ve seen usb being connected and disconnected, looks like the usb connector is broken, we’d suggest use another usb cable or panel to connect -- it's normal that cables get fraying over time. we'll keep looking into the issue though Nov 26 12:05:51 tinkerboard kernel: [ 4.653372] usb 1-1.3: USB disconnect, device number 4 Nov 26 12:05:51 tinkerboard kernel: [ 5.075529] usb 1-1.3: new full-speed USB device number 5 using dwc2 Nov 26 12:05:51 tinkerboard kernel: [ 5.178409] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=e5e3 Nov 26 12:05:51 tinkerboard kernel: [ 6.445379] usb 1-1.3: USB disconnect, device number 5 Nov 26 12:05:51 tinkerboard kernel: [ 6.755533] usb 1-1.3: new full-speed USB device number 6 using dwc2 Nov 26 12:05:51 tinkerboard kernel: [ 6.858572] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=e5e3 Nov 26 12:05:51 tinkerboard kernel: [ 7.981017] usb 1-1.3: USB disconnect, device number 6 Nov 26 12:05:51 tinkerboard kernel: [ 8.425481] usb 1-1.3: new full-speed USB device number 7 using dwc2 Nov 26 12:05:51 tinkerboard kernel: [ 8.527415] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=e5e3

hello @Poko-san, i've used tinker board 2s with debian 10 v.2.0.14 installed qv4l2 test utility, cheese and vlc - there's some compatibility that i cannot use cheese to take/ preview photos or videos using qv4l2: open qv4l2 -> open device -> select video5 -> start capturing uvc running successfully i've tried using vlc media player: open media -> capture device -> video device name '/dev/video5' in my case and it works too what's the usb video camera you're using? i'll look into the issues happened in cheese too, but if it's a compatibility limitation, we'd suggest to use another package

hello @marco@bigsis.tech, this is the imshow function error, perhaps you want to check and adjust the import frame

hello @JasonS, for rk3399/ v8 there's no zImage, you will have use Image instead, try: make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j4 make Image ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j8

hello @paul_nicholls, this is a tinker board '1.2' with no emmc (rk3288 based), you can download one of the images and burn it into microsd with balenaetcher android 12: Tinker Board R2.0 /Tinker Board S R2.0 Android 12 V0.0.3 debian 10: Tinker Board S R2.0 Debian 10 V3.0.11

hello @Sauer, what's the 7" touchscreen display? is it a rpi touch screen? and you're using hdmi connector instead of dsi, right? whats the syslog looks like? may we check this?

hello @marco@bigsis.tech, so the version of opencv-python was upgraded, if you've encountered import cv2.imshow() error, please remove the build-in opencv-python: python3 -m pip uninstall opencv-python then re-install: python3 -m pip install opencv-python --user

hello @marco@bigsis.tech, forgot to mention that if you're using the releases from us: https://tinker-board.asus.com/download-list.html?product=tinker-edge-r the script file of rknn toolkit installation is included (you can find it on desktop) no need to install opencv as it's included in the toolkit installation

hello @marco@bigsis.tech, i was testing tinker board 2s and did manage to compile opencv: sudo apt-get update sudo apt install libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev git clone https://github.com/opencv/opencv.git cd opencv/ git checkout 4.1 mkdir build cd build cmake -D CMAKE_BUILD_TYPE=RELEASE \ -D INSTALL_C_EXAMPLES=OFF \ -D PYTHON_EXECUTABLE=$(which python3) \ -D BUILD_opencv_python2=OFF \ -D PYTHON3_EXECUTABLE=$(which python3) \ -D WITH_GSTREAMER=ON .. make && sudo make install will check on tinker edge r and let you know

hello @marco@bigsis.tech which version of opencv were you building? were you building it on tinker board 2s?

hello @CardeLL, try 're-writing the os using ums from a micro sd card': User-Manual.pdf (asus.com)

hello @yshs, https://www.asuswebstorage.com/navigate/a/#/s/CB6E83A0F01F4669A3D543A7DB864EB14 1. download 'console-uart1-overlay.dtbo' file from the link above 2. move the file to /boot/overlays 3. sudo vim /boot/config.txt to enable console-uart1 (overlay=console-uart1-overlay) 4. reboot

hello @Francois, you'll need to resize SSD partitions before moving the root files into SSD. what editing boot.txt does only is to direct where to mount for rooting

hello @Francois, please edit mmc_root as your kernel still runs on emmc; you can use root path (i.e. /dev/nvme0 ...etc) instead of partuuid

hello @Francois, what reboot-bootloader does is to look for partable misc partition, please make sure there's a misc partition for booting

hello @Francois, there's a slight difference between tinker board (rk based) and tinker edge t (nxp based), please edit the root path for kernel cmdline and recompile: directory: packages/uboot-imx/debian/boot.txt ( mendel-uboot-imx-debian/boot.txt at mendel-imx_8m · TinkerEdgeT/mendel-uboot-imx-debian · GitHub ) line 4 and line 5 mmc_root="PARTUUID=70672ec3-5eee-49ff-b3b1-eb1fbd406bf5" sd_root="/dev/mmcblk1p2" change the sd_root= to your ssd UUID and recompile/ reflash

hello @Goolge, try this .py: https://www.asuswebstorage.com/navigate/a/#/s/845A267A0B6E4346BF90E84D32F8A8C84 -- import cv2 def main(): cap = cv2.VideoCapture('/dev/video10', cv2.CAP_V4L2) cap1 = cv2.VideoCapture('/dev/video12', cv2.CAP_V4L2) while(True): ret, frame = cap.read() ret, frame1 = cap1.read() cv2.imshow('Camera 1', frame) cv2.imshow('Camera 2', frame1) if cv2.waitKey(1) & 0xFF == ord('q'): exit = True break cap.release() cv2.destroyAllWindows() if __name__ == '__main__': main()

hello @denchakapon, we still have a couple of arrangement to make and hopefully get android 12 source code for tinker board r2.0 uploaded by the end of next week. will keep you informed

hello @Jay, you can edit the rc.local in /etc/ this is the script auto executed when booting. please add the following line in the file: sudo ifconfig eth0 down (save the modifed local.rc, and then reboot) remove this line if you'd like to use wired connection. alternatively, sudo ifconfig eth0 down can be added in /etc/init.d/rockchp.sh --it does the same job

hello @Mark, the only way to power tinker edge t is using the dc power jack connector

from the logs i'd suggest to keep the cpu freq at maximum, using adb commands below: adb root adb shell "echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" adb shell "echo performance > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor"

hello @김용래, 1. get a usb uart ttl serial console cable (similar to: https://www.amazon.com/Console-Galileo-Compatible-TTL-232R-3V3-TTL-232R_RPi/dp/B00XRBQJL8?th=1 ) 2. use the usb uart cable to connect tinker 2 (rx and tx pins) it to a pc (usb port) 3. use putty to collect logs, the setup is 'serial (refer device manager for the exact COM#), baud rate = 115200' the log looks like this: DDR Version 1.26 20210628 In channel 0 CS = 0 MR0=0x98 MR4=0x1 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x98 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride channel 0 CS = 0 MR0=0x98 MR4=0x1 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x98 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x3281F281, stride = 0x9 ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 MHz, current 856MHz OUT Boot1 Release Time: May 29 2020 17:36:36, version: 1.26 CPUId = 0x0 ChipType = 0x10, 640 mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! emmc reinit mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! emmc reinit mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000 mmc: ERROR: Card did not respond to voltage select! SdmmcInit=2 1

hello @kwakPro did you first: adb root adb remount adb pull /dtoverlay/config.txt (edit) and then adb push config.txt /dtoverlay/ ?