Leaderboard

could you guys release 1 for kernel 5.15.x please? or share how we can compile our own kernels?

Hi guys. Let me share Android 11 for Tinkerboard / Tinkerboard S 1-st revision (not R2.0) which Asus marked as outdated/legacy. You can find download link below: Download Android 11 ROM Tinkerboard (not R2.0) Bug reporting are welcome. Release is based on official Asus firmware for Tinkerboard S R2.0.

Hi everybody, Recently, I have been trying to run some bare metal code on my Tinker Board 2. I managed to compile ARM Trusted Firmware - A successfully with these commands: % git clone https://github.com/ARM-software/arm-trusted-firmware.git tf-a % cd tf-a % export CROSS_COMPILE=~/Developer/Toolchains/aarch64-none-elf/bin/aarch64-none-elf- % make PLAT=rk3399 After that, I tried to build U-Boot with these commands (the CROSS_COMPILE variable is set from previous commands): % git clone https://github.com/TinkerBoard2/u-boot.git uboot % cd uboot % export BL31=../tf-a/build/rk3399/release/bl31/bl31.elf % export KBUILD_OUTPUT=build % make tinker2_defconfig % make This, unfortunately failed with this error: DTC arch/arm/dts/rk3036-sdk.dtb Error: arch/arm/dts/.rk3036-sdk.dtb.pre.tmp:77.1-10 syntax error FATAL ERROR: Unable to parse input tree I tried to fix the problem, and I thought removing 'rk3036-sdk.dtb' from 'arch/arm/dts/Makefile' could work since it seemed to be the device tree of another board that I was building for, which happened to be ill formed. That made the problem disappear, but the same thing happened for 'rk3368-lion.dtb', 'rk3368-sheep.dtb' and a couple of other device trees. I removed them all (7 in total) and the build finally succeeded. I then created a GPT disk image, with a single FAT32 partition with my code compiled, in it. The partition started at sector 18405, so there should have been plenty space for U-Boot. I verified with gdisk that my disk image is not corrupt, so that is clearly not the problem. I tried writing U-Boot into the SD card with the instructions in https://github.com/u-boot/u-boot/blob/master/doc/README.rockchip and https://github.com/u-boot/u-boot/blob/master/doc/board/rockchip/rockchip.rst. Packaging with rockchip miniloader did kind of work, but it printed some unusual characters (Chinese or Japanese?) and a lot of diamonds with single question mark in them at the beginning, and I had to set the baud rate to 120000 to view the output properly. Using U-Boot SPL and U-Boot TPL + SPL only printed one diamond with a question mark in it. I also tried the method provided as an answer to this post, but that did not work, probably because it was for eMMC. I used this command to see if it worked: minicom -D /dev/cu.usbserial-1440 -b 115200 -o I connected my serial to USB cable as instructed in this post I am sure my board is not broken as I was able to run the official Debian image without U-Boot printing any weird characters or problems with baud rate. I wonder, if any Tinker Board engineers could share how U-Boot is built when preparing the official image. Any help is appreciated.

I was able to update Asus's debian to latest version by adding deb http://ftp.us.debian.org/debian testing main contrib non-free to /etc/apt/sources.list.d and then run "sudo apt update" "sudo apt upgrade" but... Disappointed with support level, Asus almost no activity, several questions not answered, software outdated etc

Sorry, here is the working link: Download Android 11 ROM Tinkerboard (not R2.0)

hello @Jovan, was the led (led1) on while using? please check if you're able to use the adb with mask2 cap on while booting?

hello @zain, here are some examples for your reference: https://github.com/rockchip-linux/rknn-toolkit/tree/master/examples/mxnet/fcn_resnet101 you can also check chapter 7.15 Export a segmentation model from 02_Rockchip_User_Guide_RKNN_Toolkit_V1.7.5_EN.pdf

hello @Alexandre Baiocco, this is for tinker board (rk3288), asus.gpio is not yet supported on tinker 3n -- we're planning to support it in the next release, target 2024/02

hello @lloydhussell, it's a decision for google to make -- my guess is once the feature rolls out there's a chance that aicore will not be exclusively available on pixel pro 8; if the compatibility meets surely it'll be supported on tinker board 3n as well

hello @MarciS, the build instruction for tinker board 2s: https://github.com/TinkerBoard/TinkerBoard/wiki/Tinker-Board-2-&-2S#21-build-image there are quite a lot of versions so be sure to use the right one when you do repo init -u (manifest) -b -m

