Go to advanced search

by HiassofT
Mon Dec 03, 2018 1:27 pm
Forum: General discussion
Topic: Automatically turn on TV using PIR motion sensor and IR emitter
Replies: 8
Views: 534

Re: Automatically turn on TV using PIR motion sensor and IR emitter

You can rather easily send IR commands with ir-ctl. eg use "ir-ctl -S rc5:0x1234" to send a IR signal using the rc5 protocol with address (manufacturer) 0x12 and command 0x34. BTW: I'd recommend using the latest v4l-utils version (currently 1.16.2), the version shipping with Debian/Raspbian is a bit...
by HiassofT
Mon Dec 03, 2018 10:25 am
Forum: Device Tree
Topic: Enabling the VC4 DRM/KMS driver
Replies: 7
Views: 2608

Re: Enabling the VC4 DRM/KMS driver

FYI: you don't need to patch the kernel tree to get dtb files with symbols, you can simply set DTC_FLAGS when calling make. eg ARCH=arm64 CROSS_COMPILE=... DTC_FLAGS="-@ -H epapr" make This also works on upstream kernels and I've been using that both for RPi and other SBCs for quite some time now. s...
by HiassofT
Mon Dec 03, 2018 10:13 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: PT8211 I2S ASOC driver
Replies: 14
Views: 2673

Re: PT8211 I2S ASOC driver

