Search the Community

Hi all, I'm deploying Tinker Board 3S units in an embedded product where physical debug interfaces need to be locked down for security. I want to completely disable the debug UART console (3-pin header, ttyFIQ0 @ 1500000 baud) so that no shell access or boot log output is possible through the serial port. What I've considered so far: - Removing "console=ttyFIQ0,1500000" from the kernel command line - Masking getty@ttyFIQ0.service - Disabling the UART node in the device tree (status = "disabled") My questions: 1. Is removing the kernel console parameter + masking getty sufficient, or does U-Boot itself also output to this UART before the kernel takes over? If so, is there a way to silence U-Boot output as well? 2. Is there a recommended device tree overlay approach to fully disable this UART on the RK3566? 3. Are there any side effects to disabling this UART (e.g., boot failures, watchdog issues)? Environment: - TinkerOS Debian on eMMC - Headless deployment, SSH-only access over Ethernet Any guidance or experience with production hardening on TB3S would be appreciated. Thanks!

Hello, I use Tinker 3S with latest Tinker OS. I connected a high-power USB 3 camera module (800 mA). At the same time, my Tinker board is periodically accessed over Wi-Fi by a web client (it runs a web server). When I cut the power to the Wi-Fi router, the USB camera capture suddenly starts failing in bursts. This is reproducible. If I disable Wi-Fi power saving mode (see attached code), the problem disappears. echo "options 8822ce rtw_power_mgnt=0 rtw_ips_mode=0 rtw_lps_level=0 rtw_low_power=0" \ | sudo tee /etc/modprobe.d/8822ce.conf However, I would like to avoid disabling power saving mode if possible. What do you think is happening here?