hello @26.albertsilva@gmail.com, edp-dp converter is not supported on tinker 3n, the edp connectors can only be used for the edp display panels that are on the qvl: https://tinker-board.asus.com/download/Tinker_Board_3N_QVL.pdf to test out dual screen setup, here i use a hdmi tv and an 15" auo g156hab02 edp panel, with tinker 3n debian 11 image v.1.0.7: modify /boot/config.txt, uncomment the overlay line, save /boot/config.txt and reboot tinker 3n: once the overlay comes effective and the edp is recognised, you can change it to either primary or secondary display in the display settings:

hello @Jovan, modifying /boot/config.txt only allows the function to be enabled these are uart driver init loggings baud rates can be changed in user space

hello @captain kirk, also please use sudo tinker-config

hello @gavin67890, for csi cameras, the coral camera is the only camera module supported on tinker edge t thus far: https://tinker-board.asus.com/download/Tinker_Edge_T_Device_QVL.pdf though there's no qvl for the uvc cameras, we use logictec c930e for testing

hello @wahaha, we'll upload the codes by the end of this week, i'll leave a comment with the url once it's done. sorry for the inconvenience.

hello @s1s1s1sg, yes and we're planning to release debian 11 os image for tinker board 2s soon

hello @sk109sk, please add it in /boot/cmdline.txt instead sudo vim /boot/cmdline.txt add this line, save and reboot spidev.bufsiz=65536 you can check the value with: cat /sys/module/spidev/parameters/bufsiz

hello @saeed soleimanifar, you can get the console log disabled by modifying the /boot/cmdline.txt: console= save and then reboot

hello @Suntech, the easiest way would be using the dd command to clone everything out of the board then use flashtools such as balena etcher to flash the .img to other boards. 1. connect tinker board 2s to an ubuntu machine 2. to check if tinker board 2s has been recognised, use lsblk 3. to clone the eMMC: sudo dd if=/dev/sdb of=(filename).img bs=1G this will take a while, i've waited for around 35 minutes or so 4. once the cloning is finished, copy the .img file and use flashtools such as balenaetcher to flash the os to other boards *if you don't have an ubuntu machine, you can plug a flash drive to tinker board 2s, and save the output file to the flashdrive (please ensure it's got enough space) change #3 to: sudo dd if=/dev/sdb of=of=/dev/<USB device_name> bs=1G **if you're using a windows pc, you can use win32 disk imager: Win32 Disk Imager - Download [Official Site] 1. connect tinker board 2s to the pc 2. whilst tinker board 2s is in ums mode, use win32 disk imager to copy the emmc Using dd to clone eMMC OS.pdf

USB Image Tool

hello @sonyan11, i think you're able to modify uvcvideo driver to module mode through menuconfig, but tinker board 2s is not able to recognize the new module because the module driver is not updated to tinker board 2s. to update tinker board 2s' module driver, please execute these two commands in the kernel directory of the source code, make ARCH=arm64 modules make ARCH=arm64 modules_install INSTALL_MOD_PATH={INSTALL_PATH} and then update the \lib\modules\4.4.194\ kernel and \lib\modules\4.4.194\modules (of which from {INSTALL_PATH} ) onto tinker board 2s accordingly

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)

Hi @tooz I'm facing an issue using the webcam inside our electron.js app. we are trying to build electrojs app and use the camera feed inside of it, but it's rendered as a black screen, and we get these errors in the console. libGL error: unable to load driver: rockchip_dri.so libGL error: driver pointer missing libGL error: failed to load driver: rockchip libGL error: unable to load driver: rockchip_dri.so libGL error: driver pointer missing libGL error: failed to load driver: rockchip do you have any idea about those errors?

to compile boot.img: source build/envsetup.shlunch WW_Tinker_Board_2-userdebug./build.sh -CKA it'll be located in directory: rockdev/Image-WW_Tinker_Board_2/

How can I access GPIO pins on android 10 without root access? I have a 2s tinker board and I want to access serial pins. Thank you in advance

hello @marco@bigsis.tech, there are different ways and tools to copy/ dump the os either from emmc or sdcard. the easiest way i can think of is to use dd command, usually i clone the os to sdcard and use balena etcher to flash other boards; if your two tinker edge r's are conencted to the same pc, you can direct the path to the board that you're going to flash. 1. insert a sdcard, using lsblk to check its path, in my case it's /dev/mmcblk0 2. clone the os sudo dd if=/dev/mmcblk0 of=/dev/sda/emmc.img conv=noerror,sync or sudo dd if=/dev/mmcblk1 of=/dev/mmcblk0 bs=4M here i clone the whole system and it takes around 18 minutes 3. once it's done, you can use the sdcard to flash another tinker edge r under ums mode, using tools such as balena etcher

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

