Search the Community

Scan ssid by mobile phone the SSID can be seen . but always in password loop. I've installed hostapd V2.7 and dnsmasq V2.79. and wpa_supplicant and networkmanager are stopped. The config files are as below: 1: etc/hostapd/hostapd.conf interface=wlan0 driver=nl80211 ssid=TinkerNet hw_mode=g channel=7 wmm_enabled=0 macaddr_acl=0 auth_algs=1 ignore_broadcast_ssid=0 wpa=3 wpa_passphrase=mypassphrase wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP 2:/etc/dnsmasq.conf interface=wlan0 # Use the require wireless interface - usually wlan0 dhcp-range=192.168.1.2,192.168.1.254,255.255.255.0,12h Then I try armbian-config ...strange thing, there is not hotspot option in network. Anyone could explain how to config hotspot on Tinkerborad S with Ubuntu 18.04?

I have spent a considerable amount reading docs and getting my head around building a custom default kernel & desktop image. Patching the kernel and optimising the desktop environment is working well. The remaining question is: How do I select a specific - kernel 4.4.174 (based on armbian-release 5.75) ? It defaults to 4.4.176 and 5.86.

I downloaded the kernel source and kernel headers on a rk3288 rockchip (tinkerboardS) and noticed there was a mismatch between kernel version, armbian release and chipset (rockchip64) - see below. root@tinkerboard:~# uname -a Linux tinkerboard 4.4.174-rockchip #7 SMP Sun Feb 10 11:57:26 CET 2019 armv7l armv7l armv7l GNU/Linux root@tinkerboard:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=tinkerboard BOARD_NAME="Tinkerboard" BOARDFAMILY=rockchip VERSION=5.75 LINUXFAMILY=rockchip BRANCH=default ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage root@tinkerboard:/usr/src# ls * linux-rockchip64-default_4.4.178_5.85_config.xz linux-source-4.4.178-rockchip64.tar.xz

Hi I need to do the following things on my Tinker Board S what i normally do on Raspberry Pi 3: raspi-config; system; Hardware; 5 interfacing options, 6 Serial Would you like a login shell to be accessible over serial? = No Would you like the serial port hardware to be enabled? = Yes then I need to add the following line in the /boot/config.txt dtoverlay=rpi3-minuart-bt This activates the Serial Console on /dev/serial0 Where do I config Serial and how? what is the correct dtoverlay for the miniuar-bt in tinkerboard? does anyone have a hint for me?

When connecting to the built-in wifi adapter (wlan0) on the tinkerboard S (rockchip 3288), the kernel produces a stacktrace and clients can't connect. [ 839.074341] kernel BUG at mm/slub.c:3904! [ 839.078825] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM - (see http://ix.io/1J1n) Is there a fix for this?

We are looking at replacing the raspi3b+ with the tinkerboardS (rockchip 3288) in an embedded system, running armbian (bionic-4.19). Initial tests show that OS stability, board performance and form factor make the tinkerboardS a good substitute for the raspi. However, one issue we have run into is a conflict with pin 32 of the GPIO which is used by the hostboard for managing output devices. We have tried to turn off serial2 by removing the UART2 overlay and adding 'console=display' in /boot/armbianEnv.txt and also disabling & masking serial-getty@ttyS2.service but that hasn't stopped pin 32 from being chatty when connected to the hostboard. Is this possible that u-boot keeps writing/reading to and from ttyS2 (pin 32/33) regardless of the set kernel parameters? If so, how do we disable that?

Hi, I'm running Armbian Stretch on a Tinker Board and trying to use a one-wire thermometer. I have this in /boot/armbianEnv.txt: overlays=i2c1 i2c4 spi2 spidev2 uart1 uart2 w1-gpio However, when I boot the board, I see this in dmesg: [Wed May 8 17:38:43 2019] rockchip-pinctrl pinctrl: unable to find group for node w1_pins [Wed May 8 17:38:43 2019] w1-gpio: probe of onewire@0 failed with error -22 Kernel version is Linux tinkerboard 4.19.33-rockchip #5.77 SMP PREEMPT Wed Apr 3 17:06:29 CEST 2019 armv7l GNU/Linux Any ideas? I'm using the rockchip-w1-gpio.dtbo that was installed with the system. Regards, Dianne.

