tooz

hello @jovanpn, For Tinker Board 2S, please use the latest version (2.0.1) . We've tested the commands and it works fine. Tinker Board (asus.com)

hello @dlphmn, what image are you using? if you download the official release of debian 10 image from our site it should have solved the issue https://tinker-board.asus.com/download-list.html?product=tinker-board-2s

hello @collin wu, open /boot/config.txt and change #intf:spi1=off to intf:spi1=on ("#" should be taken out too)

hello @Kris007, if you're using a non-tinker os, you will not be able to modify the config.txt.for 40 pin function(unless you modified dts by yourself). However, if you've only changed the rootfs and the kernel is still the same, you may be able to find the file of "config.txt" and change the settings.

hello @Dima.Sh, Based on Android design, the userdata partition will be erased the when booting from sdcard if you choose to factory reset. If you use the same sdcard to boot another board, the userdata will be empty as factory reset was performed previously. Is it okay to share your user scenario so we can specify the question? Thank you.

hello @serial115200, the commmand is used for boot.img update. sudo dd if=boot.img of=/dev/mmcblk1p4 status=progress && sync you'll have to build your own .img file if you'd like to resize the partition.

hello @Weby, The design of Tinker Edge T doesn't allow i2c to be disabled. Tinker Edge T's USB and i2c2 shared the same channel, once i2c is disabled, the user will not be able to have USB working.

hello @serial115200, please try use the command below to update boot.img sudo dd if=boot.img of=/dev/mmcblk1p4 status=progress && sync

hello @q4a, it can be found here: TinkerBoard2-Android/manifest (github.com)

Hello @Kubo the VID shows that your board has had a normal boot, please connect the board to the PC with a typeC cable, and use the command to enter ums mode #reboot ums please be aware that the board will boot normally if the PC connection is not detected

hello @Kubo could you provide the PID & VID of the driver? (as the picture shown below)

hello @Kubo, are you able to boot up the board with the current image? did you download the .img from the official website? Tinker Board (asus.com) here's a pic that shows when the board is on UMS mode(board connected to PC with USB cable, no jumper), this way you should be able to flash the board with a flash tool

hello @Kubo please try to connect the board with a PC and power on to boot into UMS mode, so then you can use flash tools such as balenaEtcher to flash the board

hello @serene, the kernel file has to be in the same directory with prebuilts. if your files are located in different directories then you may have problems because of the wrong gcc. /TinkerBoard2$ ls kernel prebuilts rkbin u-boot those four are in the same directory

hello @Hitchcock, some questions and possible solution for the issue: q1. is the resolution of the 1st pic 1920x1080? q2 . has the DPI been modified? if so, please modify the resolution to 1024x768(settings-> display-> HDMI-> resolution) and reboot; you can also try to flash the board to android 11 and see if it improves q3. is the monitor connected to the HDMI port? or is it connected to a HDMI-DSUSB dongle? also, please use the commands in adb shell below to see if it works: su setprop persist.vendor.overscan.main "overscan 100,100,100,100" stop start

hello @serene, please provide the complete build log, we will have a look

hello @Hitchcock could you send us a picture of the display when the issue happened? what model is the monitor? did you only connect the board to hdmi, or did you connect it to both dsmi and dsi at the same time? also, did you reboot the board when you modified the resolution?

hello @serene please try the command: sudo apt-get install liblz4-tool it shall install the patches needed

hello @serene, what's the build environment? you'll need x86_64 environment in order to build gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu use the command lscpu and you will see the architecture: x86_64C Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit

hello @serene, it can be found here: https://github.com/TinkerBoard2-Android/device_asus_tinker_board_2

hello @serene some commands can be found in device/rockchip/tinker_board_2/build.sh you will need the rkbin to build it successfully. building steps are as follows u-boot cd u-boot ./make.sh tinker2 kernel cd kernel make ARCH=arm64 tinker2_defconfig make ARCH=arm64 rk3399-tinker_board_2.img -j8

hello @doggedly, the reason why the scripts weren't excuted is because it requires Init-launched services in Android 10: Writing SELinux Policy | Android Open Source Project you will have to build your image in order to have SELinux Access: TinkerBoard2-Android/manifest (github.com)

hello @haxboard, do you have logs or screenshots of the issue you're facing?

hello @haxboard, are all your devices the same model(tinker board s)? did this occur only after updating to android v14.4.0.14, or did it happen on other versions as well? also, could you re-attach the logs as it's not shown on the forum, you can also inbox me the file and we can have a look

hello @doggedly, it should be the same as the first gen (tinker baord/ tinker board s). may i know the steps of how you run the executable on boot?