Jump to content

tooz

Tinker Engineer
  • Content Count

    514
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by tooz

  1. hello @ihatemundays, i think the processes should be similar but i'll let you know with the firmware versions
  2. hello @ChaJH, how did you solve the problem? did you redownload the source codes, or did you use the sample codes of mraa api for tinker board 2?
  3. hello @ChaJH, 1. i mean the tinker board android os version you're using (for example android 11 v.2.0.8), did you get the sources from here? TinkerBoard-Android/rockchip-android-manifest (github.com) 2. the sample codes from this .zip does include libmraajava.so, would you like to give it a try? The Sample codes of Mraa API for Tinker Board 2: Android-MraaDemo_tinkerboard2.zip
  4. hello @shizimi, you can either: 1. remove the notification package with this command: sudo apt-get remove xfce4-notifyd sudo apt reboot now or 2. toolbar ->preferences ->desktop session settings -> uncheck every application, and then reboot tinker board r2.0 method #2 will not remove the audio jack plugged in notification, if you'd like to remove the notifications related-to the audio jack, comment out everything that uses 'notify-send' in the directory /etc/audio/ to remove the audio jack detection function completely, edit the audio.conf and make the config 'jack_auto_switch' =off sudo vim /etc/audio/audio.conf jack_auto_switch="off"
  5. hello @shizimi, are you using the debian tinker os or the android one?
  6. 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
  7. hello @lloydhussell, yes, android 14 support is in the roadmap for tinker 3n the machine learning feature you mentioned requires android aicore: https://developer.android.com/ml/aicore and the aicore system service is only available on pixel pro 8 devices so far: https://developer.android.com/ml/aicore?hl=en#supported-functionality
  8. tooz

    Compiling Android

    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
  9. hello @wahaha, to generate uboot.img for sd cards: 1. please compile the .img with command (aka 'the normal way' to compile .imgs) ./build.sh 2. use sdboot.sh to overwrite the device/rockchip/common/scripts/sdboot.sh in the sources sdboot.sh can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/8D32B97F2E6D428A9344DB456B2CC5464 3. generate sd_uboot.img with command sudo ./device/rockchip/common/scripts/sdboot.sh -t uboot the sd_uboot.img will be located in rockdev directory 4. flash sd_uboot.img to sd card -- you can either use tools like balenaetcher or the sudo dd command
  10. 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
  11. 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:
  12. hello @kalijana, you can root tinker board 3n with magisk: 1. to download the latest android tinker os for tinker 3n: Tinker Board (asus.com) //alternatively, you can compile android os with sources too 2. to download the latest version of magisk apk: https://github.com/topjohnwu/Magisk 3. copy the boot image to tinker 3n with command: adb push boot.img /storage/emulated/0/Download/ 4. install magisk.apk with command: adb install Magisk.apk 5. [magisk] launch magisk, and hit 'install' on the right of magisk (detailed instructions on magisk can be found on topjohnwu's github: https://topjohnwu.github.io/Magisk/install.html ) 6. [magisk] click 'select and patch a file', and select the boot.img file 7. [magisk] the magisk app will patch the boot.img file to [Internal Storage]/Download/magisk_patched_[random_strings].img 8. [magisk][host machine] pull the magisk img file ( naming would be something like: magisk_patched_[random_strings].img to your host pc/ machine, with command" adb pull /storage/emulated/0/Download/magisk_patched_[random_strings].img 9. flash tinker 3n with boot image patched by magisk in fastboot mode, with commands: adb reboot-bootloader fastboot flash boot magisk_patched_[random_strings].img fastboot reboot
  13. hello @26.albertsilva@gmail.com, what's the edp you're using? it might be that the edp you're using is not ported/ supported.
  14. hello @Dr.DDC, there are a few possible reasons: 1. the system on module is loosely inserted -- please check if the google som is inserted properly 2. hardware issue (i'll need more information to check if it's the case) the fastest way to debug is to use an uart serial dongle/ putty and see if there's output for boot process: ground: pin6, tx: pin8, rx: pin10; buad rate: 115200 [tinker edge t]: dip switches set to emmc mode: (on, off, off, off), short the power pins how i flash tinker edge t: 1. connect tinker edge t with an hdmi monitor & a windows pc 2. [tinker edge t] short the power pins until the fan starts turning; you should see the desktop on the hdmi monitor once the fan stops 3. [tinker edge t] click the terminal icon on the top left and use the command to reboot bootloader sudo reboot-bootloader 4. [tinker edge t] tinker edge t is now stops at bootloader; [windows pc] tinker edge t should be recognised as asus android bootloader interface; click flash.cmd to flash the board 5. [tinker edge t] wait till the flashing is finished and reboot the board
  15. hello @Dr.DDC, if tinker edge t is not recognised by your windows pc then it's likely some driver dependency issue, i have uploaded the drivers and tools i've used here: https://www.asuswebstorage.com/navigate/a/#/s/3EC53A71A9C74D6094A777DB351D51904
  16. hello @26.albertsilva@gmail.com, lvds was bridged and converted from mipi dsi, therefore only dsi logs present if you're using lvds to enable lvds, please modify the /boot/config.txt sudo vi /boot/config.txt overlay=mipi2lvds2_the lvds panel you are using save & reboot for instance, if you're using auo 21.5" lvds panel, then the overlay line in the config.txt should be: overlay=mipi2lvds2_G215HAN01 there are 2 lvds that are supported on tinker board 3n so far: Tinker Board 3N QVL
  17. hello @26.albertsilva@gmail.com, the uart serial console is enabled by default. which pins did you connect to?
  18. hello @Ethan_Lin, there was a small mistake i made in the previous post, the dtbo should be pushed into /dtoverlay/overlays instead of /dtoverlay adb push i2c6_100K.dtbo config.txt /dtoverlay/overlays
  19. hello @SkyDragon, what modifications did you make before the issue occurred? perhaps we can try to reproduce the issue looks like the uboot is unable to load the boot partitions and gets stuck in uboot shell. if the changes in boot.scr make the partition unrecognizible, i'd suggest to re-flash tinker edge t. please use a sd card to flash, and adjust the dip switches to 'on, off, on, on' so the board can boot from sd. keep in mind that you'll need to short the power pins to boot tinker edge t whether it's boot from sd or emmc
  20. hello @Dr.DDC, was the board completely dead? here's a little tutorial on how to boot the board: Asus Tinker Edge T - First Boot Tutorial - YouTube
  21. hello @Ethan_Lin, i suspect that the overlay didn't come effectvie. will it be possible for us to have console logs for checking?
  22. hello @Ethan_Lin, which version of android 11 os are you using?
  23. hello @Ethan_Lin, you can ls to check whether clock-frequency is there or not with ls: to check if the changes have been applied: if you have peripherals, you can connect them and test out different speed settings using mraa library: Developer Guide · TinkerBoard/TinkerBoard Wiki (github.com)
  24. hello @Ethan_Lin, the files were the 10k.dtbo, my mistake. i've put the correct files here: https://www.asuswebstorage.com/navigate/a/#/s/258BFBD7E61045C9BECB7DA044378A844 and then use i2cspeed.sh to verify: adb push i2cspeed.sh sdcard/ adb root adb shell sh sdcard/i2cspeed.sh
×
×
  • Create New...