tooz

hello @shizimi, for tinker board 3 & 3s: Tinker Board 3 & 3S · TinkerBoard/TinkerBoard Wiki · GitHub there's also a github page for tinker series (in the works) Hello from ASUS Tinker Board Series Documentation | ASUS Tinker Board Series Documentation

hello @wahaha, the commands are correct, for the actual ddr bin and miniloader bin used for the project, please refer to rkboot/rk3399miniall.ini https://github.com/TinkerBoard/rockchip-linux-rkbin/blob/linux4.19-rk3399-debian10/RKBOOT/RK3399MINIALL.ini

hello @wahaha, in short: yes. idbloader is different from uboot, and you will need to dd dbloader in order to boot into uboot idbloader will need to be located in seek 0x64 in emmc whether the individual partition exists or not

hello @wahaha, from what you've decribed it's likely that the board isn't booting to either first loader or uboot. please be sure that the idbloader is located in 0x64 instead of 0x40 dd if=$IMAGES/idbloader.bin of=$DEVICE seek=64 conv=nocreat

hello @Cha.JH, android 12 is supported on tinker board 2s and the image can be downloaded here: Tinker Board 2 /2S Android 12 V3.0.2

hello @Augusto Hertz, yes, we're planning to have the first release of android image for tinker board 3 soon

hello @Kebin.h, if you must use csi cameras, we'd suggest you to stick to the existing products that are csi-enabled, or stay tuned for the future product updates

hello @Nige, i guess the hotkey you're looking for is ctrl+alt+L (xflock); xflock calls light-locker to lock the screen

hello @hisataro, sure, and in case you want to try on debian -- modify /boot/config.txt and reboot sudo vi /boot/config.txt intf:i2c7=on overlay=i2c7_egalax

hello @hisataro, you can enable egalax touch driver through overlay in tinker config app 1. open tinker config app > interface > set 'i2c7' to on 2. open tinker config app > overlay > check 'i2c7_egalax' and then reboot to make the changes come effective

hello @Didjya7, please contact the distributor (where the board was purchased) or customer service through: https://www.asus.com/support/service-center-location/

hello @esperal, my bad, i thought you're talking about tinker board and tinker board 2s, please try cat /proc/boardid this command instead:

hello @Shin, 1. for kernel 5.10, please replace files in gpio_lib_c_rk3399 with https://www.asuswebstorage.com/navigate/a/#/s/3059D9ACD7AF4D849E68AB69661499C84 2. and then rebuild and install wiringpi libraries: cd /usr/local/share/gpio_lib_c_rk3399 sudo ./build clean sudo ./build uninstall sudo ./build

hello @esperal, you can check the hardware version with command: cat /proc/boardinfo

hello @RestingSheep, haven't looked into the second question but for samba, try using aptitude for installation instead of apt. sudo apt install aptitude sudo aptitude install samba it will ask you if you want to keep the current versions of the packages, select n for no and continue samba installation xrdp can be installed using aptitude too sudo aptitude install xrdp

hello @Shin, sorry for the inconvenience. this was caused by a bug that we're aiming to fix in the next releases (for both kernel 4.19/ 5.10), before that, please follow the steps below to fix it manually. 1. update the system time (the compiler library would check it so the time has to be correct) 2. use commands to rebuild and reinstall wiringpi libraries for tinker board 2s: cd /usr/local/share/gpio_lib_c_rk3399 sudo ./build clean sudo ./build uninstall sudo ./build

hello @jeffbarbs, there's no document about the rated current (at least for now, i'll keep you updated) and these are the only two power pins on tinker board 3n.

hello @jeffbarbs, the rated current for both of the pins is 0.4a

hello @Shin, what's the software you're using? from the other post i saw the environment is kernel 4.4, which is quite old. i'd encourage you to use a more recent image: Tinker Board (asus.com) (the latest is debian 11 v.3.0.18 kernel 5.10) 1. to read i2c/ spi you can use 3rd party libraries such as python-periphery: https://pypi.org/project/python-periphery/ 2. to access gpio through sysfs interface, first you'll need to check the tinker board 2s pinout (see E22240_Tinker_System_2_EM_V2_WEB.pdf (asus.com) page 15 pin definitions) for example chip 0, line 8 GPIO: /sys/class/gpio/gpio8 TEST_CLKOUT2GPIO0_B07 GPIO output control example *Console commands: //Export the GPIO pin: echo 8 > /sys/class/gpio/export //Set the GPIO pin to output mode: echo out > /sys/class/gpio/gpio8/direction //Set value to GPIO pin: echo 1 > /sys/class/gpio/gpio8/value //Read the GPIO value: cat /sys/class/gpio/gpio8/value more reference on sysfs: https://www.kernel.org/doc/Documentation/gpio/sysfs.txt both i2c & spi are in accordance with standard interfaces, if the hardware isn't working as expected, there might be an issue that needs the correct driver to enable the system more examples on how to use gpio can be found on the github wiki: https://github.com/TinkerBoard/TinkerBoard/wiki/User-Guide#gpio-config-table-for-tinker-board-2s

hello @Shin, will using sysfs interface suit your needs for gpio programming?

hello @Shin, the differences of the libraries might be the cause of delay. please use the following commands and see if it improves: * Console commands: //Export the GPIO pin: echo 8 > /sys/class/gpio/export //Set the GPIO pin to output mode: echo out > /sys/class/gpio/gpio8/direction //Set value to GPIO pin: echo 1 > /sys/class/gpio/gpio8/value //Read the GPIO value: cat /sys/class/gpio/gpio8/value

hello @Kebin.h, what's the operating system you're developing? (debian/ android ... etc)

hello @t.kani, For Tinker Board 2 For Tinker Board 2 / Tinker Board 2S Method 1: Convert the logo file to 24 bit BMP file. It is recommended to use Window Paint for conversion. Note: After converting to 24 bit BMP file, the BMP file MUST be less than 700K bytes. Rename the BMP file to logo.bmp Copy logo.bmp and rename it to logo_kernel.bmp Replace logo.bmp and logo_kernel.bmp with logo.bmp and logo_kernel.bmp under sourcecode/kernel. Build kernel image and flash kernel image. Method 2: Convert the logo file to 24 bit BMP file. It is recommended to use Window Paint for conversion Note: After converting to 24 bit BMP file, the BMP file MUST less than 700K bytes. Rename the BMP file to logo.bmp Copy logo.bmp to sourcecode/kernel/scripts/ Execute the following command on the ubuntu server: ./bmpconvert logo.bmp You will see the following message after the command is successful Powering on device, and open terminal. Enter “reboot-bootloader” in terminal to enter fastboot mode Execute command to flash logo.bmp into splash partition fastboot flash splash logo.bmp

hello @t.kani, please refer to the developer guide 'change boot logo': Developer Guide · TinkerBoard/TinkerBoard Wiki (github.com)

hello @Jovan, this issue has been fixed in v.3.0.16, please use this version (or any version later than v.3.0.16) and give it a try. the latest os released is v.3.0.18: Tinker Board 2 /2S Debian 11 (kernel 5.10) v.3.0.18