Most recent stable build with i2s ??
Do not confuse I2S with I2C they are very different. @Ian-Steele which I2S device are you using for Audio?
@UFD thanks . Yes, sorry of course it should be i2s not i2c (although some codecs need i2c for control) I am using a PCM 1502A DAC which I use a lot with other boards. Also have the MAX98367A mention in the article on i2s audio.
This post is deleted!
Hey @Ian-Steele , Im assuming you mean PCM5102A and the good news is that I have managed to get the PCM5102A working on the Onion.
The bad news is that you will have to build the onion image from source. This is because I2S "codecs" like the PCM5102A need to be specifically built into the kernel at compilation. You can see the list of supported "codec" devices here kernel sound
I guess its not feasible for the Omega Guys to include them all as it would significantly increase the image size. (However @Lazar-Demin should consider adding the 2 main ones found in the hobbiest space i.e MAX98367A and PCM5102A).
The Omega Onion Github repo has instructions on building an image from source. You will need to manually modify the kernel source .config to build the codec module for the PCM5102A and you will need to modify the Onion Device Tree file to enable I2S and support the PCM5102 and lastly you will have to update the ramips modules file to ensure the Onion loads this module on startup.
Now that I'm reading the high level steps, I guess it is a little involved and Im not sure of your familiarity with source building, but drop me a message if you get stuck or need clarity. happy to work through it slowly with you.
crispyoz last edited by
@UFD If you are building from source and need to configure the kernel you shouldn't be editing .config just run make kernel_menuconfig in order to modify the kernel configuration and modules. Device Drivers, Sound card support.
@crispyoz Thanks, I was not aware of that option. It is far more convenient.
(However @Lazar-Demin should consider adding the 2 main ones found in the hobbiest space i.e MAX98367A and PCM5102A).
Thanks everyone for the help/info. Thats what was confusing as I thought these were
included. Anyway, last time I did some source building a few years ago It was fairly slow and painful LOL . I guess a dynamically loaded module might be the way to go.
I'll let you know if I decide to try this.
crispyoz last edited by
@Ian-Steele Building used to be slow, taking hours sometimes. But these days I can build the curent source pool in a few minutes. My best tip is DON'T USE DOCKER!! , just install on Ubuntu 18.x. Configure what you want and then start the build and go have a coffee. Once you have completed the first build, future updates and builds are easy and complete quickly. Once you have mastered the build system it is quite trivial to add/remove features and create your customised firmware.
Spent the entire day doing this but never really got a build system
going. Spent ages correcting endless errors and various problems.
I won't waste any more time ( or anyone elses) on this.
I'm not going to use Omega for this project.
Thanks to all for trying to help.
Pavils Jurjans last edited by
I also tried very hard to get I2S sound working on Omega2, but could not. So I gave up and moved my project to Raspberry Pi Zero.
Sorry that you did not come right.
I've compiled a build for you tonight based on repo as of today. Ive added in generic support for I2S playback and record (version 0.3.2 b233).
Let me know how it goes.