tooz

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

what's the cmos battery you're using? if it's got external pins perhaps you can try connecting it with the 40 pin module on tinker board 2s for it to read the voltage

hello @Jovan, it's not possible to read the cmos battery voltage due to hardware design. the input supply voltage range cannot be read externally

hello @wahaha, you still need to download all the sources and build a complete os image in order to make the sd card work; unfortunately only building u-boot image is not enough. the easiest way is to compile the complete .img and then change the rootfs to compile u-boot: git clone https://github.com/TinkerBoard-Linux/rockchip-linux-rkbin.git mv rockchip-linux-rkbin rkbin git clone https://github.com/TinkerBoard-Linux/rockchip-linux-prebuilts-gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu.git git clone https://github.com/TinkerBoard-Linux/rockchip-linux-u-boot.git cd rockchip-linux-u-boot ./make.sh tinker_board_2 CROSS_COMPILE=/path/to/rockchip-linux-prebuilts-gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- *please change the path of CROSS_COMPILE=/ to where rockchip-linux-prebuilts-gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu- is located

hello @skyrock123, 1. the default rtc is rk808-rtc on i2c bus, you'll need to connect to the the internet at least once to sync time, with command sudo hwclock -w so that the system time (rk808-rtc) is updated 2. if you use the command: sudo i2cdetect it'll list the usage that you might want to have a check, otherwise you can have a look at this page: https://manpages.debian.org/unstable/i2c-tools/i2cdetect.8.en.html 3. if there's no external rtc module, then the data from rk808-rtc would be fetched with this command. if you're not able to connect to the internet to sync time, you can change the time and date manually with command: hwclock --set --date "2024-05-29 11:30:00" for your reference: https://www.thegeekstuff.com/2013/08/hwclock-examples/

hello @M@riusz, yes, but it's going to take a while. will keep you updated.

hello @lloydhussell, here a link of the latest android release for tinker 3n: Tinker Board 3N Android 12 V.1.0.14

hello @ken, do you have logs that we can have a look and check the compatibility?

hello @lloydhussell, you can use can-utils with android userdebug build for tinker board 3n

hello @henners48, have you tried using this version? Tinker Board S R2.0 Debian 10 V3.0.23

hello @JOHN DOE, can you detail the setup, is the board connected to other peripherals? what's the pc you're using? what's the software os version? does the board recognise other devices rather than the laptop through the usb port? does it work properly when it's not connected to the laptop?

hello @JOHN DOE, it's likely the power supply is not sufficient, please check if the cable you use and the power output of the laptop usb port meet the requirement: Requirement: ．1 x Micro-USB cable with data transfer functionality ．1 x Tinker Board power supply* or other qualified 5V/2-3A power supply** ．1 x Monitor ．1 x HDMI cable ．1 x Keyboard and mouse set * Tinker Board power supply sold separately ** Cable must deliver up to 3A of power output source: https://www.asus.com/networking-iot-servers/aiot-industrial-solutions/tinker-series/tinker-board-s/

hello @skyrock123, we've tried to reproduce the issue using image v.3.0.23 and can confirm the data can be sent and received through uart1 here are the steps for reproduction: https://www.asuswebstorage.com/navigate/a/#/s/077D58B319314CA9AB298E8F012540C04 did you connect the uart tx (from the first tinker r2.0) to uart rx (from the second tinker r2.0)?

hello @sri, in \debian-kernel\scripts\dtc\dtc-lexer.lex.c, line 634 please change YYLTYPE yylloc; to extern YYLTYPE yylloc; for your reference: https://steward-fu.github.io/website/phone/pixel3axl/dd_fix_yylloc.htm