Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/26/23 in all areas

  1. 1 point
    Here 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
  2. 1 point
    Hi 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.
  3. 1 point
    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.
  4. 1 point
    Sorry, here is the working link: Download Android 11 ROM Tinkerboard (not R2.0)
  5. 1 point
    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?
  6. 1 point
    hello @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
  7. 1 point
    hello @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
  8. 1 point
    hello @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)
  9. 1 point
    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
  10. 1 point
    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
  11. 1 point
    thank you sir, @tooz! mraa works normally. Thank you very much.
  12. 1 point
    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
  13. 1 point
    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
  14. 1 point
    hello all, my colleague has come up with a little python library called stkcam, that can be used to either to see the live preview of the mipi csi camera, or to take a picture with the mipi csi camera pypi: https://pypi.org/project/stkcam/ github: https://github.com/harryliou/stkcam so far it's supported on tinker board (r2.0) & tinker board 2s (debian 10, debian 11) here's a little how-to: ##setting up tinker board/ tinker board 2s use tinker-config to change the csi overlay: sudo tinker-config //select 5 Interfacing Options //select F1 Camera //select 0 IMX219 //or 1 OV5647 for Raspberry Camera V1 //click Ok, finish, and reboot install pip3 for python3 and stkcam: sudo apt get update sudo apt-get upgrade sudo apt-get install python3-pip pip3 install stkcam ##using stkcam for mipi csi camera live preview: python3 import stkcam from stkcam import TKCam, CamType cam = TKCam(CamType.IMX219) cam.preview() **if you'd like to take a photo using the library, please finish the process first -- exiting by ctrl + d twice) ##using stkcam to take a photo with mipi csi camera: python3 import stkcam from stkcam import TKCam, CamType cam = TKCam(CamType.IMX219) cam.take_image('/home/linaro/Desktop/image.jpg') # image path feel free to give it a try and let us know
  15. 1 point
    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:
  16. 1 point
    hello @sonyan11, what's the image version you're using? if it's not on the list then the function might not have been added -- my bad. i have updated my previous post with versions that support usb vbus control. for debian 10 kernel 4.4, please use v.2.0.20 or later
  17. 1 point
    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
  18. 1 point
    hello @captain kirk, also please use sudo tinker-config
  19. 1 point
    hello @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)
  20. 1 point
    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
  21. 1 point
    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.
  22. 1 point
    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.
  23. 1 point
    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
  24. 1 point
    hello @s1s1s1sg, yes and we're planning to release debian 11 os image for tinker board 2s soon
  25. 1 point
    hello @nishi and @Thinh Nguyen, you can control the vbus power through echo commands 1. check the kernel version with command: uname -a keep in mind that if you're using a usb keyboard, the power will be off immediately after you execute the echo off command. if you wish to turn it back on without reboot, please: 1. use a type c keyboard, or 2. connect tinker board to a pc with a ttys dongle so the commands can be executed from the putty console here are the commands to control the vbus power: linux4.4 debian10 (v.2.0.20 2023/07/13 and later): TypeA port: echo on > /sys/kernel/debug/fe900000.dwc3/vbus echo off > /sys/kernel/debug/fe900000.dwc3/vbus TypeC port: echo on > /sys/kernel/debug/fe800000.dwc3/vbus echo off > /sys/kernel/debug/fe800000.dwc3/vbus linux4.19 debian10 (v.2.1.16 2023/07/14 and later): TypeA port: echo on > /sys/kernel/debug/fe900000.dwc3/vbus echo off > /sys/kernel/debug/fe900000.dwc3/vbus TypeC port (for cc chip fusb302): echo on > /sys/kernel/debug/fe800000.dwc3/vbus echo off > /sys/kernel/debug/fe800000.dwc3/vbus TypeC port (for cc chip rt1715): echo sink >/sys/class/typec/port0/port_type echo dual >/sys/class/typec/port0/port_type linux5.10 debian11 (v.3.0.6 2023/07/31 and later): typeA port: echo on > /sys/kernel/debug/usb/fe900000.usb/hub_vbus echo off > /sys/kernel/debug/usb/fe900000.usb/hub_vbus TypeC port (both fusb302 & rt1715 use the same commands): echo sink >/sys/class/typec/port0/port_type echo dual >/sys/class/typec/port0/port_type android12 (v.3.0.2 2023/07/13 and later): typeA port: echo on > /sys/kernel/debug/fe900000.dwc3/hub_vbus echo off > /sys/kernel/debug/fe900000.dwc3/hub_vbus typeC port (for cc chip fusb302): echo on > /sys/kernel/debug/fe800000.dwc3/hub_vbus echo off > /sys/kernel/debug/fe800000.dwc3/hub_vbus TypeC port (for cc chip rt1715): echo sink >/sys/class/typec/port0/port_type echo dual >/sys/class/typec/port0/port_type
  26. 1 point
    I got same qustion, If you has some method, share with me please.
  27. 1 point
    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
  28. 1 point
    hello @saeed soleimanifar, you can get the console log disabled by modifying the /boot/cmdline.txt: console= save and then reboot
  29. 1 point
    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
  30. 1 point
  31. 1 point
    hello @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:
  32. 1 point
    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
  33. 1 point
    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
  34. 1 point
    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 --
  35. 1 point
    May i know how can I boot the OS from SD Card where the SD card is flashed with Debian OS or Ubuntu OS?
×
×
  • Create New...