Rock 3c i2c機能について

#1

I installed mraa using the command below.
-Start -------------------------------------
sudo apt get install libmraa2 libmraa dev libmraa java python3 mraa mraa tools y"
-End ------------------------------------

After that, GPIO was able to operate normally for both output and input.
However, the I2C function is not working properly.
GPIO header pin:
03pin: SDA2,i2C
05pin: SCL1,i2c

And I am connecting an i2c device to this bus,
-Start -------------------------------------
rock@rock-3c:~$ mraa-i2c list
Bus 0: id=03 type=linux default
Bus 1: id=04 type=linux
rock@rock-3c:~$ mraa-i2c version
Version v2.2.0 on Radxa ROCK3 Model C
rock@rock-3c:~$ mraa-i2c detect bus
-End ------------------------------------
And it seems that i2c bus detection is not being performed.

Are there any other settings required to use the i2c bus?

#2

Maybe this doesn’t work?

mraa-i2c detect bus
-> sudo mraa-i2c detect 0

※The wires are 3 pin and 5 pin, so Bus is 0.

I think this will be helpful
https://wiki.radxa.com/RockpiX/dev/libmraa

This is when MCP23017 (address is 0x20) is connected to Bus1.
mraa3

#3

Thank you for your reply.

I found out that the reason why the I2C bus was not recognized was because I did not select the surrounding area in “overlays” of “RSETUP”.

When I enabled “Enabe I2C3-M0” in overlays of RSETUP, it was recognized successfully.

— Start -------
rock@rock-3c:~/mraa$ mraa-i2c list
Bus 0: id=03 type=linux default
Bus 1: id=04 type=linux

rock@rock-3c:~/mraa$ mraa-i2c detect bus
00: – -- – -- – -- – -- – -- – -- – -- – --
Ten: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- 32 – -- – -- – -- – -- – -- – -- –
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – -- – -- – -- – -- – --
— End ---------

It was my first time playing rock, so I didn’t understand it.

I’m currently trying to check I2C bus operation using mraa in java.

A sample URL would be helpful.
thank you.

#4

Good to know the cause.

*I thought rsetup was already known.
Sorry for the unnecessary reply.