It was a doozie indeed! I had a typo in the overlay definition:
I had '12c-mux' instead of 'i2c-mix' in the ovelay of the 0x77 multiplexer.
here is the output of i2cdetect -l, after I fixed it:Note buses 22-29 for the 0x70 and 30-37 for 0x77.
Thanks for your help. I started with isolating 0x77 as suggested. When that did't work I changed a0-2 to 0x71. When that didn't work either, I tried a new MUX... and finally I opened my eyes and read what I had typed!![:D]( "Very Happy")
Case closed. BTW, Copilot suggested I use pca9548a (with an A!)
It is also worth noting that config.txt is no longer in /boot, but in
I had '12c-mux' instead of 'i2c-mix' in the ovelay of the 0x77 multiplexer.
here is the output of i2cdetect -l, after I fixed it:
Code:
Helios@HeliosRPi4:~ $ i2cdetect -li2c-1 i2c bcm2835 (i2c@7e804000) I2C adapteri2c-20 i2c fef04500.i2c I2C adapteri2c-21 i2c fef09500.i2c I2C adapteri2c-22 i2c i2c-1-mux (chan_id 0) I2C adapteri2c-23 i2c i2c-1-mux (chan_id 1) I2C adapteri2c-24 i2c i2c-1-mux (chan_id 2) I2C adapteri2c-25 i2c i2c-1-mux (chan_id 3) I2C adapteri2c-26 i2c i2c-1-mux (chan_id 4) I2C adapteri2c-27 i2c i2c-1-mux (chan_id 5) I2C adapteri2c-28 i2c i2c-1-mux (chan_id 6) I2C adapteri2c-29 i2c i2c-1-mux (chan_id 7) I2C adapteri2c-30 i2c i2c-1-mux (chan_id 0) I2C adapteri2c-31 i2c i2c-1-mux (chan_id 1) I2C adapteri2c-32 i2c i2c-1-mux (chan_id 2) I2C adapteri2c-33 i2c i2c-1-mux (chan_id 3) I2C adapteri2c-34 i2c i2c-1-mux (chan_id 4) I2C adapteri2c-35 i2c i2c-1-mux (chan_id 5) I2C adapteri2c-36 i2c i2c-1-mux (chan_id 6) I2C adapteri2c-37 i2c i2c-1-mux (chan_id 7) I2C adapterThanks for your help. I started with isolating 0x77 as suggested. When that did't work I changed a0-2 to 0x71. When that didn't work either, I tried a new MUX... and finally I opened my eyes and read what I had typed!
Case closed. BTW, Copilot suggested I use pca9548a (with an A!)
It is also worth noting that config.txt is no longer in /boot, but in
Code:
/boot/firmware/config.txtStatistics: Posted by TriLife — Wed Mar 13, 2024 3:55 pm