If you update to kernel 4.19 the spdif transmitter codec will support 32bit as well (this was added in 4.16). On kernel 4.14 you can use the pcm5102a codec that the hifiberry dac driver is using (it's basically a dummy codec as well that's only available in the RPi kernel and was added with the hifi...
by HiassofT
Sun Dec 02, 2018 12:46 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: PT8211 I2S ASOC driver
Replies: 14
Views: 2673

Re: PT8211 I2S ASOC driver

By default bcm2835-i2s sets the number of bclk cycles to the data width - 16 for 16bit samples, 24 for 24bit etc. To use a fixed amount of cycles add the dai-tdm-slot-num (must be 2, as we have 2 channes) and dai-tdm-slot-width (set it to 32 to use 32 cycles per sample) to the cpu endpoint. eg cpu_e...
by HiassofT
Wed Nov 28, 2018 4:02 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

Add a fragment like this: fragment@1 { target-path = "/"; __overlay__ { spdif_rx: spdif_rx { #address-cells = <0>; #size-cells = <0>; #sound-dai-cells = <0>; compatible = "linux,spdif-dir"; }; }; }; and then change the cs4265 reference in the sound card fragment to &spdif_rx so long, Hias
by HiassofT
Wed Nov 28, 2018 3:53 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

You still seem to have the cs4265 codec referenced, which won't load until you attach a cs4265 via I2C - you have to replace that codec with the one you intend to use. As you seem to use the PCM4202 in a fixed samplerate configuration the easiest way would be to use the (dummy) spdif receiver codec ...
by HiassofT
Wed Nov 28, 2018 12:50 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

Unfortunately my crystal ball is currently in repair so I can't tell what went wrong. Until I get it back you might help us by providing some more info: which ADC did you use, how did you wire it up, what's your DT overlay, what do you get in dmesg and vcdbg log msg (with dtdebug=1 in config.txt)? s...
by HiassofT
Wed Nov 28, 2018 12:17 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

You have to instantiate your codec (your "ADC driver") via a devicetree fragment, the example you linked to uses the "spdif transmitter" dummy codec, so you'll only get a playback device. Since you want to use the codec as clock master you need to use a proper driver, the (dummy) "spdif receiver" co...
by HiassofT
Thu Nov 22, 2018 12:26 pm
Forum: Advanced users
Topic: Symlinking /dev/ttyUSB
Replies: 3
Views: 762

Re: Symlinking /dev/ttyUSB

Yes, udev rule is the way to go. I have several USB serial adapters here in use on my main PC, often plugged in at the same time. Using the manufacturer and serial (-number) attributes is a rather reliable way to distinguish them. Run "udevadm info -a -n /dev/ttyUSBx" to see the available attributes...
by HiassofT
Tue Nov 20, 2018 2:26 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

You automatically get all alsa controls from all codecs. In the rpi-cirrus I create a bunch of additional controls, for example to expose settings and flags of the wm8804 that aren't made available by the wm8804 driver itself. In general the soundcard driver doesn't need to contain much code, it jus...
by HiassofT
Mon Nov 19, 2018 5:13 pm
Forum: General discussion
Topic: RPi 3 -> Serial port issue
Replies: 16
Views: 1269

Re: RPi 3 -> Serial port issue

- Content for /boot/cmdline.txt file dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=08a73f7d-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait Remove "console=serial0,115200" from cmdline.txt, as described in the wiki https://www.raspberrypi.org/documentation/con...
by HiassofT
Sat Nov 17, 2018 10:51 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

1- Let my clock source behave as a gateway inbetween the RPi and DAC, acting as a clock master for both sides. This involves creating a new dai_link to connect my clock source to the Justboom DAC, and then relaying information between both dai_links. Although my intuition tells me that this would b...
by HiassofT
Wed Nov 14, 2018 1:03 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: RPI 3 UART max speed
Replies: 4
Views: 1248

Re: RPI 3 UART max speed

The RPi has 2 UARTs, a PL011 and a "mini UART". In general it's best to use the PL011. The PL011 uses the ~48MHz uart clock as a base, which results in a maximum achievable baudrate of 3Mbit/sec (48MHz/16). I recently did some tests and transmitting data at 3mbit/sec looked fine on the scope. I have...
by HiassofT
Sun Nov 11, 2018 6:38 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

It's been a while since I analyzed frame sync behaviour but this sounds a lot like the channel swap I had experienced. Basically the I2S controller won' properly sync in left-justified slave mode at start. I could reproduce this with just running arecord multiple times (and a analog source with only...
by HiassofT
Thu Nov 08, 2018 10:57 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

That's the same datasheet I was looking at. The MSB mode is usually (and also in linux) called "left justified" because the MSB is immeadiately after the leading edge - which additional bclk padding after the LSB. Right justified mode has it's LSB aligned before the trailing edge and optional paddin...
by HiassofT
Thu Nov 08, 2018 8:29 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: STICKY: The I2S sound thread.
Replies: 885
Views: 407052

Re: STICKY: The I2S sound thread.

If you want to use the codec in left-justified mode you also have to use the left-justified dai format (SND_SOC_DAIFMT_LEFT_J). But, I would not recommend doing that. bcm2835-i2 only operates correctly in left-justified mode if it is the frame master. If it's the slave left-right channel swaps can o...
by HiassofT
Thu Oct 25, 2018 10:19 pm
Forum: Advanced users
Topic: SPI clock unreliable over 8MHz
Replies: 3
Views: 810

Re: SPI clock unreliable over 8MHz

Yes, I probed directly at GPIO pin 23 and used the low inductance ground connection spring on my probe, connecting to GND on GPIO pin 20. I was running LibreELEC with the TV hat driver transferring data over SPI with tvheadend accessing it, so basically no special software - you'll get the same thin...
by HiassofT
Thu Oct 25, 2018 2:12 pm
Forum: Device Tree
Topic: RTS/CTS handshake lines on UARTs
Replies: 1
Views: 3725

RTS/CTS handshake lines on UARTs

I recently needed the RTS/CTS handshake lines of the (mini)uarts in one of my projects so I wrote a bunch of device tree overlays to enable these lines. Nothing special, but might be helpful to others. You can get the dts and dtbo files from here: https://github.com/HiassofT/AtariSIO/tree/master/con...
by HiassofT
Thu Oct 25, 2018 10:15 am
Forum: Advanced users
Topic: SPI clock unreliable over 8MHz
Replies: 3
Views: 810

Re: SPI clock unreliable over 8MHz

If you see signal distortion I recommend checking your PCB layout, grounding and that you have proper connection to the SPI pins. I just checked the SPI clock signal with the TV hat attached to an RPi3, clock is running at about 30MHz and the clock signal looks perfectly fine sck.png so long, Hias
by HiassofT
Tue Oct 23, 2018 8:53 pm
Forum: Off topic discussion
Topic: Upgrades to future Pi4?
Replies: 15
Views: 2127

Re: Upgrades to future Pi4?

DarkPlatinum wrote:
Tue Oct 23, 2018 6:54 pm
I am just a bit excited as the time is nearing... Hopefully its released in early 2019. Or who knows, it could be released on new year ;)
Usually a good bet for new releases is Pi day - March 14th :-)

so long,

Hias
by HiassofT
Sat Oct 13, 2018 7:51 am
Forum: General discussion
Topic: A2 app performance class SD cards
Replies: 11
Views: 1637

Re: A2 app performance class SD cards

Does anyone know of a relatively easy to install and use benchmark for Raspbian that measures IOPS and random read/write (CLI is fine)? Use iozone3 from http://www.iozone.org/ - it's available in Debian stretch (from non-free) but seems to be missing in Raspbian so you have to compile it yourself (...
by HiassofT
Sat Sep 22, 2018 7:08 am
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: I2S Success (at last) !
Replies: 110
Views: 43304

Re: I2S Success (at last) !

Are you maybe using a DSO 138 or a similar toy to check the signals? If yes the result is expected, bclk will be about 3MHz and the DSO 138 has a maximum bandwidth of 200kHz.

so long,

Hias
by HiassofT
Mon Sep 17, 2018 6:03 pm
Forum: Troubleshooting
Topic: kernel 4.14.69-v7+ gives: kernel: [29298.960359] cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -16
Replies: 3
Views: 401

Re: kernel 4.14.69-v7+ gives: kernel: [29298.960359] cma: cma_alloc: alloc failed, req-size: 1 pages, ret: -16

run rpi-update, this is fixed in https://github.com/raspberrypi/firmware/commit/92e1937067e63285fac9b6d7863a6b5aac0c195e and in current 4.14.70 version https://github.com/raspberrypi/firmware/commit/1bd0e85c3ce7f6946f5cd4e18e7b45d50767412f See also https://github.com/raspberrypi/linux/issues/2680 so...
by HiassofT
Tue Aug 07, 2018 5:50 am
Forum: Media centres
Topic: Pi Zero W media centre
Replies: 13
Views: 5853

Re: Pi Zero W media centre

Have a look at LibreELEC https://libreelec.tv/ I regularly test this on a RPi (1) model B and kodi works fine. Keep in mind though that streaming high bitrate files over Wifi can be problematic. Media on a local USB drive or using the wired ethernet connection on a RPi 1/2/3 is more stable. so long,...
by HiassofT
Thu Aug 02, 2018 5:36 pm
Forum: Interfacing (DSI, CSI, I2C, etc.)
Topic: Interfacing with an IR output
Replies: 1
Views: 232

Re: Interfacing with an IR output

Do you have the IR transmitter or is there just a jack for connecting one? If you have an IR transmitter it's rather easy: connect a TSOPxxx IR receiver to the RPi's GPIO pins, enable the gpio-ir overlay and then test the various protocols with ir-keytable (eg ir-keytable -p nec -t). I wrote a guide...

Go to advanced search