Jump to content
New Wiki - User & Developer Guide ×

All Activity

This stream auto-updates     

  1. Past hour
  2. in_sympathy in_sympathy joined the community
  3. Today
  4. FlostonParadise
    thanks, but I couldn’t find the dimensions for the sockets 😞
  5. tooz
    hello @FlostonParadise, you can check the drawings for reference: Tinker Board there are also aluminium cases avaiable in the market
  6. FlostonParadise started following Dimensions of cutouts for sockets
  7. FlostonParadise
    Hello Perhaps someone has a ready-made size to make cutouts in their own case. tinker board 2S
  8. tooz
    hello @Fu-., from what you decribed it's possible that it might be a hardware issue, but i'm not 100% sure. have you also modified the settings of /boot/config.txt ?
  9. Fu-.
    hello @tooz I tried setting via sysfs gpio, it seemed to be the same behavor.
  10. tooz
    hello @Fu-., have you tried using sysfs instead?
  11. Yesterday
  12. Fu-.
    hello @tooz I'm setting both pins as GPIO. I don't want these pin as using SPI, just only GPIO.
  13. tooz
    hello @Fu-., setting spi is not supported in wiringpi what are you setting for gpio2c6 and gpio2c7 and what's your configuration?
  14. Last week
  15. hasank hasank changed their profile photo
  16. Fu-.
    Question about GPIO2C6 and GPIO2C7 pins. It is possible to set them to GPIO using wiringPi, but the voltage at HIGH output is lower than other GPIO pins. It is only about 1.95V. Upon further investigation, I found that a clock-like waveform is output during HIGH output. GPIO2C6 is exclusive with SPI5_CLK and GPIO2C7 is exclusive with SPI5_CSN, but it appears that the SPI5 clock continues to be output when each pin is set as a GPIO. Any suggestions?
  17. Earlier
  18. denbon denbon joined the community
  19. rugfk rugfk changed their profile photo
  20. Lee Swee Kee
    Found it in other thread in the forum.
  21. Lee Swee Kee
    Had been using this on a gen 1 tinker board for quite some time. Unfortunately, the SD card was corrupted, and my Mac also had to be reset and could no longer find the original download. Please re-host the download again. It is still useful for the old tinker board.
  22. Lee Swee Kee Lee Swee Kee joined the community
  23. TomasA started following [Release] Tinker Board Debian OS V2.1.16
  24. TomasA
    Hello, will there also be a new version of Debian 12 for Tinker Board S R2.0?
  25. TomasA TomasA joined the community
  26. Ming-Ta Yu started following Tinker Board draws power after shutdown
  27. Erik started following Tinker Board draws power after shutdown
  28. Erik
    I've got an original Tinker Board v1.2 and have tried putting DietPi and Armbian on it because Tinker Os for this board is too old to install Klipper. Problem is with both DietPi and Armbian, when I shutdown the board, the lights go out but it still draws 400 to 700mA and the SOC stays warm. With Tinker OS it doesn't do this, the power usage goes to zero after shutdown. Does anyone know how to fix Armbian or DietPi so the power gets turned off when the board is shut down?
  29. Erik Erik joined the community
  30. Igor Melnik Igor Melnik changed their profile photo
  31. tooz

    OS Andorid

    tooz replied to Augusto Hertz's topic in Android

    hello @Augusto Hertz, the android releases can be found on the official website: Tinker Board the latest version is: Tinker Board 3 Android 14 (kernel 6.1) V.1.0.9
  32. lamode lamode joined the community
  33. ninosan ninosan joined the community
  34. Kai005 started following Xibo - Digital signage software with Tinker Board 3N
  35. Kai005
    A few days later I tried Xibo on Tinker board 3N and it worked, yay~ https://xibosignage.com/ I used Xibo to design the layout and push it remotely to Tinker board 3N, there are many interactivity features to try. I tried Android 12, Xibo also supports Linux, I think Debian should be work.
  36. vanth started following No cxf file to load into the Tuning Tool
  37. vanth
    Hi, I'm using the RKIQ_Tuning_Tool_V1.9.1 for purpose of color calibration. I'm having trouble loading SG_chart.cxf because I don't have eye-one device to generate the SG_chart.cxf file. Does anyone have a cxf file to tune the colors on the Rockchip Tuning Tool with the 24 color chart? Thanks a lot.
  38. vanth vanth joined the community
  39. michaelbhavel
    I think no, USB debugging not required if you're using Wireless Debugging. No fast-boot devices connected error typically means the device not in fastboot mode or is not detect. Ensure, it's in fastboot mode and try restart adb with adb kill-server and adb start-server.
  40. MS1 MS1 joined the community
  41. PIROGUE 1 PIROGUE 1 joined the community
  42. deanmsands3
    How much time you got? In Weston using FBDev mode as root or with permission-modded /dev/mali0: Weston: Success cog w/Wayland: Platform setup failed: Could not initialize EGL (0x3001) After a while, I must have changed something because Weston stopped working with FBDev. In Weston using DRM mode as root or with permission-modded /dev/mali0: Weston: Success cog w/Wayland: EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) glmark2: glmark2: Error: Could not Initialize canvas glmark2-wayland: Error: Failed to bind api Error: main: Could not initialize canvas glmark2-es2-wayland: Success From command-line as root or with permission-modded /dev/mali0: drmgl: Success ( https://gist.github.com/Miouyouyou/89e9fe56a2c59bce7d4a18a858f389ef/raw/b4b5c03398ef84446f9212e1112d87dcaee8fa87/Linux_DRM_OpenGLES.c ) kmscube: kmscube: Success kmscube using card0: Success glmark2: glmark2: Error: Could not Initialize canvas glmark2-drm: error: Failed to bind api error: main: Could not initialize canvas glmark2-es2: Success glmark2-es2-drm: Success Without modding /dev/mali0's permissions, a user in video, render, and input groups: Weston: DRM w/ or w/o launcher: Failed creating base context during opening of kernel driver. Kernel module may not have been loaded arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. failed to initialize failed to initialize EGL FBDev: weston-launcher: Success but without menu on the top Without launcher: Failed creating base context during opening of kernel driver. Kernel module may not have been loaded arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. failed to initialize failed to initialize EGL glmark2: glmark2-es2: Error: Could not Initialize canvas glmark2-es2-drm: arm_release_ver of this libmali is ‘r18p0-01rel0’, rk_so_ver is '5' Failed creating base context during opening of kernel driver Kernel module may not have been loaded. arm_release_ver of this libmali is ‘r18p0-01rel0’, rk_so_ver is '5' Error: eglInitialize() failed with error 0x3001 Error: main: Could not initialize canvas drmgl: Failed creating base context during opening of kernel driver. Kernel module may not have been loaded arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. failed to initialize failed to initialize EGL kmscube w/ or w/o card0: Failed creating base context during opening of kernel driver. Kernel module may not have been loaded arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '5'. failed to initialize failed to initialize EGL I'll have to check while an application is running. With no application running, the /boot/display tree doesn't exist.
  43. tooz
    hello @deanmsands3, the official distro uses x11 instead of wayland and we cannot guarantee that gpu/ diplay will function well with this massive change in terms of mali midgard driver updates, we usually integrade the software development kits release from rockchip, instead of fetching sources from arm. this way we're more confident with the hardware compatibility may we know in what cases it works and in what cases it doesn't? are you able to fetch the node in xrandr.cfg? cat /boot/display/hdmi/xrandr.cfg
  44. deanmsands3
    It's a re-assembled image using the first 8 partitions of the official distro with a root fs rebuilt with debootstrap as well as the firmware and kernel modules from the original. I compiled the Mali Midgard Wayland GBM driver from the Rockchip libmali repo and it works in some but not all cases. I'm running Chromium w/Wayland turned on inside Cage kiosk 0.12.1 compiled for Bullseye. While not a best practice, I have a one-shot service that changes the permissions on /dev/mali0 from 600 root:root to 660 root:video. This doesn't work in a systemd service, but USUALLY works fine run from the command line after the system has finished booting. Usually. I can try again with an official image but my priorities have shifted for the moment. Using the official image, I would do the following. Disable the lightdm service. Install the Mali Midgard Wayland GBM driver. Write a oneshot systemd service to mod /dev/mali0's permissions, setting it to start after systemd-udevd.service. Write another systemd service for cage using the template in the wiki modified so that it depends on the first service. modified ExecStart to cage -- chromium --kiosk --enable-features=UseOzonePlatform --ozone-platform=wayland "https://www.google.com" Add the PAM config for cage (per the wiki). Enable the cage service. Reboot. An alternative configuration would be everything from the first one except: No systemd service for cage. override getty@tty1 to auto-login to the kiosk user. modify the .bashrc script to run the cage command. I also tried a variation of the second one using the pre-installed X drivers with openbox as a backend and a .xinitrc script to launch chromium. That one lacked hardware acceleration (which my project absolutely needs), but thinking back on it, I might have accidentally left in the Wayland parameters. I'll try it again later this week. For those interested in trying the Wayland Drivers: # On an AArch64 Bullseye OS (like the official image): # Install the build dependencies (along with git) # Check the BuildDepends line in https://github.com/TinkerBoard-Linux/rockchip-linux-libmali/blob/linux5.10-rk3399-debian11/debian/control # This command is all one line. sudo apt install git devscripts build-essential lintian \ debhelper meson pkg-config libstdc++6 libgbm-dev \ libdrm-dev libx11-xcb1 libxcb-dri2-0 libxdamage1 \ libxext6 libwayland-client0 # Wait for the packages to install mkdir drivers # The debian build process will store the debs in this folder. cd drivers git clone https://github.com/TinkerBoard-Linux/rockchip-linux-libmali.git cd rockchip-linux-libmali git checkout linux5.10-rk3399-debian11 # Or whichever branch you need debuild -us -uc # Run the actual build # Go make some coffee or something. # Ponder the nature of the universe. # Maybe a little more coffee. # Reconnect with an old friend - and oh hey! It's done. cd .. # Back to the drivers folder # Find the deb package starting with "libmali-midgard-t86x-r18p0-wayland-gbm"
  45. tooz
    hello @deanmsands3, did you compile the .img by yourself, or was it downloaded from the official website: Tinker Board if it's the latter, which version are you using? we're trying to duplicate the issue and see what goes wrong
  46. deanmsands3
    From the rockchip-linux-kernel repo, branch: linux5.10-rk3399-debian11: /drivers/gpu/drm/rockchip/rockchip_drm_vop.c: #define ASUS_HDMI_RESOLUTION_FILE_PATH "/boot/display/hdmi/xrandr.cfg" #define ASUS_DP_RESOLUTION_FILE_PATH "/boot/display/dp/xrandr.cfg" static void asus_write_resolution_to_file(char *buf, int writelen, int type) { struct file *fp; loff_t pos = 0; if(type == DRM_MODE_CONNECTOR_HDMIA) { fp = filp_open(ASUS_HDMI_RESOLUTION_FILE_PATH, O_WRONLY, 0644); if(!IS_ERR(fp)) { kernel_write(fp, buf, writelen, &pos); pr_info("%s: set HDMI resolution file to %s", __func__, buf); filp_close(fp, NULL); } else pr_err("%s: HDMI failed to open file\n", __func__); } else if(type == DRM_MODE_CONNECTOR_DisplayPort) { fp = filp_open(ASUS_DP_RESOLUTION_FILE_PATH, O_WRONLY, 0644); if(!IS_ERR(fp)) { kernel_write(fp, buf, writelen, &pos); pr_info("%s: set DP resolution file to %s", __func__, buf); filp_close(fp, NULL); } else pr_err("%s: DP failed to open file\n", __func__); } else pr_err("%s: error type\n", __func__); } So, this file, "/boot/display/hdmi/xrandr.cfg", which doesn't exist on the visible filesystem, has to be available to the kernel for this function to work. But I can't find any information about it. Any help from the Asus engineers?
  47. Ming-Ta Yu started following Updated Linux libMali drivers? and Debian: Cannot change video mode inside a systemd service
  48. deanmsands3
    Distro: Debian Bullseye OS: Linux 5.10.198 Arch: Arm64 GPU: Mali Midgard T-860 Driver: libmali-midgard-t86x-r18p0-wayland-gbm Hello! Trying to launch a browser session from a systemd service. I'm getting this error when I try to run the service. [ 175.756156] rockchip-vop ff900000.vop: [drm:vop_crtc_atomic_enable] Update mode to 1920x1080p60, type: 11 [ 175.756243] asus_write_resolution_to_file: HDMI failed to open file What's causing this and how do I fix it? Or how do I debug it?
  49. deanmsands3
    Rockchip released the r18 version of the libMali Midgard T86X drivers. Arm has r28 source listed on their site. The current Mali DDK doesn't cover the Midgard chips so I can't compile it myself. Will Rockchip update the drivers? Is there any way to contact them about this?
  50. tooz
    hello @Vova Efcom are you looking for 4 pin female connector for tinker board or tinker board 3n?
  1. Load more activity
×
×
  • Create New...