Leaderboard
Popular Content
Showing content with the highest reputation since 01/23/24 in all areas
-
1 pointhello @tsukazaki, we're aiming to include this in the upcoming release and it will be supported in v.1.0.6 or later versions and here are the sources and docs for eapi: Tinker Board 3 & 3S · TinkerBoard/TinkerBoard Wiki
-
1 pointhello @esperal, my bad, i thought you're talking about tinker board and tinker board 2s, please try cat /proc/boardid this command instead:
-
1 pointhello @esperal, you can check the hardware version with command: cat /proc/boardinfo
-
1 pointhello @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.
-
1 pointhello @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
-
1 pointhello @Jovan, it's not possible to read the cmos battery voltage due to hardware design. the input supply voltage range cannot be read externally
-
1 pointHere it is : adb connect [tinker boad ethernet IP] adb root adb remount adb push MindTheGapps-12.1.0-arm-20231025_200802\system\product /system adb push MindTheGapps-12.1.0-arm-20231025_200802\system\system_ext /system adb push MindTheGapps-12.1.0-arm-20231025_200802\system\addon.d /system adb shell pm trim-caches 128G adb reboot
-
1 pointHi guys. Let me share Android 12 for Tinkerboard / Tinkerboard S 1-st revision (not R2.0) which Asus marked as outdated/legacy. You can find download link below: Download Android 12 ROM Tinkerboard (not R2.0) Bug reporting are welcome. Release is based on official Asus firmware for Tinkerboard S R2.0.
-
1 pointHi 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.
-
1 pointSorry, here is the working link: Download Android 11 ROM Tinkerboard (not R2.0)
-
1 pointhello @Jovan, was the led (led1) on while using? please check if you're able to use the adb with mask2 cap on while booting?
-
1 pointhello @Jovan, 1. the connection should be type c port (tinker board 3n) to type a port (macbook) 2. both the jumper caps need to be removed 3. no need to adjust mask1 dip switch
-
1 pointhello @Jovan, please remove the yellow jumper cap, and re-do the procedure (connecting tinker board 3n to the computer) again booting without the jumper cap attached so the tinker board 3n can start on uboot and the board should be in ums mode
-
1 pointhello @Jovan, the cc logic controllers between tinker board 2s and tinker board 3n are different -- for tinker board 3n, if both the ports connected are type c port, the controller will not be able to recognise which port should be in host mode and which port should be in device mode. for tinker board 3n i would recommend to connect type c port from tinker board 3n to type a (macbook)
-
1 pointhello @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
-
1 pointhello @captain kirk, also please use sudo tinker-config
-
1 pointhello @captain kirk, imx219 is supported on tinker board r2.0, i don't think you need to add an overlay, but if you must, try modify the last line: overlay=CSI0-IMX219 save and then reboot to test and see if the camera works: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink reference: Tinker Board (asus.com)
-
1 pointhello @hisataro, thanks for the details. at this point, we would suggest to re-flash the device first: User Guide · TinkerBoard/TinkerBoard Wiki (github.com) once the flashing is done, please copy the boot image to the device. the boot.img file (TB2_Android11_v2.0.6_boot_img) is re-uploaded and can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/50AF1C5364224C2BA8C8A5802DD779064 adb push boot.img /storage/emulated/0/Download/ then you can start rooting the device using magisk, please follow along the steps:
-
1 pointhello @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
-
1 pointhello @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
-
1 pointhello @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 --