tooz

hello @Stefan A., the changes made in monitor settings will be kept (even if you reboot the device), unless the device is connected to other panels with different resolution. here's another alternative to configure, but it should be done right after flashing, if the device's resolution has been changed and saved in monitor settings, then this method might not work: in /etc/X11/xorg.conf.d/20-modesetting.conf please added the highlighted lines; once the .conf is modified, the changes will come in effect after reboot. Section "Screen" Identifier "Default Screen" Device "Rockchip Graphics" Monitor "Default Monitor" SubSection "Display" Depth 24 Modes "1920x1080" EndSubSection EndSection

hello @Stefan A., by fullhd, do you mean 'hdmi output resolution'? if so, you can change it in monitor settings in the tinker os

hello @peterpan1207, is this the official dsi panel of raspberry pi? ( https://www.raspberrypi.com.tw/8826/470/ ) if it's not the official rpi panel, there's also chance that the panel is not compatible with tinker board-- also for mipi dsi panels usually an external 5v power supply is required, from the pic looks like the power is connected to the fan? have you tried if the panel works for other devices?

hello @Remontoir, yes, tinkerboard/ tinkerboard s only supports opengl es-- which test are you running? perhaps we can run it our side and see what comes out.

hello @Chridster1, my colleague has looked into it and suggets to use the right compiler--using the prebuilt compiler on ubuntu may be the easiest way to do so; the build enviornment is crucial for compiliing. all the bsp source code's uploaded onto Tinker Board 2 (github.com) including buildroot TinkerBoard2/buildroot (github.com)

hello @JasonS, if you're using debian os, you can modify /etc/init.d/adbd.sh to ultilize the usb gadget

hello @Sanko_bs (cc @Tinker_HWEE) from software perspective, if the device is not under heavy loads(running multiple complicated applications/ tasks/ processes), the cpu temperature shall be normal, we'd suggest to do a re-flashing if you'd like to debug and find the rootcause of cpu overheating.

hello @peterkwon, please refer to the instructions on google coral: https://coral.ai/docs/m2/get-started/#2a-on-linux https://coral.ai/docs/edgetpu/tflite-cpp/#inferencing-example for now only python and c++ are supported

hello @ManyanJin10, that's great to know, thanks for the update.

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 @Junhyuk Oh, please revert these two changes from kernel: a11f35719c4d logo: change linux kernel logo by ADC request. 95e5b2643333 logo: Show linux logo and dump kernel log to display during system booting.

hello @ManyanJin10, you can try to modify this line to: src = "gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=1920,height=1080,framerate=30/1 ! videoconvert ! appsink"

hello @Junhyuk Oh, did you reboot the device after applying the patch?

hello @Junhyuk Oh, this patch and be applied for changing/removing logo: https://www.asuswebstorage.com/navigate/a/#/s/3CC2A30D765146908D2D7A8CC8BB99C84 if you'd like to change the boot as well, here's a little guide on how to do so: https://github.com/TinkerBoard/TinkerBoard/wiki/Developer-Guide#tinker-board-on-debian-os

hello @Chridster1, gcc: error: unrecognized command line option '-mlittle-endian'; did you mean '-fconvert=little-endian'? ↑ this gcc error was cause by false cross compiler settings; the openSuSE Leap 15.3 compiler can't be used in this case. please check the cross compiler directory -- after the gcc-aarch64-linux-gnu packages install, you'll see a bunch of aarch64-linux-gnu files under /usr/bin/ if not, you will have to find the right directory and set in “make ARCH=arm64 rk3399-tinker_board_2.img CROSS_COMPILE=aarch64-linux-gnu- -j8” CROSS_COMPILE

hello @ManyanJin10, which debian os are you using? if you're using one of the official releases from tinker-board.asus.com may i know the version? thank you.

hello @Adam, we've tried to reproduce the issue with debian 10 v.2.0.3 and v.2.0.4 but it didn't occur in both os versions. is the serial frequency set to 115200? if so, perhaps there's something happened during the flash, or the sigal of cable isn't stable. we'd suggest to 1. reflash the image and/or 2. use another cable and try if it fixes the problem.

hello @Chridster1, unfortunately we can't add tinker board 2s to buildroot as it's developed by another company. have you tried with the kernel 4.19 one? $ repo init -u https://github.com/TinkerBoard2/manifest.git -b linux4.19-rk3399-debian10 $ repo sync we're not able to reproduce the issue, may we know what your build environment is?

hello @kenta, the default sensor settings of IMX219 is 1920x1080, the cmds below can be used to adjust IMX219 sensor settings to 3280x2464: media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":0[fmt:SRGGB10_1X10/3280x2464]' media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":0[crop:(0,0)/3280x2464]' media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":2[fmt:YUYV8_2X8/3280x2464]' media-ctl -d /dev/media0 --set-v4l2 '"rkisp1-isp-subdev":2[crop:(0,0)/3280x2464]' media-ctl -d /dev/media0 --set-v4l2 '"m00_b_imx219 1-0010":0[fmt:SRGGB10_1X10/3280x2464]' v4l2-ctl -d /dev/video0 --set-fmt-video=width=3280,height=2464,pixelformat=NV12 --set-crop=top=0,left=0,width=3280,height=2464 And, I cannot find the Test_tool directory. Could you give any information about the Capture_Test.sh the script can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/5B06BC29115E4004A181738E5E0F909E4

hello @R_Pekov, looks like there's a build conflict from the log, you will have to remove 241-7~deb10u8, and then reinstall libudev1 (= 241-7~deb10u7) .

fyr: https://github.com/TinkerBoard2/kernel/issues/8

hello @Chridster1, looks like cd kernel didn't get excuted, hence why the error. you have to change directory to whereveer the kernel is located. when you cd to the directory where the source code is located, you can use the command ls kernel for checking: kernel$ ls android build.config.goldfish.arm certs firmware Kconfig Makefile scripts virt arch build.config.goldfish.arm64 COPYING fs kernel mm security backported-features build.config.goldfish.mips CREDITS include lib net sound block build.config.goldfish.mips64 crypto init logo.bmp README tools build.config.cuttlefish.aarch64 build.config.goldfish.x86 Documentation ipc logo_kernel.bmp REPORTING-BUGS usr build.config.cuttlefish.x86_64 build.config.goldfish.x86_64 drivers Kbuild MAINTAINERS samples verity_dev_keys.x509 result should be files listed on https://github.com/TinkerBoard2/buildroot then you can continue the following: Installing the build tools $ sudo apt-get install git-core gitk git-gui gcc-arm-linux-gnueabihf device-tree-compiler gcc-aarch64-linux-gnu mtools parted libssl-dev Build Kernel $ cd [source code] $ make ARCH=arm64 tinker2_defconfig $ make ARCH=arm64 rk3399-tinker_board_2.img CROSS_COMPILE=aarch64-linux-gnu- -j8 Also I found https://github.com/TinkerBoard/buildroot would this work for the Tinkerboard 2S? No, this is for RK3288 based (Tinker Board, Tinker Board 2S) which is different from RK3399 based Tinker Board 2S, the defconfig's different

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.

hello @Alvin Kwek, sorry for delayed reply, perhaps you can use balenaetcher to do flashing on multiple boards: https://www.balena.io/etcher/

hello @Chridster1, you certainly can, please check the the docs folder in source code, there's also information available on github wiki for tinker board 2s: https://github.com/TinkerBoard/TinkerBoard/wiki/Developer-Guide