/dtoverlay/config.txt does not exist in Android 11 v1.0.0 Tinkerboard S R2.0 release. There are only cmdline.txt file and overlays folder: WW_Tinker_Board:/dtoverlay $ ls -la total 24 drwxrwxrwx 3 root root 16384 2021-12-14 01:16 . drwxr-xr-x 25 root root 4096 2021-12-14 00:43 .. -rwxrwxrwx 1 root root 58 2021-12-14 00:46 cmdline.txt drwxrwxrwx 2 root root 2048 2021-12-14 00:46 overlays WW_Tinker_Board:/dtoverlay $

nevermind. i solved this portion. posted the guide here for anyone who is interested: https://github.com/wahahawasabi/TinkerBoard2s

Hi everyone, I am searching for a simple "standalone" video looper software for the Tinkerboard (R2.0), similar to the Adafruit videolooper for the RaspbePi. Can anyone help me please? I am searching for sth that runs on reeboot (e.g. after crash or no electricity) so that the looper starts immeadiatley after booting, no keyboard or mous manipulation needed. Even better woudl be if it would be possible to add keyboartd shortcuts like fast forward (usually key L on keyboard) and fast backward (J) and K is usually stop/pause and play. Thank you very much in advance if you have an idea. At the moment I'm downbloading Kodi, but this always needs to be manipulated to start video... 😞 Cheers and a solution will be much appreciated 🙂 Polly

Kernel Build Questions in Tinker Edge T I installed Mendel 5 Eagle V3.0.2 on Tinker Edge T. I want to change Boot Logo of Tinker Edge T, and I want to communicate with UART device in Mendel Linux. To change the Boot Logo, Kernel must be compiled. Where can I download the kernel source for Mendel 5 Eagle V3.0.2? And, what do I need to do to communicate with the UART device in mendel linux? Guid documentation says /dev/ttymxc0 and /dev/ttymxc2 should exist, but I see /dev/ttymxc0 and /dev/ttymxc1. If /dev/ttymxc1 is checked, it is said to be incorrect. I need help with the above two. regards.

hello @metala, the two parts used here are: MURATA/DLW21SN900HQ2L , CHILISIN/CMHD21T-900M-N

hello @Chridster1, thanks for the update, i'll discuss with team in terms of meta-layer releases; for the build issue, please try prebuilt gcc and see if it works: $ make ARCH=arm64 CROSS_COMPILE=../prebuilts/gcc/linux-x86/aarch64/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- tinker_board_2_defconfig $ make ARCH=arm64 CROSS_COMPILE=../prebuilts/gcc/linux-x86/aarch64/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- rk3399-tinker_board_2.img -j8

hello @hasank, we cannot reproduce the issue, but for most cases external disks without individual power supply consume a lot of power that causes connection problem. we'd suggest to use a seperate power supply for the external disk, otherwise use an usb hub with external power supply.

Unfortunately Asus made Tinker Board, sold it and forgot. What makes Raspberry pi popular is the software support behind it. In this forum, your posts are approved very late and receive no response. Unfortunately, I also bought Tinker Board 2S. I regret. There is no support.

Hi @Excel Tinker board 2 supports 3x USB 3.2 Gen 1 TYPE-A ports and 1x USB3.2 Gen 1 TYPE-C OTG port. The TYPE-A and TYPE-C ports are each in a separate USB 3.2 Gen 1 group. Since the three TYPE-A ports of Tinker Board 2 are implemented by USB HUB. When each TYPE-A port is used individually, each port can support up to 5Gbps; however, when all 3 TYPE-A ports are used simultaneously, they will share 5Gbps of bandwidth. If you have a requirement for two 5Gbps USB ports, it is recommended that you use TYPE-A and TYPE-C to implement your requirement, respectively. Thanks.

Hi @Sohrab: Please reference the following wiki for Tinker Board 2 (RK3399) mraa library on Android. https://github.com/TinkerBoard/TinkerBoard/wiki/Developer-Guide#mraa-library-for-android

