However with that said, applying the patches you suggested and building from source has allowed me to successfully play audio using I2S on build Ω-ware: 0.3.2 b222
Your help is greatly appreciated @luz
@luz , Thanks!
I have followed the instructions to build firmware from source and I have applied the two patches mentioned. however I do not see the required MAX98357A option anywhere in
Ive used the search option with no luck. is their something that I could possibly be missing in the process?
Just adding some info from onions logs in the hope it point someone in the right direction:
New Firmware (0.2.2 b200)
Fri May 24 06:36:52 2019 kern.info kernel: [ 12.122322] ralink-i2s 10000a00.i2s: mclk 480KHz Fri May 24 06:36:52 2019 kern.err kernel: [ 12.130308] max98090 0-0010: Failed to reset codec: -6 Fri May 24 06:36:52 2019 kern.err kernel: [ 12.135792] max98090 0-0010: Failed to read device revision: -1 Fri May 24 06:36:52 2019 kern.err kernel: [ 12.141799] max98090 0-0010: ASoC: failed to probe component -1 Fri May 24 06:36:52 2019 kern.err kernel: [ 12.148456] asoc-simple-card sound: ASoC: failed to instantiate card -1 Fri May 24 06:36:52 2019 kern.warn kernel: [ 12.155350] asoc-simple-card: probe of sound failed with error -1
Old Firmware (0.2.0 b193)
Tue Jul 17 23:48:36 2018 kern.info kernel: [ 11.947660] ralink-i2s 10000a00.i2s: mclk 480KHz Tue Jul 17 23:48:36 2018 kern.err kernel: [ 11.986476] max98090 0-0010: Unrecognized revision 0xff Tue Jul 17 23:48:36 2018 kern.warn kernel: [ 11.991794] max98090 0-0010: Mismatch in DT specified CODEC type. Tue Jul 17 23:48:36 2018 kern.info kernel: [ 12.000577] max98090 0-0010: use default 2.8v micbias Tue Jul 17 23:48:36 2018 kern.info kernel: [ 12.020403] asoc-simple-card sound: HiFi <-> 10000a00.i2s mapping ok
Good Day Onion Team and Community,
Can we please get an acknowledgement that I2S has not been functional since b193?
Please can you share any information that may be relevant to this issue so that the community can help debug.
Both Audio OUT and IN are required for a project that I am doing and I would really like to be on the latest Build including all the nice work you guys have been doing.
I bought a few Omega's for my projects a few months back as its price was good at $5 and $9 for the 2 and 2+ respectively.
I was shocked today to find out the price has increased more than double to $10.75 and $13.
What happened guys?? You are now in the realm of the Pi Zero W, which I would personally choose over the Omega as costs are the same.
@George-Gerber, it is there, you may miss it because it falls under 0.1.10 i.e. omega2p-v0.1.10-b160.bin
@Sergiy-Tarasov, I have had some success using what is most likely a hack and not recommended.
Then proceed with the insmod as before.
Im glad you guys found this useful!
@Jeff-Seese Thanks for the additional information on spinning up multiple I2C channels (useful when you have fixed I2C address based devices).
@Jan-Breuer I will certainly look into this. It would be amazing if "real" I2C worked on the Omega.
You should be able to use any pair of GPIO pins to act in "bitbang" i2C mode. This way you can have multiple i2C lines.
Please refer to this post in order to set this up:
So possibly a bit of a weird one.
I have a log file that my application writes to in the /root folder. After about a month I find that the onion is reporting the log file size as 91MB using:
however the disk free command
Indicates that the filesystem size for / is only 25MB.
What am I missing?
Looks like your connection to Community was lost, please wait while we try to reconnect.