gen2thomas

Thanks! Unfortunatelly it is not working for me. But with the tag "tinkerboard-2" now I can found more information in the forum and stay up to date.

I have done some investigation and it looks a little bit different, but it seems there is the same behaviour for character device and sysfs. If all features are off (i2c1, uart etc.) the following header pins act fine as output: 3, 5, 7, 19, 21, 22, 23, 24, 26, 27, 28, 31 not working as output, current state in round brackets: 8 (1), 10 (1), 11 (0), 12 (1), 13 (1), 15 (1), 16 (0), 18 (0), 29 (0), 32 (1), 33 (1), 35 (0), 36 (1), 37 (1), 38 (1), 40 (0) Thats the reason why my initial test with pin 36 is not working and pin 26 has worked.

@usual user thanks for the fast reply, but therefore I have also tested sysfs and the "wait" option. Today I found my fault: It seems the used 1kOhm resistor together with the meter was not strong enough to override the internal resistors. The default internal resistor setup is possibly different between the Kernels. Using a LED show the correct behavior. Today I have also used another pin (header26, asus251, chip8-line3), so I will double check this.

Hello, is there an armbian available for Tinkerboard 2 (RK3399)? Mainly I need to setup a headless system with working i2c, pwm and gpio . Thanks!

Hi, I have installed "Armbian_22.08.7_Tinkerboard_bullseye_current_5.15.74_minimal.img.xz" on a Tinkerboard (no S, with RK3288). I have tried to set the output of some header pins without success. I used both "sysfs" and "gpiod" (which uses char-devices). Test procedure, e.g. for pin 36 (gpio223): # echo "223" > /sys/class/gpio/export # cat /sys/class/gpio/gpio223/direction in # cat /sys/class/gpio/gpio223/value 0 # echo "out" > /sys/class/gpio/gpio223/direction # cat /sys/class/gpio/gpio223/direction out # echo "1" > /sys/class/gpio/gpio223/value # cat /sys/class/gpio/gpio223/value 0 # echo "0" > /sys/class/gpio/gpio223/value # cat /sys/class/gpio/gpio223/value 0 The example is for the pin36 is grounded by an resistor with 1kOhm. If the resistor is switched to 3.3V all read values are go to "1". The read values match the measured voltage (~0V for "0", ~3.3.V for "1"). The same behaviour for "gpioset 7 7=0". After this, the "gpioinfo 7" lists the line as output, like expected. Only the voltage remain unchanged (gpioget will change the line to input). With TinkerOS the same test is working (with sysfs only, because old Kernel 4.4.). Afterwards I have also tested some (or all) different options, like "sudo gpioset -m wait -D push-pull -B pull-down gpiochip7 7=0". But no success. Have I something missed to set up in the device tree? I have enabled i2c1 & i2c4 and disabled all other features (uart, spi and w1-gpio etc.) by usage of armbian-config. Thanks for your help in advance

Hello, I'm trying to use i2c (i2c1, i2c4) with fresh installed image "Armbian_21.05.1_Tinkerboard_focal_current_5.10.34.img.xz". The related overlays seems to be enabled by default: cat /boot/armbianEnv.txt verbosity=1 bootlogo=false overlay_prefix=rockchip overlays=i2c1 i2c4 spi2 spidev2 uart1 uart2 rootdev=UUID=68be20e3-93fc-4c59-95e1-0c534586d070 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u i2c is enabled by default: i2cdetect -l i2c-2 i2c rk3x-i2c I2C adapter i2c-0 i2c rk3x-i2c I2C adapter i2c-5 i2c rk3x-i2c I2C adapter What I have missed to setup? Thanks Thomas

Please read this topic, eventually this could help you:

Using the "/atc/asound.conf" for this to prevent modifications of the system file "/usr/share/alsa/cards/USB-Audio.conf" is pretty simple. * Open the files "/etc/asound.conf" and "/usr/share/alsa/cards/USB-Audio.conf" with your prefered editor. * Copy the last two sections of the "USB-Audio.conf" incl. "<confdir:pcm/iec958.conf>" to the "asound.conf" (at the end of the file). * Close the file "USB-Audio.conf". * Add "cards." before the section description e.g. "cards.USB-Audio.pcm.iec958.0 {...}". in "asound.conf" * Change the values "default 0" to "default 999" and "default 999" to "default 1". * alsactl init * "aplay -L|grep iec958" will gives only the right device iec958:CARD=OnBoard,DEV=1 The result should look something like this: Unfortunately some devices will disappear for alsa front, surround21, surround41, surround50, surround51, surround71 In case of active using such devices the copy procedure must repeated for each needed device. For simple tests with mpv generate your configuration file Add/open the file ".config/mpv/mpv.conf" with your editor. Add the next lines to it (actually HDMI is active):

