All Activity
This stream auto-updates
- Today
-
Ming-Ta Yu started following pisound + tinker board 2
- Last week
-
In the meantime under the keyword "cmos battery" I found a bunch of offers for different button cell batteries with cables but they rarely specify which connectors are attached. Rather they name matching devices. Thus it would be great if you could name some (Asus) devices which have the same battery connector.
-
I found a datasheet for REALTEK ALC4030 codec at https://download.datasheets.com/pdfs2/2020/3/20/10/38/7/53589/rts_/manual/alc4030.pdf In this datasheet RTL ALC4030 codec supports 96 KHz sample rate microphone input. "One stereo and mono ADCs support 8/16/24/32/44.1/48/96KHz Sample Rate, 16/24-bit" I do not know why Tinker Board S R2.0 does not support 96Khz.
-
btwin started following Tinker board S R2.0 audio codec
-
According to my tests Audio RTL ALC4030U CODEC used in Tinker Board S R2.0 version does not provide 96Khz audio input. It only supports 48Khz sampling frequency. $ arecord -d 5 -f S24_3LE --device="hw:0,1" --channels=2 --rate=96000 test.mp3 Recording WAVE 'test.mp3' : Signed 24 bit Little Endian in 3bytes, Rate 96000 Hz, Stereo Warning: rate is not accurate (requested = 96000Hz, got = 48000Hz) please, try the plug plugin
-
hello @Buchhalter, 1. was the usb camera working with the previous os releases? 2. what’s the usb camera you’re using? 3. what’s the output when you execute v4l2-ctl --list-devices
-
iTink started following RTC Battery
-
And how do I connect it to the RTC battery header? Please don't tell me with a ACES 50276-002H0H1-001 plug. I read the manual but I don't have such uncommon hardware handy and a web search didn't even give me a clue where to get it.
-
iTink joined the community
-
hello @Lucas32, this guide from toradex explains what device tree overlays are and how they work: https://developer.toradex.com/linux-bsp/os-development/build-yocto/device-tree-overlays-linux/ reboot is needed after you sudo vim /boot/config.txt what is the os version? the dtbo of dac hats in the qualified vendor list are already built out/ included in the os. you might want to an os that's later than v.2.1.6 Tinker Board 2 Debian 10 V2.1.6 Description Tinker Board 2 Debian 10 V2.1.6 Tinker OS default username is "linaro", password is "linaro". Release Notes: * Changelog 1. First Kernel 4.19.x release version 2. Merged kernel security patch 3. Audio: Support JustBoom DAC HAT/Digi HAT/Amp HAT 4. Audio: Support IQaudIO Pi-DAC+/Pi-DAC Pro/Pi-Digi+ 5. Audio: Support HiFiBerry DAC+ Light/Digi+ 6. USB: Enable USB printer in kernel config 7. Config: Default enable GPIO PIN37 as S/PDIF, for Type-C DP audio function.
-
hello @btwin, yes, tinker-config is also supported for tinker board r2.0, you can download v.3.0.11 here: Tinker Board S R2.0 Debian 10 V3.0.11 to disable auto-login using tinker-config: sudo tinker-config in ther terminal prompt: 1. select "3. Boot Options" 2. select "B1 Desktop" 3. select "B3 Desktop" 4. finish the prompt will ask you to reboot the board so the new setting comes in effect. i would suggest to power off the board and re-power it again, just in case.
-
Hello everyone, The logrotate.timer does not work cyclically in Tinker Edge R Debian 10 V2.0.5. This problem causes the log file to become large and take up drive space. On this OS, logrotate is executed by systemd, not cron. I understand that the essence of the problem is that logrotate.timer is not enabled. $ systemctl status logrotate.timer * logrotate.timer - Daily rotation of log files Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset: enabled) Active: inactive (dead) Trigger: n/a Docs: man:logrotate(8) man:logrotate.conf(5) Looking at the configuration file, the timer should run once a day. $ systemctl cat logrotate.timer # /lib/systemd/system/logrotate.timer [Unit] Description=Daily rotation of log files Documentation=man:logrotate(8) man:logrotate.conf(5) [Timer] OnCalendar=daily AccuracySec=12h Persistent=true [Install] WantedBy=timers.target It appears in the timer list, but there is no execution history. $ systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES n/a n/a n/a n/a anacron.timer anacron.service n/a n/a n/a n/a apt-daily-upgrade.timer apt-daily-upgrade.service n/a n/a n/a n/a apt-daily.timer apt-daily.service n/a n/a n/a n/a fstrim.timer fstrim.service n/a n/a n/a n/a logrotate.timer logrotate.service I have tried start logrotate.timer, but this command never completes. $ sudo systemctl start logrotate.timer I have confirmed that logrotate can be run manually. $ sudo /usr/sbin/logrotate -v /etc/logrotate.conf There is an option to edit /etc/cron.daily/logrotate to ignore the systemd timer and run logrotate in cron, but I consider this a last resort. Could anyone please share the steps to start logrotate.timer? Thank you in advance for your assistance.
-
I would like to disable automatic login but I do not know how to configure it. I appreciate any help.
-
Hi, There was a Tinker Board Configuration tool in Tinker Board S. Is there an equivalent tool in the new Tinker Board S R2.0? Thanks,
-
KMO joined the community
-
Hello there, As a Linux beginner, I find it challenging to comprehend the functioning of overlays and similar concepts. I would greatly appreciate a detailed explanation of how to configure the system to recognize specific hardware, such as the HiFiBerry DAC. I have attempted various approaches, including editing the "/boot/config.txt" file based on the guidance provided in the Raspberry Pi article. However, when I execute the "aplay -l" command, it still displays "rkhdmidpsound" instead of the desired configuration. Additionally, I have noticed that in my environment, only the "hifiberry-dacplus" overlay is available in the "/boot/overlays" directory, and other overlays like "hifiberry-dac" are nowhere to be found. Is it necessary to install additional components or packages to access these missing overlays?
-
hello @Suntech, the easiest way would be using the dd command to clone everything out of the board then use flashtools such as balena etcher to flash the .img to other boards. 1. connect tinker board 2s to an ubuntu machine 2. to check if tinker board 2s has been recognised, use lsblk 3. to clone the eMMC: sudo dd if=/dev/sdb of=(filename).img bs=1G this will take a while, i've waited for around 35 minutes or so 4. once the cloning is finished, copy the .img file and use flashtools such as balenaetcher to flash the os to other boards *if you don't have an ubuntu machine, you can plug a flash drive to tinker board 2s, and save the output file to the flashdrive (please ensure it's got enough space) change #3 to: sudo dd if=/dev/sdb of=of=/dev/<USB device_name> bs=1G **if you're using a windows pc, you can use win32 disk imager: Win32 Disk Imager - Download [Official Site] 1. connect tinker board 2s to the pc 2. whilst tinker board 2s is in ums mode, use win32 disk imager to copy the emmc Using dd to clone eMMC OS.pdf
-
ADC is pcm1804, but it doesn't matter, as basically all I need is master clock signal, taken from i2s. I can test master clock adding with a DAC pcm5102. That's what I'm doing. I'm using hifiberry-dac-overlay with changes above, and in addition to usual i2s I want to get master clock on one of the pins. As I think, it can be done with adding i2s-8ch-mclk to an overlay. The question is how ? pcm 5102 connected and it sounds OK, I'm probing additional pin with oscillograph, hoping to get master clock
-
hello @giseleznev, 1. which adc are you using? do you have a product link so i can check the spec? 2. may i have a look at how the sound card is connected to tinker board 2s?
-
USB Image Tool
-
DevTricks joined the community
-
@tooz, Any ideas, please ?
-
Ming-Ta Yu started following ADC add MCLK signal
-
sin joined the community
-
For a simple test, I'm adding usage of i2s_8ch_mclk to a hifiberry dac overlay. I want to see not just i2s signal, but also master clock on pin 37 (phys num). There no master clock, just i2s for now. What am I doing wrong? Any ideas, please, help! Overlay (Linux linaro-alip 4.4.194) : #include <dt-bindings/pinctrl/rockchip.h> #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/clock/rk3399-cru.h> /dts-v1/; /plugin/; / { compatible = "rockchip,rk3399"; fragment@0 { target-path = "/spdif-sound"; __overlay__ { status = "disabled"; }; }; fragment@1 { target-path = "/hdmi-dp-sound"; __overlay__ { status = "disabled"; }; }; fragment@2 { target = <&i2s0>; __overlay__ { assigned-clocks = <&cru SCLK_I2SOUT_SRC>; assigned-clock-parents = <&cru SCLK_I2S0_8CH>; pinctrl-0 = <&i2s_8ch_mclk>, <&i2s0_8ch_bus>; status = "okay"; }; }; fragment@3 { target-path = "/"; __overlay__ { pcm5102a-codec { #sound-dai-cells = <0>; compatible = "ti,pcm5102a"; status = "okay"; }; }; }; fragment@4 { target = <&pinctrl>; __overlay__ { i2s0 { i2s_8ch_mclk: i2s-8ch-mclk { // GPIO4_A0 - RK3399 I2S_CLK rockchip,pins = <4 21 1 &pcfg_pull_none>; }; }; }; }; fragment@5 { target-path = "/sound-ext-card"; __overlay__ { compatible = "hifiberry,hifiberry-dac"; i2s-controller = <&i2s0>; status = "okay"; }; }; };
-
OK, I found: i2s_8ch_mclk: i2s-8ch-mclk { rockchip,pins = <4 0 RK_FUNC_1 &pcfg_pull_none>; }; Seems like I need this one to use in overlay to output mclk. How should I add it to a .dts file ?
-
Hi everyone, I'm currently trying to disable the boot log levels on my Tinker Edge R board running Debian 10 (Buster). I've made the following modification to the `/boot/cmdline.txt` file: console=ttyS0,115200 consoleblank=0 rootwait quiet loglevel=0 However, despite saving the changes, the boot log levels remain unchanged. I would greatly appreciate any assistance or guidance on how to achieve this. Here is some additional information about my system: - OS: Debian GNU/Linux 10 (Buster) - OS Details: [Output of `cat /etc/os-release`] ``` PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ``` Thank you in advance for your help and suggestions!
-
Hello, i tried using my Webcam on the latest Debian 10 version on my Tinker Board. Unfortunately it does not get detected as UVC device, which it should. On another Laptop it works fine in Linux. Now i dont know why uvcvideo (the Kernel driver) does not detect this cam. it is listed with lsusb. The ID is 17ef:482f Is there anything i can do to get it working? I tried to recompile the kernel as the uvcvideo is compiled into the kernel. But i dont get very far with the Tutorial from https://github.com/TinkerBoard/TinkerBoard/wiki/Developer-Guide the error i get is when trying to "sudo apt-get install gnupg-agent" The following packages have unmet dependencies: gnupg-agent : Depends : gpg-agent (>= 2.2.12-1+deb10u2) but 2.2.12-1+deb10u1 is to be installed i dont know what route to take. It seems this debian version is broken in some way. Maybe you can point me to another distribution or some solution to my webcam problem? many greetings, Buchhalter
-
Buchhalter joined the community
-
planthey joined the community
-
Basically, I need to output clock signal to one of free gpio pins. It should be synced with other clocks of i2s. How can I do it ?
-
I am trying to copy the Debian O/S installed on the Tinker Board 2S eMMC and the working software codes and settings between eMMCs to mass-produce them on the same 2S board. Please explain how.
-
hello @tooz, After changing the allocation of the build environment memory from 20GB to 24GB, "WW_Tinker_Board2-raw.img" was successfully generated. thank you!
-
MAnd joined the community
-
I got I2S working with a PCM5102 codec (DAC), but in the next board I would like to use a board which requires MCLK (256*fs). How to output MCLK as well additionally to BCLK/LRCLK?