hello @hisataro, please continue follow the instruction, now you'll need execute this command adb push boot.img /storage/emulated/0/Download to flash the image 2. Copy the boot image to your device adb push boot.img /storage/emulated/0/Download/ 3. Download the latest version of Magisk Installation | Magisk (topjohnwu.github.io) 4. Install Magisk adb install Magisk.apk 5. Launch Magisk from your device 6. Press the Install button 7. Choose “Select and Patch a File” in method, and select the boot.img file, The Magisk app will patch the boot.img file to [Internal Storage]/Download/magisk_patched_[random_strings].img 8. Pull magisk_patched_[random_strings].img to your PC adb pull /storage/emulated/0/Download/magisk_patched_[random_strings].img 9. Flash boot image patched by magisk in fastboot mode adb reboot-bootloader fastboot flash boot magisk_patched_[random_strings].img fastboot reboot

hello @hisataro, please try the following and see if the device can be found: fastboot devices if the device has been detected, you can try the reboot fastboot command otherwise, we'd suggest to re-flash the device

hello @RichUK, you can root the device using Magisk, here's a brief instruction: -- 1. Prepare boot image -- you can either: a. Get the latest boot image from Tinker Board website: Tinker Board (asus.com) or b. build boot image from source code: Tinker Board 2 - Android · GitHub 2. Copy the boot image to your device adb push boot.img /storage/emulated/0/Download/ 3. Download the latest version of Magisk: Installation | Magisk (topjohnwu.github.io) 4. Install Magisk adb install Magisk.apk 5. Launch Magisk from your device 6. Press the Install button 7. Choose “Select and Patch a File” in method, and select the boot.img file, The Magisk app will patch the boot.img file to [Internal Storage]/Download/magisk_patched_[random_strings].img 8. Pull magisk_patched_[random_strings].img to your PC adb pull /storage/emulated/0/Download/magisk_patched_[random_strings].img 9. Flash boot image patched by magisk in fastboot mode adb reboot-bootloader fastboot flash boot magisk_patched_[random_strings].img fastboot reboot --

Hi, We are new to Tinker Board coming from Raspberry Pi 4. We need an OS to build upon and to decide which components we want to install. Although the Asus Linux guys seem to have don a great job in building a Linux with all the bells and whistles, but our system must be light weight, as it runs as an IoT device and I can not afford/risk to update any oft the certainly upcoming vulnerabilities in packets which we are not using anyways. As we will run 1000s of these devices, I can not carry around unnecessary packets. So instead of taking the heavy Tinker OS, throwing away everything Asus was working so hard on, I need a Debian base image to add stuff. Raspberry OS has a tiny version which was a perfect start, but it does not run on ATB . So far, I haven't been able to install anything else than Tinker OS. All alternatives I tried simply did not start up (regardless of the maskrom jumper): DietPi Tinker Board DietPi RockPro64 Armbian Debian ARm Tinker OS boots up immediately. Is there a Debian based distro available to start building the required configuration upon? Thanks

I try to use balena Etcher to install https://github.com/home-assistant/operating-system/releases/download/7.4/haos_tinker-7.4.img.xz in UMS mode. But it failed to boot up. No any screen information or current status show off. Did anyone success to install home assistant?

Samba doesn't want to be installed using other dependencies as an excuse. but i solved his problem. it's ok with one command, like this: sudo apt-get install python-samba samba-common-bin samba-libs samba libwbclient0 libsmbclient

