tooz

hello @minami, it's been updated to github: TinkerBoard-Android/rockchip-android-manifest (github.com) sorry for the inconvenience

hello @haonc, i don't think this camera module is on the qualified vendor list nor been calibrated yet. i will let you know once i have more information from my colleagues.

hello @Tolga, please refer to the setting below. It’s not necessary to use uart1, uart2 or uart4 can be used, too. Using uart3 however is not suggested, since it’s used for uart log output https://github.com/TinkerBoard/TinkerBoard/wiki/User-Guide#gpio-config-table-for-tinker-board-and-tinker-board-s First, modify the /boot/config.txt file as follows, and then reboot to enable I2C1 and I2C4. ##### Hardware Interface Config ####### Note: fiq_debugger and uart3 use the same pin. Set fiq_debugger first while bb oth on. ## ## Note: uart4 and spi0 are the same pins. Set the latter one while both on. ## ## Note: uart2 is the same pins to pwm2 and pwm3. Set the latter one while both on. ## intf:fiq_debugger=on intf:i2c1=on intf:i2c4=on #intf:spi0=off #intf:spi2=off #intf:pwm2=off #intf:pwm3=off intf:pcm_i2s=on intf:uart1=on #intf:uart2=off #intf:uart3=off #intf:uart4=off Chip,line Device Path GPIO number Function2 Function1 GPIO Pin# Pin# GPIO Function1 Function2 GPIO number Device Path Chip,line --- --- --- --- VCC3.3V_IO --- 1 2 --- VCC5V_SYS --- --- --- --- 8,4 GPIO:/sys/class/gpio/gpio252 I2C:/dev/i2c-1 252 --- I2C1_SDA GPIO8_A4 3 4 --- VCC5V_SYS --- --- --- --- 8,5 GPIO:/sys/class/gpio/gpio253 I2C:/dev/i2c-1 253 --- I2C1_SCL GPIO8_A5 5 6 --- GND --- --- --- --- 0,17 GPIO:/sys/class/gpio/gpio17 17 --- TEST_CLKOUT GPIO0_C1 7 8 GPIO5_B1 UART1_TXD --- 161 GPIO:/sys/class/gpio/gpio161 UART:/dev/ttyS1 5,9 --- --- --- --- GND --- 9 10 GPIO5_B0 UART1_RXD --- 160 GPIO:/sys/class/gpio/gpio160 UART:/dev/ttyS1 5,8 5,12 GPIO:/sys/class/gpio/gpio164 SPI:/dev/spidev0 UART:/dev/ttyS4 164 UART4_CTSN SPI0_CLK GPIO5_B4 11 12 GPIO6_A0 I2S_SCLK --- 184 GPIO:/sys/class/gpio/gpio184 6,0 5,14 GPIO:/sys/class/gpio/gpio166 SPI:/dev/spidev0 UART:/dev/ttyS4 166 UART4_TXD SPI0_TXD GPIO5_B6 13 14 --- GND --- --- --- --- 5,15 GPIO:/sys/class/gpio/gpio167 SPI:/dev/spidev0 UART:/dev/ttyS4 167 UART4_RXD SPI0_RXD GPIO5_B7 15 16 GPIO5_B2 UART1_CTSN --- 162 GPIO:/sys/class/gpio/gpio162 UART:/dev/ttyS1 5,10 --- --- --- --- VCC3.3V_IO --- 17 18 GPIO5_B3 UART1_RTSN --- 163 GPIO:/sys/class/gpio/gpio163 UART:/dev/ttyS1 5,11 8,9 GPIO:/sys/class/gpio/gpio257 SPI:/dev/spidev2 257 --- SPI2_TXD GPIO8_B1 19 20 --- GND --- --- --- --- 8,8 GPIO:/sys/class/gpio/gpio256 SPI:/dev/spidev2 256 --- SPI2_RXD GPIO8_B0 21 22 GPIO5_C3 --- --- 171 GPIO:/sys/class/gpio/gpio171 5,19 8,6 GPIO:/sys/class/gpio/gpio254 SPI:/dev/spidev2 254 --- SPI2_CLK GPIO8_A6 23 24 GPIO8_A7 SPI2_CSN0 --- 255 GPIO:/sys/class/gpio/gpio255 SPI:/dev/spidev2.0 8,7 --- --- --- --- GND --- 25 26 GPIO8_A3 SPI2_CSN1 --- 251 GPIO:/sys/class/gpio/gpio251 SPI:/dev/spidev2.1 8,3 7,17 GPIO:/sys/class/gpio/gpio233 I2C:/dev/i2c-4 233 --- I2C4_SDA GPIO7_C1 27 28 GPIO7_C2 I2C4_SCL --- 234 GPIO:/sys/class/gpio/gpio234 I2C:/dev/i2c-4 7,18 5,13 GPIO:/sys/class/gpio/gpio165 SPI:/dev/spidev0.0 165 UART4_RTSN SPI0_CSN0 GPIO5_B5 29 30 --- GND --- --- --- --- 5,16 GPIO:/sys/class/gpio/gpio168 SPI:/dev/spidev0.1 168 --- SPI0_CSN1 GPIO5_C0 31 32 GPIO7_C7 UART2_TXD PWM 239 GPIO:/sys/class/gpio/gpio239 UART:/dev/ttyS2 PWM:/sys/class/pwm/pwmchip3 7,23 7,22 GPIO:/sys/class/gpio/gpio238 UART:/dev/ttyS2 PWM:/sys/class/pwm/pwmchip2 238 PWM2 UART2_RXD GPIO7_C6 33 34 --- GND --- --- --- --- 6,1 GPIO:/sys/class/gpio/gpio185 185 --- I2S_LRCKRX GPIO6_A1 35 36 I2S_LRCKRX UART3_RXD --- 233 GPIO:/sys/class/gpio/gpio223 UART:/dev/ttyS3 7,7 7,8 GPIO:/sys/class/gpio/gpio224 UART:/dev/ttyS3 224 --- UART3_TXD GPIO7_B0 37 38 GPIO6_A3 I2S_SDI --- 187 GPIO:/sys/class/gpio/gpio187 6,3 --- --- --- --- GND --- 39 40 GPIO6_A4 I2S_SDO0 --- 188 GPIO:/sys/class/gpio/gpio188 6,4

