I2C not working on Orange Pi Zero2

[Yordan Yanakiev]

Hello.

I'm trying to communicate with i2c ( i've connected ADS1115 on it if this maters ), but even without anything connected on it - it shows 0x30 on it, and I am not sure how to make it works.
Please help ! 😐 

[Ryzer]

Hi Yordan,

 

Are you sure you have correctly enabled the i2c overlay on your board? what is the output of cat /boot/armbianEnv.txt? If something is showing up even with nothing apparently connected they your are likely targeting a different bus. It is possible what you are seeing is the address of the internal pmic although this normal shows up as UU.

 

Best of luck

 

Ryzer

[Yordan Yanakiev]

I've added trough the armbian-config the current, but no joy. Tried a few from ChatGPT - no joy as well.
I am not into this, since it's my first ( so far only ESP32 ), and honestly I had no idea that this requires this much stuff just to run a basic feature😐

Any help is greatly accepted.

 

This is the /boot/armbianEnv.txt :

 

verbosity=1
bootlogo=true
console=both
disp_mode=1920x1080p60
rootdev=UUID=f5d36c6f-cd6a-4f3b-a0a8-b0e85ac089e5
rootfstype=ext4
overlay_prefix=sun50i-h616
overlays=sun50i-h616-i2c0-pi sun50i-h616-i2c1-pi
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
 

[kris777]

maybe add manually in the file /boot/armbianEnv.txt the entry:

overlays=i2c0 i2c1 i2c2

 

[Ryzer]

oh right, then maybe there is a few things you can help me with in future as I still getting to grips with my esp32. Don't worry it look difficult at first but gets easier. Now I believe I know what the problem, on the overlays line modify it to i2c0-pi and i2c1-pi. This appears to be a common problem with armbian-config overlay functional. My own A10 and A20 systems also has this problem as well.

[Yordan Yanakiev]

Same as before. 

[Ryzer]

My mistake I was suggesting based on prior comments found on the Orange Pi Zero3 thread but after reviewing again it looks like the port part of the overlay is no longer necessary either so as Kris777 suggested just the interface name should hopefully now suffice. According to wiki, the main i2c interface should be i2c3: https://linux-sunxi.org/Xunlong_Orange_Pi_Zero2

Edited yesterday at 08:04 PM by Ryzer

[Yordan Yanakiev]

so, how should be looking my armbianEnv file ?

[Yordan Yanakiev]

Is this the changes ? I got still the same 😐

[TRay]

I confirm that armbian-config has problem with add ovelay prefix to overlays= please look on: 

 

https://github.com/armbian/configng/issues/592

 

So i must add manually devices in amrbinaEnv.txt and for OZPI v3 to use I2C i have

 

overlay_prefix=sun50i-h616
overlays=i2c3-ph

 

 

[Yordan Yanakiev]

Good lords. i2c3-ph is actually i2c-1which is i2c-0 since it is on pin 3 and 5.

LOL !
This is literally a total mess.

[TRay]

1 hour ago, Yordan Yanakiev said:

i2c3-ph is actually i2c-1

 

Yes in overlays i2c3-ph is on system is i2c-1 on OZPI v2/3 boards on pins 3 and 5

 

 

So you can check connected devices on pins 3 and 5 

i2cdetect -y 1

 

[Yordan Yanakiev]

seems like the config should be distinguishing by models, not by .. idk even what it is. let say 

config->OrangePi2->hardware->peripherals->i2c->i2's enumerate.