Raspberry Pi Forums

HiassofT

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 t...

HiassofT

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...

HiassofT

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...

HiassofT

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 ...

HiassofT

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 ...

HiassofT

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...

HiassofT

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)...

HiassofT

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 ...

HiassofT

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...

HiassofT

- 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/documen...

HiassofT

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...

HiassofT

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 sco...

HiassofT

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...

HiassofT

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 optio...

HiassofT

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...

HiassofT

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...

HiassofT

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...

HiassofT

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

HiassofT

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

HiassofT

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 (...

HiassofT

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

HiassofT

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...

HiassofT

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,...

HiassofT

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...

HiassofT

Glad you got it working! It could well be that the remote uses a non standard protocol - there's a lot of really odd remotes and proprietary protocols out there. In this case raw data recording/transmission is needed, and with ir-ctl you'll need to use separate files per button for that. so long, Hias

Search found 274 matches

Re: Enabling the VC4 DRM/KMS driver

Re: PT8211 I2S ASOC driver

Re: PT8211 I2S ASOC driver

Re: STICKY: The I2S sound thread.

Re: STICKY: The I2S sound thread.

Re: STICKY: The I2S sound thread.

Re: STICKY: The I2S sound thread.

Re: Symlinking /dev/ttyUSB

Re: STICKY: The I2S sound thread.

Re: RPi 3 -> Serial port issue

Re: STICKY: The I2S sound thread.

Re: RPI 3 UART max speed

Re: STICKY: The I2S sound thread.

Re: STICKY: The I2S sound thread.

Re: STICKY: The I2S sound thread.

Re: SPI clock unreliable over 8MHz

RTS/CTS handshake lines on UARTs

Re: SPI clock unreliable over 8MHz

Re: Upgrades to future Pi4?

Re: A2 app performance class SD cards

Re: I2S Success (at last) !

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

Re: Pi Zero W media centre

Re: Interfacing with an IR output

Re: Possibility for multiple instances of LIRC?