Jump to content
New Wiki - User & Developer Guide ×

All Activity

This stream auto-updates     

  1. Earlier
  2. Sean Lai Sean Lai joined the community
  3. Igor V. Timofeev Igor V. Timofeev changed their profile photo
  4. sonyan11
    @Frank_Chiang Thank you so much for your kind response! Best.
  5. Frank_Chiang
    Hi Sonyan, In general, we don’t recommend disabling the UART log, since it removes an important recovery and debugging channel. If you still need to disable it, please try to disable the status of /fiq-debugger in device tree. This will stop console output during the kernel and system stages. For U-Boot, we recommend using CONFIG_SILENT_CONSOLE to silence its output. Thank you.
  6. Kyawgyi Kyawgyi changed their profile photo
  7. sonyan11 started following How to fully disable debug UART console for production deployment?
  8. sonyan11
    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!
  9. wpk2 wpk2 joined the community
  10. Chris_
    Update. Hi Owen Chen, The original dts file is the file for mipi2lvds2_G156HAN02.dts , I've tweaked the timings a bit. I found the problem: the LVDS power supply from the ThinkBoard (3.3V) drops below 3.1V under panel load. The panel requires 3.15V to 3.6V, which is causing the image distortion. The panel works perfectly with an external power supply. Do you know the maximum current the ThinkBoard can deliver at its LVDS output? Or is there a solution for this?
  11. Owen Chen
    Hi Chris, Thank you for the information. You mentioned using an overlay from the /boot/overlays/ folder. Could you let us know where this specific .dts file originated from? We are asking because we actually do not include this file in our official release, and we do not support the G156HCE-L01 panel on our Debian system.
  12. Chris_
    Thanks for the reply, I got Debian from https://tinker-board.asus.com/download.html#os Here is the screenshot of the command output:
  13. Owen Chen started following LVDS/Panel problems with tinker board 3N Lite
  14. Owen Chen
    Hi Chris, Thank you for choosing our product. To help us better analyze the situation, could you please let us know which operating system and version you are currently using? For example, you can usually retrieve this information by running the following commands in your terminal: $cat /etc/version $cat /etc/os-release We look forward to your reply so we can assist you further.
  15. Owen Chen Owen Chen joined the community
  16. Chris_ started following LVDS/Panel problems with tinker board 3N Lite
  17. Chris_
    Hallo, I have a ThinkBoard 3N Lite and want to control a G156HCE-L01 panel via LVDS. I used one of the existing overlays from the /boot/overlays/ folder and tried to adapt it to my panel. After several attempts, I'm still having the problem that simple images (login screen and normal desktop) work. However, when I have a window or the black terminal on the screen, the panel starts flickering, or black/colored stripes appear. I think there might be something wrong with the timing values or LVDS settings. What is worng with the LVDS settings? Can anyone help me? mipi2lvds2_G156HCE_L01.dts
  18. Chris_ Chris_ joined the community
  19. abductedgnomez@gmail.com abductedgnomez@gmail.com joined the community
  20. Nathan started following SPI Issue - Tinker 2S
  21. Nathan
    We are currently working on Tinker 2S board for one of our project. We have the requirement of using both SPI buses of the Tinker 2S board, but currently we are facing an issue with the SPI5 bus. Scenario 1 : We connected MOSI and MISO in a loop and enabled loop back, it worked with a normal wire length but after increasing the wire length it stopped working. We tried the same scenario with the SPI1 bus and it was working without any issue. But we used twisted pair wire with the same increased length on the SPI5 bus and it was working fine that time. Scenario 2 : We connected a SPI slave to SPI1 bus and it worked without any issue, but connecting the same slave to SPI5 and it was not working. We enabled SPI5 from OS and all connections was as per the pin out diagram itself. What may be the issue that SPI5 bus is not working properly?
  22. AvR started following Spi5 Not working
  23. AvR

    Spi5 Not working

    AvR posted a topic in Hardware

    I am using the Tinker 2S board and am unable to use SPI5, as it always returns junk values. However, the same SPI slave works correctly with SPI1. What could be the issue?
  24. AvR AvR joined the community
  25. senpaistream senpaistream joined the community
  26. jkroivas jkroivas joined the community
  27. Backlink Service Backlink Service joined the community
  28. Toru
    Hi TzuWen, Thank you for the information. I disabled usbdevice.service as you suggested, and I have confirmed that the service was successfully stopped. This resolved my issue. Thanks again for your support. Best regards,
  29. duofilm duofilm changed their profile photo
  30. rightcheckin5 rightcheckin5 joined the community
  31. TzuWen_Chang
    Hi Toru, You can stop the usbdevice.service directly. Please use the following command: sudo systemctl disable usbdevice.service BRs, TzuWen
  32. jovanpn
    To people who is having same issue, I found possible solution for this version of TinkerOS. The problem was that dhcpcd5 software is accessing network interfaces before udev tries to set Predictable Names for network interfaces which actually blocks udev executing the change. So the possible solution is to delay starting dhcpcd service until udev completes its task. This is why network interfaces get their predictable names correctly when dhcpcd is disabled to start at boot. Possible solution includes creating a file at location: /etc/systemd/system/dhcpcd.service.d/override.conf with further contents: [Unit] After=network-online.target Wants=network-online.target After this file is created, dhcpcd service can be enabled to start at boot.
  33. Toru started following [Tinker Board 3/3S Debian 11 V1.0.7 OS] How to Disable ADB
  34. Toru
    Hello, I would like to ask how to properly disable ADB on TinkerOS. 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 I also commented out the ADB-related sections inside /usr/bin/usbdevice (lines 260–272): # /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 } Are there any concerns or drawbacks with disabling ADB in this way? Is there an official or recommended method to disable ADB in TinkerOS? Any advice would be greatly appreciated.
  35. dingxt started following GPIO lib for Tinkerboard 3
  36. dingxt
    Hi Anyone can advise how to install python3-ASUS.gpio. Now error is unable to locate package
  37. felix_vu
    I have mistaken when downloading old source code. After trying with latest source code, Audio works normally now. Please ignore. Thank you !
  38. felix_vu started following rockchiprk809 sound card can not probe
  39. felix_vu
    Hi everyone ! I have tried to build Debian for Tinker Board 3s by following the guide at https://github.com/TinkerBoard/TinkerBoard/wiki/Tinker-Board-3-&-3S After building and flashing image, Debian can boots up and most of features function properly. But I can not play audio via 3.5 mm port: Some debug information: root@linaro-alip:/# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiphdmi [rockchip,hdmi], device 0: fe400000.i2s-i2s-hifi i2s-hifi-0 [fe400000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 root@linaro-alip:/# dmesg | grep sound [ 4.011331] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.013325] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.015123] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.621126] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.623107] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.625071] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.637447] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.639581] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.641652] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.649570] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.653490] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.656981] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.738595] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.740769] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.744236] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.751415] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.754619] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.758382] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 4.833968] rk-multicodecs rk809-sound: Failed to get ADC channel [ 4.836622] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 4.839072] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 5.043269] rk-multicodecs rk809-sound: Failed to get ADC channel [ 5.045282] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 5.048308] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 5.668399] rk-multicodecs rk809-sound: Failed to get ADC channel [ 5.670634] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 5.672530] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 7.484887] rk-multicodecs rk809-sound: Failed to get ADC channel [ 7.516061] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 7.516070] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 7.555597] rk-multicodecs rk809-sound: Failed to get ADC channel [ 7.555795] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 7.555798] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 7.639002] rk-multicodecs rk809-sound: Failed to get ADC channel [ 7.761508] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 7.763343] rk-multicodecs rk809-sound: Audio routing invalid/unspecified [ 9.902650] rk-multicodecs rk809-sound: Failed to get ADC channel [ 9.904733] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 9.906440] rk-multicodecs rk809-sound: Audio routing invalid/unspecified When try to flash official image from https://tinker-board.asus.com/download-list.html?product=tinker-board-3, I can play audio via 3.5 port normally. Did any one face the same issue ? Please help me !!!
  40. denchakapon denchakapon changed their profile photo
  41. cursorman
    That’s an impressive milestone for the Armbian team — they’ve managed to balance performance improvements with community-driven innovation, which isn’t easy in open-source projects of this scale.
  42. quenchjian started following APP Permission not remembered
  43. quenchjian
    Hi, I follow the wiki to flash Android OS to Tinkerboard 3S devices and then install my app that need manage storage permission, but every time I reboot the device, the manage storage permission is revoked. Then I check the install app permission of "Files" app, the same thing happens. Image flashed: Tinker Board 3/3S Android 14 (kernel 6.1) V.1.0.9 Reproduce steps: Setting -> Apps -> Files -> Permission -> allow install other app permission. Reboot the device. Check permission again, you can see the install permission is revoked. BTW, I also tried flash latest image Tinker Board 3/3S Android 14 (kernel 6.1) V.1.0.19, but it also happens.
  44. tooz
    hello @LucD, sorry to hear that. could you provide a screencap of the failure so we can further investigate the issue?
  45. Alistair Low
    Replying to this old thread because I had the same problem this week on the Tinker Board (not S) R2.0: I tried both of the Android 11 images with the same issue as @AJofre - after running adb reboot-bootloader the logo screen appears but the device gets stuck on that screen and the device is not visible when I run fastboot devices Tinker Board R2.0 /Tinker Board S R2.0 Android 11 V1.0.6 Tinker Board S R2.0 Android 11 V1.0.0 However, I was able to work around the problem as follows: Reboot the device to boot normally (I had to power off the Tinker Board, remove the SD card, power it on again, power off, reinsert SD card, power on again) adb shell su dd if=/storage/emulated/0/Download/magisk_patched-XXX.img of=/dev/block/by-name/boot adb reboot After the reboot, I'm able to grant root permissions to apps that request them.
  46. sonyan11
    @TzuWen_Chang Hello. Thank you so much for your kind advice. I will try. Best regards,
  47. TzuWen_Chang
    Hi, Here are a few ways to reduce radio frequency interference (RFI): 1. Disable USB 3.0. In your case, you can directly use a USB 2.0 port to connect the camera. 2. Improve signal shielding. Try adding metal shielding (grounded) between the Wi-Fi network card and the motherboard. 3. Switch to a USB Wi-Fi card and use a USB extension cable to move the USB Wi-Fi card away from the USB 3.0 port.
  48. Cliff Cliff changed their profile photo
  49. LucD started following Activate I2S
  50. LucD

    Activate I2S

    LucD posted a topic in Software

    Dear, I try to activate i2s on my thinkerboard 3S. Situation: Tinker Board 3/3S Debian 11 (kernel 5.10) V.1.0.7 Updated: /boot/config.txt intf:i2s3_2ch=on Direct connected i2s MEMS microphone, custom build on PCB, worked on tinkerboard S R2.0. Pins, power and ground Mic BCLK to pin 12 Mic DOUT to pin 38 Mic LRCL to pin 35 Updated the asound.conf to (based on chatGPT): pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 } alsa installed aplay -l doesn't list capture devices What am I missing?
  51. danfoxley
    I don't seem to have this file on Armbian 25 Noble with a Tinker Board S R 2.0. Please help with any suggestions. /boot/config.txt . Any suggestions?
  1. Load more activity
×
×
  • Create New...