Dear All, I am running a project with Tinkerboard and a gigE camera. Trying to take video image through gstreamer (gst-launch). The camera is an Imaging source camera (DFK 33GX249) and I am using the linux library (https://github.com/TheImagingSource/tiscamera) for developing apps. My Tinkerboard is running Armbian Stretch (Armbian_5.50_Tinkerboard_Debian_stretch_next_4.14.52_desktop) Everything is working perfectly untill I am trying to run the command below: tinker@tinkerboard:~$ TCAM_LOG=DEBUG gst-launch-1.0 --gst-debug=tcamsrc:5,tcambin:5 --gst-debug-no-color tcambin ! videoconvert ! autovideosink The output is: In general the system crashes but I dont know why. I need to know if it because insufficient system resources or from own my fault. How can I cross check something like that? Is there any info in the above results that I can use for starting searching? Can anyone please help me? Thank you in advance Apostolos

I'm using Armbian on a Tinker Board S. I did the installation back when the 4.4 kernel was still the default one. I expected that I'd get the newer 4.19 kernel by using 'apt update && apt dist-upgrade' at some point as it would become the new stable. This does not seem to be the case however, as I see the new downloads use 4.19 by default, but the stable package still points to a 4.4 kernel. Is it recommended to just move up by installing the kernel package with the next suffix or are there still reasons to wait with upgrading?

I try to understand the usage of Tinkerboard for Industrial Application usage, we have below questions. 1. Operating temperature is between 0-60 C [as many Industrial PLCs recommend 0-55 C only] 2. Long Term Supply of the Boards 3. Bulk Quantities buying [Get 30 to 50 boards in 2-4 weeks notice] The board and quality seems top notice, RPI interface is good for our use cases, anyone sees a risk in above points or would like to suggest something? We are looking a good sized community, Ubuntu OS, much stable and better performing board compared to Raspberry PI, all seems good with Tinkerboard. Please share your ideas and thoughts. Regards, Gops

I put a TinkerBoard in a Pi-Top CEED and using TinkerOS 2.0.8 it boots and the LCD works fine. Using Armbian it looks like it boots but nothing is displayed on the LCD. The Pi-Top CEED uses a HDMI to 30-pin converter board and the current LCD is a 1920x1080 14in that I used to upgrade the original. Any ideas why the Raspberry running Raspbian and The Tinkerboard running TinkerOS would work with the display but Armbian wouldn’t?

Just reporting that there is some tx-offload bug in the ASUS Tinker Board Rockchip. I think I read about this issue regarding other rockchip/platforms when checksum offload bugs on large packets. When I run ethtool -K eth0 tx off I stop having issues with NFS over TCP The last part of diagnosis is when I forced a NFS crash by enabling tx offloading.

Hi! I connect my 1366x768 monitor to Tinkerboard, but resolution sets to 1280x720. $ xrandr Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192 HDMI-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 410mm x 230mm 1920x1080 60.00 + 1280x720 60.00* 720x480 60.00 Yes, i tried set timings manualy. I set native from edid: Modeline "Mode 0" 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync But after applying this modeline: - monitor detects 1280x720 resolution instead of 1366x768 - crops image as 1024x768 - have many noises and waves on screen... very unstable image (pixel clock 84.857 mhz, but expected 85.5 mhz) I tried use modelines but result is one - not working. Why it happens? Answer is simple: https://github.com/TinkerBoard/debian_kernel/blob/e57365482d2e2e5105d9d368eca432248fcf92a2/drivers/gpu/drm/rockchip/rockchip_drm_vop.c#L2273 /* * Hdmi or DisplayPort request a Accurate clock. */ if (output_type == DRM_MODE_CONNECTOR_HDMIA || output_type == DRM_MODE_CONNECTOR_DisplayPort) if (clock != request_clock) // see this return MODE_CLOCK_RANGE; Clock for HDMI must be set without any deviations. And this is the very reason why 1366x768 not listed in xrandr. But setting manual timings with xrandr omits this check. But not works too. Why? Here the answer was also simple. I added debug to hdmi_av_composer() for dump actual mpixelclock. And i set manual timings like this: Debug for this timings: [ 152.196219] hdisplay = 1366 pixel [ 152.196224] vdisplay = 768 lines // Front porch [ 152.196231] h_de_hs = 70 pixel clks // hsync len [ 152.196236] hsync_len = 143 pixel clks // back porch [ 152.196226] hblank = 426 pixel - (143 + 70) = 213 // Front porch [ 152.196234] v_de_vs = 3 lines // vsync len [ 152.196238] vsync_len = 3 lines // back porch [ 152.196229] vblank = 30 pixel - 6 = 24 // pixel clock [ 152.196241] vmode->mpixelclock = 84857000 hz [ 152.196243] vmode->mtmdsclock = 84857000 hz And what do we see? All is well, except pixel clock. I set 85.5 MHz, but driver set 84.857 MHz. WTF? 0.643 Mhz difference, Karl! What does it mean? PLL can't calculate dividers for wanted DCLK frequency. Okay, after few day of research i randomly checked TinkerOS. And it works: azq2@tinkerboard:~$ xrandr Screen 0: minimum 320 x 200, current 1280 x 720, maximum 8192 x 8192 HDMI-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 410mm x 230mm 1366x768 59.79 + 1920x1080 60.00 59.94 1152x864 75.00 1280x720 60.00* 59.94 1152x720 59.97 1024x768 75.03 60.00 832x624 74.55 800x600 75.00 60.32 720x480 60.00 59.94 640x480 75.00 60.00 59.94 720x400 70.08 O_O WTF??? This is a bug of Armbian maintainers...? (spoiler: It turned out that yes -_-) I checked all patches that affect dw hdmi or VOP. And I found a problem. In commit 93ae28f78dce6c747f0616dced591af7edf31377 maintainer igorpecovnik upgrades kernel and for some strange reasons disables very important patch 01-linux-0005-dts.patch But this patch contains important changes for HDMI: +static struct rockchip_pll_rate_table rk3288_npll_rates[] = { + RK3066_PLL_RATE_NB(594000000, 1, 99, 4, 32), + RK3066_PLL_RATE_NB(585000000, 6, 585, 4, 32), + RK3066_PLL_RATE_NB(432000000, 3, 216, 4, 32), + RK3066_PLL_RATE_NB(426000000, 3, 213, 4, 32), + RK3066_PLL_RATE_NB(400000000, 1, 100, 6, 32), + RK3066_PLL_RATE_NB(342000000, 3, 171, 4, 32), + RK3066_PLL_RATE_NB(297000000, 2, 198, 8, 16), + RK3066_PLL_RATE_NB(270000000, 1, 135, 12, 32), + RK3066_PLL_RATE_NB(260000000, 1, 130, 12, 32), + RK3066_PLL_RATE_NB(148500000, 1, 99, 16, 32), + RK3066_PLL_RATE(148352000, 13, 1125, 14), + RK3066_PLL_RATE_NB(146250000, 6, 585, 16, 32), + RK3066_PLL_RATE_NB(108000000, 1, 54, 12, 32), + RK3066_PLL_RATE_NB(106500000, 4, 213, 12, 32), + RK3066_PLL_RATE_NB(85500000, 4, 171, 12, 32), + RK3066_PLL_RATE_NB(74250000, 4, 198, 16, 32), + RK3066_PLL_RATE(74176000, 26, 1125, 14), + { /* sentinel */ }, +}; + #define RK3288_DIV_ACLK_CORE_M0_MASK 0xf #define RK3288_DIV_ACLK_CORE_M0_SHIFT 0 #define RK3288_DIV_ACLK_CORE_MP_MASK 0xf @@ -214,7 +235,7 @@ static struct rockchip_pll_clock rk3288_pll_clks[] __initdata = { [gpll] = PLL(pll_rk3066, PLL_GPLL, "gpll", mux_pll_p, 0, RK3288_PLL_CON(12), RK3288_MODE_CON, 12, 8, 0, rk3288_pll_rates), [npll] = PLL(pll_rk3066, PLL_NPLL, "npll", mux_pll_p, 0, RK3288_PLL_CON(16), - RK3288_MODE_CON, 14, 9, ROCKCHIP_PLL_SYNC_RATE, rk3288_pll_rates), + RK3288_MODE_CON, 14, 9, 0, rk3288_npll_rates), }; It adds additional dividers for npll (used as source for DCLK). For exmaple, 85500000 needed for me. After applying this patch my problem resolved. All resolutions determinted and monitor works normal. root@tinkerboard:~# cat /sys/devices/platform/display-subsystem/drm/card0/card0-HDMI-A-1/modes 1366x768p60 1920x1080p60 1920x1080p60 1152x864p75 1280x720p60 1280x720p60 1024x768p75 1024x768p60 800x600p75 800x600p60 640x480p75 720x400p70 I send pull request https://github.com/armbian/build/pull/1317 I'm not sure that he will be accepted. I created this topic for tinkerboard users with same problem. This patch helped me. You can manualy build kernel with this patch (needed ubuntu bionic as host system): git clone https://github.com/armbian/build cd build wget https://patch-diff.githubusercontent.com/raw/armbian/build/pull/1317.patch -O 1317.patch patch -p1 < 1317.patch sudo ./compile.sh BOARD=tinkerboard BRANCH=default KERNEL_ONLY=yes RELEASE=bionic NO_APT_CACHER=yes BUILD_KSRC=no P.S. The commit description speaks for itself Debs for test: linux-image-rockchip_5.77_armhf.deb linux-dtb-rockchip_5.77_armhf.deb Or image with installed patched debs:https://zhumar.in/Armbian_5.75_Tinkerboard_Ubuntu_bionic_next_4.19.20_desktop_v3.zip sha256: 377040dd9c42beaec1531199099d0eb12a547cab3f4e761801bbe1c20afe00b1 Not official. Only for test. Use this as own risk.

Hey, maybe a stupid question, but how I can change the i2c clock rate in the armbianENV.txt? I have search around the forum and didn't find anything. can someone point me in right direction? Greets

Hello Guys. สมัครสมาชิกufabet เว็บพนันบอลต่างประเทศ I want to extend the current kernel (Tinkerboard with rockchip-kernel-4.4.120 on Debian-Armbian) to include IR (GPIO) and DVB modules. What do I have to consider or is this possible with the usual run-through? (copy .config from current system, make menuconfig, make, sudo make install, sudo make modules_install) Is there possibly already a tutorial that I have not seen?

Hy, I have tried to use my tinkerboard like an hotspot. configuration done with armbian-config. when i used the armbian jessie ( ARMBIAN 5.73 stable Debian GNU/Linux 8 (jessie) 4.19.20-rockchip) : everything works IF i don't do an apt-upgrade. If i do an apt-upgrade or using the last img of armbian strectch, i cannot connect any devices to my Tinkerboard : here what i have when i used ssh to see what's wrong : Can somebody help me please

Hello ! I bought this screen recently: https://www.seeedstudio.com/10-1-inch-1200-1980-HDMI-IPS-LCD-Display-p-2863.html I tried to connect it to my Tinkerboard but could not get an image. On an raspberry I have input specific display settings in the configuration file. hdmi_drive=2 hdmi_mode=87 disable_overscan=1 # 10.1 inch hdmi_timings=1200 0 100 24 52 1920 0 65 4 25 0 0 0 60 0 169000000 0 max_framebuffer_width=1920 max_framebuffer_height=1920 display_rotate=3 framebuffer_width=1920 framebuffer_height=1200 By cons I do not know how to do with the tinkerboard. same problem on Nanopi-M4

Tinkerboard (old one, not S) to be used as x2go thin client. Installed latest image (5.70_Tinkerboard_Ubuntu_bionic_next_4.19.14_desktop), applied all updates. Working fine (thanks to everybody who contributed). Issue remaining: My Tinkerboard refuses to use the monitor's native display size of 1920x1200, tried several monitors and cables (HDMI to DVI adapter cables, in case this is relevant). Without any modifications, Armbian desktop comes up with 1280x960. I used xrandr to set 1920x1080 (works), but 1920x1200 leads to "xrandr: Configure crtc 0 failed". Any chance to resolve this?

Hello, I have several Hardware working with the Tinkerboard / S and like to propose those to the "Tested 3rd party hardware" section To whom can i address this? Thanks Roman

Hello, Has anyone managed to get usb-redirector working? 4.14.70-rockchip and headers. with 'arm' It installs ok, and the driver loads... lsmod and dmesg confirms. Module Size Used by tusbd 126976 0 but when I try one the binaries, it just returns me back to the prompt.??? (i've tried other versions arm-eabi. armeb, that just returns file not found when using a binary) Many thanks. Mark

Hi, I'm trying to upgrade my armbian from 5.73 to 5.75 but without succes. I've checked in armbian-config if the updates are not frozen which is not the case. I tried : - sudo apt-get update sudo apt-get upgrade - sudo apt update - armbian config -> system - > firmware (update) I did accidentally installed Full firmware package but reverted to mini. kernel version should be ok : ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.19.20-rockchip And I'm not sure what else I can do to upgrade to 5.75... I would like to use the new drivers for the CPU so htop shows more info. Thanks!

Hello Currently my SixFab 4G hat is not working with the 4.4.x Kernel but with the latest 4.19.y Is there any chance that you port media script to the new Kernel build? Many Thanks Roman

Hy again :p; I have customed my sd for my tinkerboard. i have done some settings like eth0 in static, partitions modified scripts and hostapd. When i put it in another Tinkerboard, everything works except wifi ap. I have searched why, and i have found that in my initial tinkerboard wifi is wlan0 and his settings is in /etc/network/interfaces.d/armbian.ap.nat When i put my SD in another tinkerboard, it is wlan1 which mounts and no wlan0. Wlan1 has no ip address. i don't see where is the problem? thanks by advance

Hy, I'm looking for a Command to get the Serial Number of my Tinkerboard. I have found this in the Web : cat /proc/cpuinfo | grep Serial | sed s/.*\ //g But i get 000000000000. Someone have an Idea please? Thank you :)

Hy, I have a Tinkerboard with armbian ( debian jessie). When I put behind my fiber router, and i do a speed test i have : With iperf3 ==> download : 980M and upload : 240M with speedtest-cli ==> More or less Results. I wanted to conenct my Asus's card behind the ONT(Optical Termination Boxes) i can connect with pppoe or dhcp. And in pppoe or dhcp my speed test show this : With iperf3 ==> download : 110M and upload : 80M with speedtest-cli ==> More or less Results. I have tested with anorther Board, bananapi mé with Bananian and i have the same Results if I put behind my fiber router so : With iperf3 ==> download : 980M and upload : 240M with speedtest-cli ==> More or less Results. Someone can help me