Jump to content

Search the Community

Showing results for tags 'tinkerboard'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Hi! I seem to have the same problem described here: I have an Asus Tinkerboard, not the S version. Today I upgraded from the latest Asus TinkerOS image: 20190821-tinker-board-linaro-stretch-alip-v2.0.11.img to: Armbian_19.11.3.346_Tinkerboard_buster_current_5.3.15_minimal.img I notice that my maximum CPU frequency has dropped from 1.80GHz to 1.61GHz. cpufreq-info now reports: $ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 115 us. hardware limits: 126 MHz - 1.61 GHz ... and my cpufrequtils config is unmodified: $ cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=600000 MAX_SPEED=1900000 GOVERNOR=ondemand Whereas on TinkerOS, cpufreq-info reported: $ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 115 us. hardware limits: 126 MHz - 1.80 GHz ... Is this something I can change locally, or does something need to change in the Armbian image?
  2. Hi guys i am new on forum so i am sorry if this topic is in wrong place or if i badly look for answer in existing topics. I already using bionic legacy 4.4.199 destkop for few weeks and i am happy ( only problem which i have is with bluetooth-device manager not working aftar i connect keyboard or mouse and handsfree doesnt work too) but i see on web that there is new version so i download bionic 5.4.8 desktop to give a try. boot look normal until i get to tinkerboard login. there i use default root/1234 - it ask for changing root pass so i make it - then Retype pass and after enter it doesnt do anything. i can type anythong but enter only move to another line but nothing else. i even try to flash twice but same result. I have same problem on buster_current_5.4.8_minimal is it normal (on develop) or there is problem on my TB? thanks for answers. (sorry for my bad english)
  3. Hi there, can anyone give me an URL that i can download an Armbian Stretch Release for the Tinkerboard S? I´ve Problems with my RPI-RF-MOD and i´m thinking it is something with the new Releases. Thx.
  4. Hi all, I'm trying a Tinkerboard running armbian (minimal) and DietPi. My goal is to handle suspend and wake up. To enter in suspend mode i run 'echo mem > /sys/power/state'. I'm looking other ways to suspend .. by C application or by a signal on GPIO To wakes up I notes different modes on different OSes: - linaro pressing power button, pressing a key on usb+bt keyboard, pressing usb+bt mouse button - dietpi - pressing power button - armbian minimal - nothing ? my guess is that the board shuts down Please con you confirm? Where does reside this different behaviors? Thanks, regards. PS: is it possible to handle hibernation?
  5. Hello, I'm unable to make the RTL8723BS chip on my Tinker Board to work on AP mode with the 5.4 kernel (same configuration works on legacy kernel). When I try to connect I get this error on dmesg: RTL8723BS: ap recv deauth reason code(3) sta:40:4e:36:cf:8a:18 On the console I also get a bunch of kernel errors similar to this: Message from syslogd@localhost at Dec 27 14:26:11 ... kernel:[ 799.239910] ff60: bf0377a4 dd8057e8 dd07ffac dd07ff78 c014a17c bf0377b0 de2d9128 de2d9128 Is this a known problem? Thanks
  6. Hello, I'm trying to show a startup logo a Tinker Board without success. I tried to add a parameter logo=/boot/boot.bmp to /boot/armbianEnv.txt but it doesn't work. Is the boot logo implemented on the Tinker Board? Does it require a patch? Thanks for your feedback.
  7. Hi, because I find in 4r dont see any topic to talk more about change ramdisk as increase or decrease, so I make this cmt, hope somebody help me know + How to resize for ramdisk, and how to using sd card as ramdisk and swap file, so emmc size will be have more space, because I want install kali into + If using bionic desktop, and only install kali tool for pentest, will bionic running ok ? or I must build and install kali as root ? Hope someone can help me know it. Thank you so much
  8. Dear all, I'm looking for help on having RFCOMM TTY working on a Tinker Board S. Any help will be welcome !! Using : Ubuntu Bionic with Armbian Linux 4.19.69-rockchip # uname -a Linux astrotinker 4.19.69-rockchip #5.95 SMP PREEMPT Mon Sep 2 07:34:36 CEST 2019 armv7l armv7l armv7l GNU/Linux I'm trying to have rfcomm tty working with a bt HC-05 dongle, but RFCOMM TTY seems not to be available. The BT HC-05 is well reconized and connected: # bluetoothctl [NEW] Controller 80:C5:F2:46:E2:C2 astrotinker [default] [NEW] Device 00:14:03:06:04:ED HC-05_TIC Agent registered # systemctl restart bluetooth.service # systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-11-25 22:23:51 CET; 3min 30s ago Docs: man:bluetoothd(8) Process: 5198 ExecStartPost=/usr/bin/rfcomm bind rfcomm1 00:14:03:06:04:ED (code=exited, status=0/SUCCESS) Main PID: 5196 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4784) CGroup: /system.slice/bluetooth.service └─5196 /usr/lib/bluetooth/bluetoothd -E Nov 25 22:23:51 astrotinker bluetoothd[5196]: System does not support network plugin Nov 25 22:23:51 astrotinker bluetoothd[5196]: Bluetooth management interface 1.14 initialized Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.73 path=/MediaEndpoint/A2DPSource Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.73 path=/MediaEndpoint/A2DPSink Nov 25 22:23:51 astrotinker bluetoothd[5196]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Nov 25 22:23:51 astrotinker bluetoothd[5196]: RFCOMM server failed for :1.73/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: Nov 25 22:23:51 astrotinker rfcomm[5198]: RFCOMM TTY support not available Nov 25 22:23:51 astrotinker systemd[1]: Started Bluetooth service. # journalctl -u bluetooth.service -- Logs begin at Mon 2019-11-25 00:30:28 CET, end at Mon 2019-11-25 22:23:52 CET. -- Nov 25 00:30:35 astrotinker systemd[1]: Starting Bluetooth service... Nov 25 00:30:35 astrotinker bluetoothd[1466]: Bluetooth daemon 5.48 Nov 25 00:30:35 astrotinker bluetoothd[1466]: Starting SDP server Nov 25 00:30:35 astrotinker bluetoothd[1466]: kernel lacks bnep-protocol support Nov 25 00:30:35 astrotinker bluetoothd[1466]: System does not support network plugin Nov 25 00:30:35 astrotinker bluetoothd[1466]: Bluetooth management interface 1.14 initialized Nov 25 00:30:35 astrotinker rfcomm[1467]: RFCOMM TTY support not available Regards Franck
  9. Hi all, I just bought TinkerBoard S and I downloaded Armbian Stretch 4.19 (tried both with and without desktop ) and I tried to boot. But no luck I was waiting for few mins but nothing. I also tried Armbian Strech 4.4 but also nothing. Am I missing something here? Original TinkerOS work without any issue Thank you for any advice/help
  10. Hello people, I am trying to set CPU Governors but all the cores change to the same clock and cpufreq-info reports "CPUs which run at the same hardware frequency: 0 1 2 3", with that even one thread working is making the CPU scale up all clocks and heat more than it should, is there a way to unlink them and each one have their own clocks according to each core processing load?
  11. Hello all, I downloaded the Armbian Buster OS desktop version. I need to run it with a vertical display - portrait mode. The OS starts correctly and I see the desktop in landscape mode but when I try to rotate left the display, it does not rotate and return to landscape mode. The display is a large NBT monitor 1920x1080 that I need to rotate to 1080x1920. Any idea? Regards
  12. Looking for a current realtime RTOS real time deb package or SD card image for the tinkerboard. I have been trying to compile a current real time build. All of my attempts have failed so far. free offer described below
  13. Hello! I would like to know if it is possible to use the microUSB-Connector for connecting a USB device (a 7-port USB hub in my case)? My Tinkerboard is powered through the GPIO pins, so i don't use the microUSB for power input. Is it even possible from the hardware architecture of the board? Do i need some extra kernel packages and/or USB OTG to make it work? Thanks in advance, aElmecker
  14. Greetings, After setting my tinkerboard pins 22 and 24 as an Inputs, they reverts to being an output pin on HIgh after around 30 seconds. What is the cause of this? Is this some kind of feature. I don't have this happen on any other pin other than these 2. iomari
  15. Greetings, On the tinkerBoard, I'm using python. I having difficulty understanding why the functions don't return the values that is expected according tho the library help. I'm using python3 and the ASUS GPIO library. import ASUS.GPIO as GPIO GPIO.setmode(GPIO.BOARD) This is the output from ipython: In [18]: help(GPIO.gpio_function) Help on built-in function gpio_function in module ASUS.GPIO: gpio_function(...) Return the current GPIO function (IN, OUT, PWM, SERIAL, I2C, SPI) channel - either board pin number ,RK number or ASUS number depending on which mode is set. But when I try for instance: In [19]: GPIO.gpio_function(29) Out[19]: 1 AS you can see, the return value is '1' not (IN, OUT, PWM, SERIAL, I2C, SPI) Also if I run: In [20]: help(GPIO.getmode) Help on built-in function getmode in module ASUS.GPIO: getmode(...) Get numbering mode used for channel numbers. Returns BOARD, RK, ASUS or UNKNOWN Then I run: In [21]: GPIO.getmode() Out[21]: 10 As you can see, I'm not getting a return of 'BOARD, RK, ASUS or UNKNOWN' but instead I'm getting 10. IS it me or are the outputs to these functions wrong? iomari
  16. Hi I have a problem with change desktop language from en to polish. I tryed all solutions armbian-config , dpkg-reconfigure locales, export LANG. After reboot I got english desktop and locale info http://ecocut.pl/wp-content/uploads/2019/03/locale-1.jpg
  17. I have 85 tinkers running with armbian 5.41 xenial next 4.14.23. Normally I run a script that apt upgrades them all but I run a small batch of them first as a test. Today I ran apt update/upgrade on three of them and they are all bricked. No output to the screen. Can't ping them. Any ideas?
  18. Hi, I am looking for a solution to have the JustBoom and HifiBerry Audio Hat with dtoverlays working like in the TinkerOS 2.0.8 Image from ASUS. Does someone known and has a procedure how to compile those and integrate in the Image or Compile a new kernel with its integration or a way to get those two hat's working? Many Thanks for your help Roman
  19. Hi, I spent several days trying to figure this out, which is a bit confusing given all the information that is available and posts and wikis saying that "Waveshare" LCDs are supposed to work, but something is still not right, hope you guys can help. What I have: ASUS Tinker Board S, flashed with Armbian_5.90_Tinkerboard_Debian_buster_default_4.4.182_desktop.img Updated to 4.19.57-rockchip via armbian-config (in order to get the fbtft* modules that were missing in 4.4). The LCD is a 3.5" original Waveshare 32a panel. I started by adding the overlay for this screen (i.e. my armbianEnv.txt has these overlays: overlays=i2c1 i2c4 spi2 waveshare35a-tinker uart1 uart2): https://github.com/TinkerBoard/debian_kernel/blob/develop/arch/arm/boot/dts/overlays/waveshare35a-tinker-overlay.dts I have a serial console connection and I could see that the overlay is getting loaded upon boot: Applying kernel provided DT overlay rockchip-i2c1.dtbo 286 bytes read in 1 ms (279.3 KiB/s) Applying kernel provided DT overlay rockchip-i2c4.dtbo 311 bytes read in 1 ms (303.7 KiB/s) Applying kernel provided DT overlay rockchip-spi2.dtbo 2224 bytes read in 2 ms (1.1 MiB/s) Applying kernel provided DT overlay rockchip-waveshare35a-tinker.dtbo 287 bytes read in 2 ms (139.6 KiB/s) Applying kernel provided DT overlay rockchip-uart1.dtbo 287 bytes read in 1 ms (280.3 KiB/s) Applying kernel provided DT overlay rockchip-uart2.dtbo 232 bytes read in 1 ms (226.6 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) Adding the above overlay made the touchscreen work out of the box, however the framebuffer device didn't. In dmesg I could see the following: [ 15.706674] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 15.712403] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 15.712696] rockchip-pinctrl pinctrl: unable to find group for node waveshare35a_pins [ 15.712708] fb_ili9486: probe of spi2.0 failed with error -22 I read the driver sources, pinctrl documentation, overlay documentation, but being a userspace coder I did not really know what to make of all this and the above pinctrl error message. The waveshare nodes were available in the live device tree, so I am not sure why this line triggers and where this "group" is supposed to be coming from: https://github.com/armbian/linux/blob/rockchip/drivers/pinctrl/pinctrl-rockchip.c#L566 I then tried to configure the fbtft_device driver manually using the following parameters (tried to use the values from the waveshare dts): modprobe fbtft_device custom name=fb_ili9486 gpios=dc:163,reet:171 speed=15000000 busnum=2 rotate=270 fps=30 txbuflen=32768 bgr=0 width=480 height=320 The above made half of the screen to react, settig the rotation to 0 allowed to access the whole screen (tried catting /dev/random into /dev/fb0 which fills the screen with random colored pixels). I added xorg settings as suggested in the tinkerboard wiki and started xorg: Section "Device" Identifier "Rockchip Graphics" Driver "fbdev" Option "fbdev" "/dev/fb0" Option "DRI" "2" EndSection However the image looked totally distorted (I had the feeling that its drawing every other line), it was however vaguely recognizable as some text / X login screen. Just out of curiosity I removed the overlay, rebooted and again loaded the driver as above with the same result (only that touchscreen did not work anymore as expected). I am adding a full dmesg output with the overlay applied, the first fbtft load attempt is the "automatic" one and shows the rockchip pinctrl error, the second fbtft loading comes from my manual modprobe line which I pasted earlier. I have no idea where to go from here, I thought those Waveshare screens are well supported, and from what I read they seem to work for others. What am I missing? Kind regards, Jin P.S. ...couple of hours later... Turned out that the results are a lot better if width and height parameters are left out. While the dts suggests to use bgr=0, bgr=1 gives correct colors, but it seems that the gamma is totally off. I also tried taking the init sequence from the dts and passing it to fbtft_device, but I could not see any difference. So right now I ended up with the following line and results: modprobe fbtft_device custom name=fb_ili9486 bgr=1 gpios=dc:163,reset:171 speed=15000000 busnum=2 fps=30 txbuflen=32768 Original image for comparison: So, some progress at last, I'd however be still interested in fixing the pinctrl problem and understanding why the dts would not work... Next question of course - how to come up with proper gamma values?
  20. Installed the desktop version of Armbian (bionic) on Asus Tinker Board S and noticed that the GPIO Pin 40 is always high on boot up. Please let me know whether this is high by default for any reason and if possible how to set it to Low while start up.
  21. Update May-21-2018: script may have negative impact on HDMI audio, needs further investigation. Patches pushed to enable I2S HDMI device, but audio does not come out. Update Feb-20-2018: script update committed for out of the box audio support (both outputs and inputs) for ASUS Tinker Board. Available sinks: BT-VOIP SPDIF Headset (the jack) Available sources: BT-VOIP Headset-input (the jack) Tinkerboard sound is possible with Armbian, however I have not worked to get it set up "out of the box" because of a major bug in the sound itself, namely that it outputs pure high pitched garbage from certain applications and certain source materials. I don't want anyone going deaf/destroying equipment, and I don't want to get backed into a corner on something I don't immediately know how to fix. That said, I'm hoping @Kwiboo or @Da Alchemist or the like may have an idea of what's going on here, it's one of the more annoying issues holding this back from being a daily driver. It's important to note I experienced the same sort of insanity using a simple I2S DAC with the Tinker Board. If some PA settings can take care of it that's great, if it's a clock issue on the Tinker I'm not sure where to go from there. I will be doing some testing on the new kernel 4.13, as there have been some clock reassignments/adjustments that, while seemingly unrelated, may be. Also, has anyone found a specific driver for the Realtek chip, or is it still just "generic USB Audio?"
  22. Anyone who typically updates on nightly kernels I would recommend freezing and not updating until we clear up some issues gifted us by some large amount of upstream changes that broke well, pretty much everything. I will update this thread as things get brought back to life. June 7th 2018: I've made a branch (rockchip-default) to work out the kinks. So far I have the board booting and Mali working again (with an initial error on load) , however there is no HDMI terminal, so initial boots would require a uart or SSH hdmi terminal is back thank you to Ntemis on github, I'd missed part of the conversation (I only have cell phone while at work) July 19th 2019: an issue with kernel 4.4 and spidev came up, no one is apparently using it, in any case Pi Supply found it while updating Tinker Board support. Fix committed.
  23. Hi there, I'm trying to install docker on my tinkerboard s running armbian 5.73. I've managed the following steps from your documentation: sudo apt-key adv --keyserver pool.sks-keyservers.net --recv-keys 0EBFCD88 sudo echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable" > sudo /etc/apt/sources.list.d/docker.list sudo apt update But when i tried to install docker using: sudo apt install docker-ce I'm getting the error that docker-ce has no installation candidate. Does anyone maybe have an idea how to get this working? Thank you.
  24. Hi all, I'm running Armbian 4.19 (both stable kernel 5.77 and nightly) on an TinkerBoard S. I'm trying to connect a 3.2inch resistive Touch Display to SPI2. The display works with ili9341 module on SPI2 CS0. I have the touch screen of it on the SPI2@1 (CS1) but no way of getting a module or overlay dts for the ADS7846 TouchScreen. I've seen, there is a generice resisitive-adc-touch module, but I can't get it running. Using the ADS7846 on armbian with AllWinner and several other boards for many years. Works great so far. Any hints, how to get it running in such a way, that it will be there with downstream updates (meaning without having a special kernel for it)? Thanks, kind regards, Olaf
  25. I'm trying to get the RPI 7in touchscreen working on armbian with my Tinker Board. Can anyone tell me how?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines