I am using a Tinker Board 3S with TinkerOS (Debian 11 V1.0.7).
For security reasons, I want to prevent ADB from automatically starting when a USB device is connected, since this device will be used to run a custom application in a production environment.

At the moment, I am disabling ADB by manually removing the ADB function from the USB gadget configuration:

sudo rm /sys/kernel/config/usb_gadget/asus/configs/b.1/f-ffs.adb
sudo rmdir /sys/kernel/config/usb_gadget/asus/functions/ffs.adb

# /usr/bin/usbdevice
adb_prepare()
{
        # usb_mount adb /dev/usb-ffs/adb -o uid=2000,gid=2000 -t functionfs
        # usb_start_daemon /usr/bin/adbd
        # usb_wait_files -m /dev/usb-ffs/adb
}

adb_stop()
{
        # usb_stop_daemon /usr/bin/adbd
}

Any advice would be greatly appreciated.

I am trying to connect an UART device (MCU)  to a TinkerBoard3S.
I have confirmed that UART1, 4, and 9 work correctly, but it does not work with UART0.
Is there any difference between UART0 and UART1,4,9?
I have checked the performance with baudrates of 9600, 115200.

I assume that UART0 has CTS and RTS pins.
Therefore, I have set the CTS and RTS pins to not be used in the software.
I attached sample python code with pyserial module.

>>> import serial
>>> ser = serial.Serial("/dev/ttyS0", 9600, timeout=1)
>>> ser.rtscts=False
>>> ser.dsrdtr=False
>>> ser.rts=False
>>> ser.dtr=False

Are there any other necessary settings?

Currently, I am using the Tinkerboard2S for its USB OTG function. In the future, when this model becomes EOL, I will need to choose a device that has OTG function.

I am new in Asus arena, I am testing an tinker3s board.

I have much more experience in Rpi, ESP32, Arduino, microcontrolers, STM32 ...

I would like to harden an Tinker3s like I do with other boards. I succeed to download debian 11 on SDCard and eMMC.

update and upgrade have been performed.

-----------------------------------------------------------------------------------------

hostnamectl
  Static hostname: xxxxxxxxxxx
  Icon name: computer
  Machine ID: 455600600d8c4f4fd26c8dbc67221164
  Boot ID: f4a9d2397ba347a8a7030b8c89e54df4
  Operating System: Debian GNU/Linux 11 (bullseye)
  Kernel: Linux 5.10.209
  Architecture: arm64

-----------------------------------------------------------------------------------------

Looking at the forum I did not found expected informations, here are few questions :

• Is there some online command to be used to prevent from using GUI tinker-config tool ?
• Is it possible to download light OS with NO desktop ?
• How should be configured resolv.conf file ? Is it updated at each board reboot ?
• How should be set DNS configuration ?
• How should be set NTP configuration ? set-ntp does not work like if config files are missing. I set date & time manually.
• How should be configured wire network (configuration file and interfaces) ?
• Where is located the default wired network configuration file and associates certificates ?
• How should be configured ROOTCA, IntermediateCA and user certificates used for enterprise wifi vlan connexion ? (I set wpa_supplicant and certificates with no sucessfull connexion)

Thanks in advance for your help

I am currently trying to check GPIO control with TinkerBoard3S.

・Environment
　TinkerBoard3S
    OS：Tinker Board 3 Debian 11 (kernel 5.10) V.1.0.1(The results were the same with 1.0.4)

I tried to check the LED blinking with pin108 using the following sample code, but it doesn't work.(there is no import error)

import ASUS.GPIO as GPIO
import time
 
GPIO.setmode(GPIO.ASUS)
GPIO.setwarnings(False)
GPIO.setup(108, GPIO.OUT)
while True:
  GPIO.output(108, GPIO.HIGH)
  time.sleep(0.2);
  GPIO.output(108, GPIO.LOW)
  time.sleep(0.2);

The result of "gpio readall" before executing sample code is bellow, but after executing the 108 pin  mode remained IN.

Also, to check UART communication, I enabled UART communication from tinker-config, but there was no change in "gpio readall" results.

Is there anything else I need to do regarding the GPIO control?　

linaro@linaro-alip:~$ gpio readall
 +-----+-----+---------+------+---+--Tinker--+---+------+---------+-----+-----+
 | CPU | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | CPU |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
 |     |     | GPIO8A4 |      |   |  3 || 4  | IN   | 5v      | 146 | 146 |
 | 105 | 105 | GPIO8A5 |   IN |  5 || 6  | IN   | 0v      | 147 | 147 |
 | 106 | 106 | GPIO0C1 |   IN |  7 || 8  | IN   | GPIO5B1 | 148 | 148 |
 | 107 | 107 |      0v |   IN |  9 || 10 | IN   | GPIO5B0 | 149 | 149 |
 | 108 | 108 | GPIO5B4 |   IN | 11 || 12 | IN   | GPIO6A0 | 150 | 150 |
 |     |     | GPIO5B6 |      |   | 13 || 14 |   |      | 0v      |     |     |
 |     |     | GPIO5B7 |      |   | 15 || 16 |   |      | GPIO5B2 |     |     |
 |     |     |    3.3v |      |   | 17 || 18 |   |      | GPIO5B3 |     |     |
 |     |     | GPIO8B1 |      |   | 19 || 20 |   |      | 0v      |     |     |
 |     |     | GPIO8B0 |      |   | 21 || 22 |   |      | GPIO5C3 |     |     |
 |     |     | GPIO8A6 |      |   | 23 || 24 |   |      | GPIO8A7 |     |     |
 |     |     |      0v |      |   | 25 || 26 |   |      | GPIO8A3 |     |     |
 |     |     | GPIO7C1 |      |   | 27 || 28 |   |      | GPIO7C2 |     |     |
 |     |     | GPIO5B5 |      |   | 29 || 30 |   |      | 0v      |     |     |
 |     |     | GPIO5C0 |      |   | 31 || 32 |   |      | GPIO7C7 |     |     |
 |     |     | GPIO7C6 |      |   | 33 || 34 |   |      | 0v      |     |     |
 |     |     | GPIO6A1 |      |   | 35 || 36 |   |      | GPIO7A7 |     |     |
 |     |     | GPIO7B0 |      |   | 37 || 38 |   |      | GPIO6A3 |     |     |
 |     |     |      0v |      |   | 39 || 40 |   |      | GPIO6A4 |     |     |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 | CPU | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | CPU |
 +-----+-----+---------+------+---+--Tinker--+---+------+---------+-----+-----+

When will the documentation for this product be available on the official website?

I am trying to burn DebianOS into TinkerBoard3S(not Tinker3).

I connected the Tinker to my Windows Laptop(Windows11) with a USB-MicroB cable as described in the instructions in this manual(https://tinker-board.asus.com/download/E22692_Tinker_Board_3_UM_WEB.pdf),

but the Laptop does not recognize it.(Also, it is not recognized as a target by balenaEtcher).

・Current Status
The Red LED on the back is on. When I connected the 3S via USB to Laptop, the device is listed as “unknown device” in the device manager of the windows Laptop.

I tried the following, but the results were the same.
・Replace the USB cable.
・Change the USB port(of laptop)
・Connecting to other windows laptop
・Update and Reboot Windows.

Is there anything else I need to do regarding the setup?

Most efficient for existing csi users

Please give me an alternative.