hello @Shtrihcode, this will be fixed in the next release, thanks for letting us know and sorry for the inconvenience

hello @User 604, 1. did you get camera preview sucessfully when you executed command? gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink 2. seems like the cameras you use don't support NV12 format, also the cameras used are not specified in the commands. please use this command to check the cameras' video nodes: v4l2-ctl --list-devices and then use this commend to check if you can get a preview smoothly: gst-launch-1.0 v4l2src device=/dev/videoN ! videoconvert ! autovideosink ^ /dev/videoN -- please change the 'N' to the actual # of the video node you're using

hello @User 604, 3x USB A ≈13.5W, USB C ≈7.5W; please make sure the adapter that you use provides sufficient power. OTG for USB C means both host mode and device mode are supported at the same time, so no need for extra configuration, if the camera that connects to the USB C port's been detected/ recognized. However please keep in mind that the 4 USB A ports use the same host controller via an usb hub so they share the same bandwith; the USB C uses another host controller and therefore doesn't share the same bandwith with the 4 USB A ports. please try this command and see if the issue still persists: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink reference: https://tinker-board.asus.com/doc_tb.html#camera/

hello @gigigagagogo, this forum is dedicated to tinker series (single board computers); for laptop related questions please visit: https://zentalk.asus.com/t5/laptop/ct-p/Laptop

hello @Unbroken, the new tinkeros (debian 11) was released: Tinker Board (asus.com) ; the system should be more compatible imo

hello @User 604 do you have the product name/ serial of the basler usb3 cameras you're using so i can have a look at the specifications and support?

hello @hisataro, you can burn a SD card with Debian OS, save the Android OS (.img) file into the card, and use dd command to write the Android image from SD card to emmc: Download Debian OS from Tinker Board website -- the latest version is Tinker Board 2 /2S Debian 11 (kernel 5.10) v3.0.6 Use BalenaEtcher to flash the Debian OS to a SD card, please make sure the flashing is sucessful and Tinker Board 2S is bootable with the image Download and save Android OS into the same SD card that has Debian OS in it – you don’t need to use BalenaEtcher for this step, just save the Android OS as file Insert the SD card into the Tinker Board 2S you’d like to flash Android OS onto, and boot the device from SD card Once the device is boot up, use dd command to write the Android OS into device’s emmc: sudo dd bs=4M if=/path/to/TinkerOSAndroid.img of=/dev/mmcblk0 To verify, power off the device and remove the SD card, and boot the device from emmc, the expected result is that Tinker Board 2S boots from emmc with Android OS.

hello @Omirax, the default password is linaro

hello @Vaa, will check with team and let you know hello @James Kim, sorry for the late reply, please try this command and see if the camera module can be recognised: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink

hello @Fu-. we are checking with the soc vendor, at the same time, may i know where this ↑ reference came from? thank you

hello @Fu-., i was too stupid to realize that you meant the 'reproduce.zip'. i just set up the enviorment and can confirm it takes about 1 - 2 minutes to get the result.jpg. i'll let you know as soon as possible if there's any new findings.

hello @Fu-., i've downloaded your file and installed opencv/ libjpeg-turbo with your cmake list, however i cannot find the sample.zip. is this file missing or is it in the other zip files? Build and execute samples $ unzip sample.zip $ cd ~/sample $ make $ export OPENCV_OCL4DNN_CONFIG_PATH=~/.cache/opencv/4.x/opencl_cache/ARM--Mali-T860--1_2 $ ./sample bus.jpg

hello @Fu-. may i knnow how your environment and how you run the inference, i'll see if i can reproduce the performance issue

hello @Fu-., and are you using yolov5? the debian 11 os that just released?

hello @brick, the partition table: what's the issue you're facing now?

hello @Oswald, i don't think this gsm shield is on the qualivied vendor list but i'll see if it's compatible with tinker board s r2.0 from the specification. do you have a model name of the shield or a product page link? and if possible, is it okay to share the dmesg logs?

hello @Vaa, the debian 11 header file for tinker board 2s can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/4A6FF93C2E304C2598FB3D74DE583F824

hello @s1s1s1sg / @jons, debian 11 for tinker board 2s is now released and can be downloaded here: Tinker Board 2 /2S Debian 11 (kernel 5.10) v3.0.6

hello @shizimi i've uploaded a simple instruction on wol in the attachment. Tinker Board R2.0_Enable WoL-230728.pdf

hello @shizimi, wake on lan from sleep = supported wake on lan from shutdown = not supported are you trying to perform wake on lan from sleep?

hello @shizimi, yes, wake on lan is enabled by default. more information on wake on lan: https://wiki.debian.org/WakeOnLan

hello @walter if you're using tinker board (first gen, no s, just tinker board): rx: pin10, tx: pin8 otherwise it’s pin36 for rx and pin37 for tx to connect to the serial please set the baud rate to 115200