linaro@tinkerboard:~$ linaro@tinkerboard:~$ linaro@tinkerboard:~$ cat /etc/*release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" VERSION_CODENAME=stretch ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" linaro@tinkerboard:~$ linaro@tinkerboard:~$ uname -a Linux tinkerboard 4.4.132+ #1 SMP Wed Aug 21 19:15:55 CST 2019 armv7l GNU/Linux linaro@tinkerboard:~$ linaro@tinkerboard:~$ linaro@tinkerboard:~$ sudo apt-get update Err:1 http://tprd.asus.com:8000 stretch InRelease Could not resolve 'tprd.asus.com' Hit:2 http://repo.linaro.org/ubuntu/linaro-overlay stretch InRelease Hit:3 http://security.debian.org stretch/updates InRelease Ign:4 http://cdn-fastly.deb.debian.org/debian stretch InRelease Hit:5 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease Hit:6 http://cdn-fastly.deb.debian.org/debian stretch Release Reading package lists... Done W: Failed to fetch http://tprd.asus.com:8000/dists/stretch/InRelease Could not resolve 'tprd.asus.com' W: Some index files failed to download. They have been ignored, or old ones used instead. linaro@tinkerboard:~$ linaro@tinkerboard:~$ linaro@tinkerboard:~$ sudo apt-get upgrade -y Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. linaro@tinkerboard:~$ linaro@tinkerboard:~$ ------------------------------------------------------------------------------------- there is also this error Err: 1 http://tprd.asus.com:8000 stretch InRelease Could not resolve 'tprd.asus.com' has the repository address changed ? thank's

Hello, I invested over a year on this project and spent many frustrating hours getting a tablet based OS to perform like a version made for TV's. This is not a finished product, but I thought some of you may find it useful. I am not a developer and therefore cannot guarantee an issue free experience. I stepped away from the project due to getting stuck in many areas. If anyone with the skills, time and willingness to help wants to help me polish this OS...feel free to send me a PM. Without further delay, I present AvA ROM (Android Video Appliance) for Tinkerboard: Download: AvA ROM RC1 Things to know: Based on Android 7.1.2. Works best with keyboard and mouse. Plugging in wireless remotes causes severe slowdown (solution = Android TV Remote app). Shutdown/sleep doesn't work well. Should run on Tinkerboard S. Not licensed for Netflix or Disney Plus (most other apps and games work). Image is 2.46 GB in size (minimum 4GB SD card). There are workarounds for the above licensing woes, solutions are just a Google search away. I am not sure if the forum moderators will approve this post immediately, but look forward to hearing some of you got to try it out. Best regards, WrekLess.

If there's any failure encountered during the OS writing process on Tinker Board S, you can either recover using the UMS from eMMC if eMMC’s U-Boot still workable, or re-writing the OS using UMS from a microSD card if there's a problem booting from eMMC's U-bbot. Below are the procedures: UMS from eMMC eMMC’s U-Boot still workable and had built-in the UMS function. Can use the UMS mode to re-flash The eMMC need have a workable U-Boot. Connect Tinker Board S to PC via Micro-USB. It would booting & create the partitions like a USB drive. (please remove other extend device on board) Just flash as the old way. UMS from SD card eMMC’s U-Boot is broken to booting or not built-in the UMS function (e.g. 3rd party custom image). Can trigger the UMS mode from SD card Flash the Image (with UMS’s U-Boot) to SD card. Install the SD card to Tinker Board S. Plug the Jumper on the Maskrom mode. (force to boot from SD, jump out the eMMC) Connect Tinker Board S to PC via Micro-USB, then there will become as USB mass storage on your computer Then you can flash the eMMC as usual, the old way. (e.g.: win32DiskImager, etcher and so on) After finish the image flash, unplug the USB from PC and then put the jumper at the "no function" mode. Plug in the AC adaptor to boot the device It would boot successfully & create the partitions like a USB drive. (please remove other extend device on board) Without UMS mode Recovery from SD’s image system & without the PC mode (ready on TinkerOS v2.0.4 or above) Plug the Jumper on the Maskrom mode. (force to boot from SD, jump out the eMMC) Flash the Image (any can bootable) to SD card. Plug the SD card to Tinker Board S. Booting the Tinker Board S. It would booting to the RootFS. Then dd or other ways to flash new image file to eMMC(mmcblk1). * Further details could be find on Setup - Tinker Board Wiki (tinkerboarding.co.uk).

Could I use this SBC to install Ubuntu 20.04 and ROS Noetic?

Hi Brian, try this: use "tinker-power-manager" or find it in "tinker-config" this command-line tool. (make sure you exec it via sudo or root)

Hi Pirate, For Tinker Board 2, the max loading (all connectors been connected) power is around 30W. So considering the degradation of conversion efficiency of some power supplies, we provided a conventional 19V's 45W for reference. (You can check with our user manual, https://tinker-board.asus.com/doc_tb2.html#user, page. 18.) So, if your would not connect with power-hungry USB devices, 15~20W should meet most of the usage. (without others, board only, max stress around ~10W.) And the website, it is should be the maintenance error, written too large as a reference value, which we will arrange to revision. Is 12V or 19V better? My understanding is 12V leads to more amps, so should I go 12v? --> No, 12~19V all would re convert to board used voltage, so you can just make sure the totally watt. Is it max 45W or 65W because both websites say a different thing. --> Like above, you can reference 45W or depends on real usage needs. Does anyone have a link to a compatible power supply, preferably on Amazon.ca? --> All safety compliant, and 5.5/2.5mm DC plug, 12~19V +-5% adapters should be fine. (You can find follow info from our user manual too, https://tinker-board.asus.com/doc_tb2.html#user, page. 18.) Thanks.

Introduction RKNN-Toolkit is a software development kit for users to perform model conversion, inference and performance evaluation on PC, RK3399Pro. AI Compute Stick or RK3399Pro Linux development board. https://github.com/rockchip-linux/rknn-toolkit/tree/v1.3.2