For now I have only an dirty hack to force alsa to get the correct device number. Manipulate file * Open "/usr/share/alsa/cards/USB-Audio.conf" and jump to the end of the file. * In section "USB-Audio.pcm.iec958.1" set the value of "default 999" to another value, e.g. "1". "999" means "deactivated". Restart alsa and check * alsactl init * "aplay -L|grep iec958" will gives a new device iec958:CARD=OnBoard,DEV=0 iec958:CARD=OnBoard,DEV=1 Remove the wrong device and check * Open "/usr/share/alsa/cards/USB-Audio.conf" and jump to the end of the file. * In section "USB-Audio.pcm.iec958.0" set the value of "default 0" to "999". * alsactl init * "aplay -L|grep iec958" will gives only the right device iec958:CARD=OnBoard,DEV=1 Test mpv: * open command line (so you can see the messages from mpv) * start "mpv MyMovie.mkv" --> the movie plays (eventually without audio when no fiber cable is connected to your sound system) * stop video and see there is no error anymore for audio * recognize the line "AO: [alsa] 48000Hz stereo 2ch spdif-ac3" --> seems to be the correct paththrough Next step is to prevent this dirty hack with "/etc/asound.conf" or another solution for normally use. Any idea? BTW: This also works great with KODI!

Hi, I have made some progress for SPDIF paththrough. All tests are made with alsa and mpv, therefore pulsaudio was deactivated to simplify things. Remember was the problem is: aplay -L|grep iec958 iec958:CARD=OnBoard,DEV=0 Which is wrong for tinkerboard, it should be "DEV=1" Deactivate pulsaudio (use sudo if necessary) refer to KodiWiki: * open "/etc/pulse/client.conf", set autospawn from "yes" to "no" and remove comment sign ";" * reboot or just "pulseaudio --kill" Prepare mpv with configuration in users home directory: * open/create ~/.config/mpv/mpv.conf and add some content for play with: Test mpv: * make an ac3 (or another) video available for testing e.g. in users home directory * open command line (so you can see the messages from mpv) * start "mpv MyMovie.mkv" --> the movie plays without audio * stop video and see some errors from mpv marked with [ao] * modify mpv.conf for your preferred output and start the movie again --> this should work Fix the problem * see next post(s)

After some playing around with "aplay -L" and "speaker-test -D" the device "iec958" seems to be not OK. iec958:CARD=OnBoard,DEV=0 USB Audio OnBoard, USB Audio IEC958 (S/PDIF) Digital Audio Output All devices with "DEV=1" in the name, except "dsnoop" switches the LED light on while playing with speaker-test. The iec958 device only works with "-r8000" like all other devices with "DEV=0" (possible BT-devices) and the LED light keeps off. see also "cat /proc/asound/card0/stream0" --> gives the rate 8000 The test code: "speaker-test -D iec958:CARD=OnBoard,DEV=0 -c2 -r8000" This only works with r8000: "speaker-test -D dmix:CARD=OnBoard,DEV=0 -c2 -r8000" This switched the LED on: "speaker-test -D dmix:CARD=OnBoard,DEV=1 -c2" This gives sound on head phone: "speaker-test -D dmix:CARD=OnBoard,DEV=2 -c2" Is this wrong mapping, a configuration failure or an kernel issue?

I'm not able to configure armbian nor KODI with paththrough. Only stereo is available. Can I solve this (with configuration and/or rebuild of kernel and/or KODI) or is this an known limitation at the moment?

Hi, this depends on your installation procedure. In case of "apt-get install kodi" (installs v17.x krypton) you can try this site. I cleaned up my old installation first by "apt-get purge *kodi*". After install "apt-get install kodi" I get the v18.1 leia (on my lubuntu x86_64 notebook). In case of using the media-script this is also interesting to me because start without running X on armbian device: @JMCC please can you give us some explanation how to build kodi like you.

Toslink on armbian (using pulseaudio) works fine with my music center. I tried the media script and installed accelerated Kodi (it is not the latest release) from that. Now Kodi is smooth enough and SPDIF is available in audio configuration of Kodi. Next I will test it by playing an video and, when running good enough, configure it to start Kodi on system startup. This could be an alternative to LibreELEC in case of I can't get it to work with S/PDIF.

Thank you very much! Such simple solution - the red LED now was switched on. Is there the same solution using LibreELEC? Background information: Armbian actually is very slow with Kodi installation, with LibreELEC it runs smoothly but without SPDIF at the moment. Alternatively I could activate hardware acceleration for GPU in armbian, but how to do?