Hi Matt,

Le 2022-05-10 à 18 h 09, Matt Flax a écrit :
That is possible.
Last time I wrote about the issue, I was trying the Octo on a RPI4.
Beause I'm using the RPI4 for another project,
I'm now trying on a RPI3 with PicorePlayer.

Test whether it is detectable on the i2c bus. You may need to disable 
the overlay in config.txt.

i2cdetect -l
The result is empty.
ls /dev/i2c* is also empty

That will list the available i2c busses. Then you can detect a bus, such 
as bus 1 :

i2cdetect 1

Do you see any indications in the output from i2cdetect that an IC is 
responding on the bus ?

Nope.

I also added "dtoverlay=audioinjector-addons" to config.txt
but dmesg tells me:
audioinjector-octo soc:sound: snd_soc_register_card failed (-517)

Is there something additional to configure in order to activate i2c devices?

Thanks for your help.

Marc

Matt


On 11/5/22 07:52, Marc Lavallée wrote:
Hi Matt,

There's no trace of the card being connected and detected, at all.
Could there be that I fried it by plugging it incorrectly?

Thanks
Marc

Le 2022-05-10 à 17 h 49, Matt Flax a écrit :
Can you report on anything you see when probing for available devices ?

aplay -l

If nothing is there, do you see anything in the system log : dmesg

Matt

On 7/5/22 08:29, Marc Lavallée via People wrote:
Hi,

I acquired an Octo a few months ago, but never tried it.
Sadly, it doesn't seem to work, and it looks like a harware issue.

I don't use a stock RPI OS, I use DietPi. But it's similar, so I added
'dtoverlay=audioinjector-addons' at the end of /boot/config.txt
No luck...

If I understand correctly how dtoverlay works,
it would looks for the octo in the /proc/device-tree folder,
so there should be some trace of "audioinjector" in it...

Is there something I'm missing?

Marc