I was trying to fool around with an i2c capacitive touch sensor, and ran into some strange behavior.
This is the sensor’s learning guide:
The sensors i2c address is 0x36, which I have confirmed with a RPi Pico. Before enabling any overlays (I really need to learn more about those) there is an i2c device already present with addresses 0x30 and 0x50 present.
So I know I’m kind of on my own with the CircuitPython stuff, but when using their sample script I get errors including " ValueError: No I2C device at address: 0x36 "
Running the i2c scan script provided in the above link produced:
s$ python3 i2c_scan.py
I2C addresses found: [‘0x30’, ‘0x3a’, ‘0x50’]
I2C addresses found: [‘0x30’, ‘0x3a’, ‘0x50’]
I2C addresses found: [‘0x30’, ‘0x3a’, ‘0x50’]
This makes me think CircuitPython is talking to this mysterious /dev/i2c-0 instead of my desired device. Also, no clue where 0x3a came from.
Switching to i2c-b and pins 27 & 28 solves this problem despite i2c-0 still existing, so it seems to be related to pins 3 & 5.
It’s not detrimental or anything, and I understand this is likely a CircuitPython issue not to be resolved here, but if there’s an easy and safe way to disappear this /dev/i2c-0 (I don’t even know what it is) it seems that would be far easier.
Also, what is the proper way to use an i2c device with the AML-S905X-CC? I’ve only ever used i2c devices with CircuitPython, and I’m looking to spread my wings.
Now that I’ve got home and checked it out, smbus2 seems to be just what I was looking for as I take those next few steps away from micro-controller land. Thanks for all the help!