tooz

hello @JFB, we've tested lte modules with both hat + mpcie interface & usb dongle +m.2 interface and confirm they both work. however please notice that not all lte modules are supported, here are the modules enabled on tinker board 2s for your reference: Vendor Product VID:PID Firmware Quectel EG25-G 2C7C:0125 EG25GGBR07A08M2G_01.003.01.003 EG21-G 2C7C:0121 EG21GGBR07A11M1G_01.002.01.002 EC25-AU 2C7C:0125 EC25AUFAR06A01M4G EC25-E 2C7C:0125 EC25EFAR06A08M4G_01.007.01.007 EC25-J 2C7C:0125 EC25JFAR06A05M4G_01.008.01.008 EC25-AF 2C7C:0125 EC25AFFDR07A10M4G_01.004.01.004 BG96 2C7C:0296 BG96MAR04A04M1G_01.005.01.005 EM06-E 2C7C:0306 EM06ELAR03A08M4G other lte modules that are not listed may or may not work on tinker board 2s, it's just that the list are the modules we actually got & tested

hello @lloydhussell, most of the touch drivers work on tinker board 2s if it's usb interface; the 240hz would be the tricky part since it depnds on the cpu

hello @ChaJH, no, just checking the environment this panel's resolution is 1600x600, which is supported on tinker board 2s, but it might be blocked by resolution_white.xml please use commands below to remove resolution white adb root adb remount adb shell rm -rf /system/usr/share/resolution_white.xml and then reboot tinker board 2s the expected result is the 1600x600 resolution is supported on tinker board 2s

hello @ChaJH, are you using android 12 os ( Tinker Board 2 /2S Android 12 V3.0.2 ) or android 11?

hello @rugfk, the os download page of tinker edge r: https://tinker-board.asus.com/download-list.html?product=tinker-edge-r

hello @shizimi, these are the logs for device management service, your tinker board r2.0 shall stop printing related logs once dmprovider.service is stopped.

hello @sanma, i've uploaded a folder named 'audio patches for tinker board 2s', please apply the three patches in the folder to enable hdmi audio output: https://www.asuswebstorage.com/navigate/a/#/s/7AC916CB836740359132FEDCC45B06194

tinkerboard　2s　の　gpio　40pin　セッティング説明はこちらです： Tinker Board 2 & 2S · TinkerBoard/TinkerBoard Wiki (github.com)

hello @Alexandre Baiocco, the new release (kernel 5.10, debian 11) of tinker board 3n supports asus.gpio by default: Tinker Board 3N Debian 11 (Kernel 5.10) V1.0.17

hello @Alexandre Baiocco, the documentation for asus gpio (tinker board 3n) can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/5D3F8EFB2B2D4EDD96C4AF57334C5B434

こんにちは　@jun0129 この製品のスペックがありますか？

hello @Alexandre Baiocco, the asus.gpio for tinker board 3n can be downloaded here: https://www.asuswebstorage.com/navigate/a/#/s/C48903C16D79411E96C4FB3DB82621014 it'll be supported by default in our next os release

hello @Alexandre Baiocco, i'll check with my team and see if i can get you the sources for gpio

hello @jovanpn, thanks for the information, please give a try on boot.2.img: https://www.asuswebstorage.com/navigate/a/#/s/9A55AA4C9F5E4B878AA751052AC080CC4 this boot.img contains the nft configurations we're planning to enable for the next release

hello @Bram, if you're using a windows pc and see these popping up just ignore -- these are the partitions divided in the storage i use balenaetcher: https://etcher.balena.io/ there's a 'clone drive' option that allows users to clone sd cards/ usb drives win32diskimger should work too

hello @jovanpn, i've compiled a beta boot.img (file name boot.1.img) with a couple of more configs enabled, please give it a try and let me know https://www.asuswebstorage.com/navigate/a/#/s/11FC555055EA4D0288030C09125440F24 to replace the boot.img: check the partition orders from the parameter.txt in the v.3.0.11 image file, in this case the boot.img is the 4th CMDLINE: mtdparts=rk29xxnand:0x00002000@0x00004000(uboot),0x00002000@0x00006000(trust),0x00002000@0x00008000(misc),0x00020000@0x0000a000(boot),0x00040000@0x0002a000(recovery),0x00010000@0x0006a000(backup),0x00020000@0x0007a000(userdata),-@0x0009a000(rootfs:grow) uuid:rootfs=614e0000-0000-4b53-8000-1d28000054a9 on tinker board 2s: sudo lsblk replace the fourth partition (boot.img) with boot.1.img sudo dd bs=4M if=/path/to/boot.1.img of=/dev/mmcblk1p4 status=progress && sync reboot and check if the changes work

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

hello @jovanpn, i'll check and see if we've missed out something in the defconfig, if so this will be fixed in the next release.

hello @jovanpn, here's a tutorial on how to set the firewall on debian 11 that might be helpful: How To Set Up a Firewall with UFW on Debian 11 | DigitalOcean

hello @MarciS, what are the commands you used for downloading source codes/ compiling? are you using the codebase from: https://github.com/TinkerBoard2-Android/kernel/tree/android11-rk3399/drivers/media/i2c/cam_sensor ? cam_imx219.c, cam_ov5647.c, cam_sensor_code.c are only available in android 11

hello @grv2025, to avoid entering ums mode on boot, please modify /boot/config.txt, in line 25, change conf:auto_ums=on to conf:auto_ums=off sudo vi /boot/config.txt conf:auto_ums=off save and reboot

hello @grv2025, i've tried using debian 11 beta v.3.0.13 to reproduce the issue: tinker board 2s (boot from sd card) connected to an usb mouse, an usb keyboard, and type c port connected to a pc result: tinker board 2s starts up and the desktop appears within a few seconds. on my windows pc: tinker board 2s is recognised as rk33xx device https://i.imgur.com/XMyCMLZ.mp4 what's the os version you're using? is there any other peripherals connected to tinker board 2s? what's your setup?

hello @Kuzma30, panels that are not on the qualified vendor list need extra support for driver porting etc. i'd suggest to choose the ones from the qvl: https://tinker-board.asus.com/download/Tinker_Board_3N_QVL.pdf

hello @ihatemundays, i can't reproduce the issue on my side (tinker board rev.1.2, debian os) the audio works just fine. we'll need a bit more details to narrow down the issue -- 1. os version 2. occurance 3. does it happen on specific timing -- i.e. on boot/ when playing certain type of audio ... 4. commands that you use it might not be the audio firmware problem as alc4040 and alc4030u are different; they also have different firmware upgrade process flows. alc4030u uses one time programmable memory and alc4040 doesn't

hello @ChaJH, got it, thanks for the update. the mraa library will be added in the next android 12 os release too