Yes about sign : drivers which were used as bases of our omega simpleaudio driver seemed S16 as normal but if Andrew is sure it actually sends unsigned then that is the problem :
If the maxxxxxx driver actually uses the unsigned (weird unstandart and rare) 16bit format then we need to switch our firmware to builds using an asoc/alsa wm8960 or pcm5102 or whatever else is available as nearly ALL OTHER i2s drivers would provide us the usual/standart (i2s meaning signed) our DAC chips need.
"MCK lack" subject is not the problem here because I also use a i2s DAC chip that features an MCK generation builtin because MT7688 chip does not have any MCKout.
These 2 matter would make me much regret the former ar9331 soc chip...
There are random corruptions happening on the SPI display, where some other pixels outside of the normal rectangle are overwritten. I don't know yet if that's an issue in my driver (timing violations maybe?) or with the SPI interface, but because the entire frame is overwritten each tick, the corruption is only visible for a short amount of time.
BTW, since there is no OSC_out pin brought out to be exposed in the PCB (most won't, it is not a good idea w/o termination anyway), you might just as well put your own oscillator on the SGTL5000 codec board.
It does not say that your file does not exist - this message says that ash cannot find any executable in bin named foghorn1.wav, which should be run. The same way when you write eg. ls - ash then looks for a proper executable in bin and if no results are yielded, returns an error message.
If you want to run a file from current directory, you'd need to write ./my-file, but it only works for executables, which - clearly - a music file is not.
I dont see what the converter has to do with not finding and playing a file
BTW, this class of USB-video capture dongle simply performs NTSC (or PAL) to
720x480 4:2:2 decoding, then streams via
USB 2.0 high-speed (480Mpbs) isochronous transfer mode to the receiving side (a PC.)
Very often a low end PC cannot handle it.
Omega2 simply cannot handle this type of load. Period.
@Christoph-Zembrowski Yes, I believe that is one of the repositories that opkg consults.
Along with two others it is listed in the opkg configuration file /etc/opkg/distfeeds.conf
Once you have done a opkg update the command opkg list will list all packages available from all known feeds
Additionally, if you have obtained a ???.ipk file for a package and copied it to your Omega, you can install it using:
opkg install <path to .ipk file>
though you may possibly need to take care yourself of any other packages it may depend on
@Samuel-Ellicott That was one of the things I found.
However, I am not highly familiar with i2s :-(
I just did some Google seraches with terms like OpenWRT i2s and came across a few links that could be relevant - though I don't know enough the evaluate how good they are
Looks like your connection to Community was lost, please wait while we try to reconnect.