uname -a : Linux nanopiair 3.4.113-sun8i #18 SMP PREEMPT Thu Jun 15 02:16:06 CEST 2017 armv7l armv7l armv7l GNU/Linux

i installed i2c-tools, libi2c-dev, python-smbus

 

but if i try like this

 

i2cdetect -y 0

   0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

 

i2cdetect -y 1

0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

 

i can't use i2c

 

gpio load i2c

->  gpio: Unable to load i2c-sunxi

 

so i tried like this

 

so i add overlays = i2c0 i2c1

/boot/armbianEnv.txt  and /etc/modprobe.d/blacklist.conf(checking i2c-bcm2708 and i2c-dev)

add from /etc/modules -> i2c-bcm2708, i2c-dev 

 

Eventually I could not find a possible i2c number

so what should i do?

 

please tell me detail ~

10 hours ago, moonki123 said:

Linux nanopiair 3.4.113-sun8i

Legacy doesn't use DT and its overlays.

To enable I2C on Legacy, you need to decompile the /boot/script.bin into FEX, edit the FEX and recompile the BIN.

(Of course, you should do a backup of /boot/script.bin in case of trouble...)

thanks your reply

you mean change this part

 

[twi0_para]

twi0_used = 1 // (enable)

twi0_scl = port:PB00<2><default><default><default> // i think Hardware pin number

twi0_sda = port:PB01<2><default><default><default> // also pin number

 

but i want to use another i2c address

now 0x48 address be used so i want to use another one

 

so your method is not match to this question so what should i do?  

0x48 is probably a on-board peripheral which UU means it is already known/used by a kernel driver.

You can still use this I2C for other peripherals with different addresses.

Which peripherals do you wish to connect ?

 

i want to use 0x68 address

How can I use the peripherals I want?

 

 

 

As I said, the 0x48 is another I2C peripheral currently present on the bus.

If you don't see your at 0x68, it is probably a wiring problem.

What is your peripherals ? Which chip number ? Which manufacturer ?

 

I do not know if the peripherals I think are right, but let me tell you.

my peripherals is mpu-6050(accleration + gyro-sensor)

Now i using H3 chip and i don't know manufacturer

my processor is  ARMv7 Processor rev 5 (v7l)

hardware is sun8i

 

i used this Wiring - git clone git://github.com/wertyzp/WiringNP
 

and my gpio -v is  

 

Copyright (c) 2012-2014 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

Banana Pro Details:
  Type: Model A, Revision: 1.2, Memory: 1024MB, Maker: LeMaker

 

That's all I know.

As I said :

18 hours ago, martinayotte said:

If you don't see your at 0x68, it is probably a wiring problem.

The MPU6050 is effectively at 0x68 (or 0x69 if AD0 is pulled high).

Since it doesn't appear in your test, the wiring is incorrect.

Did you have PullUps on your bus ?

Is the VLOGIC pin is at VCC ?

Are you using pre-fab module ?

 

no  i didn't PullUps on my bus but i  connected MPU-6050 Vcc Pin - NanoPi Neo Air Vcc 5v in...

oh... if i use NanoPi Neo Air 5v(IN) i have to change 3.3v(OUT)? or 5v(OUT)?

and i'm not using pre-fab module  

Be careful when attaching 5V devices on 3.3V buses ... You need mosfet level-shifter.

Some board provide PullUps, some other don't.

If "i2cdetect" is slow showing the devices, it proves that no pullup present.

Then add somes, usually 4K7 should be Ok !

 

Um "i2cdetect" is not showing the devices  

so it's same result ...

also A few months ago an orange pi zero succeeded in connecting i2c but now Orangepi Zero showed same result as the nanoPi neo air

Is there no other way to use another address? 

On 2017/09/28 at 3:15 AM, moonki123 said:

[twi0_para]

twi0_used = 1 // (enable)

twi0_scl = port:PB00<2><default><default><default> // i think Hardware pin number

twi0_sda = port:PB01<2><default><default><default> // also pin number

 

This is probably the cause : looking at Neo Air schematic, I2C0-SCL is on PA11 and I2C0-SDA is on PA12 ...

@moonki123

Try this

1.edit /etc/modprobe.d/fbdev-blacklist.conf and add 2 line.

blacklist pcf8591
blacklist bmp086

2.reboot system

@nopnop2002

i try like you but i can't see i2c address

it's not working

i want to try another way...

Did you fixed that I've mentioned above ?

On 10/1/2017 at 9:22 AM, martinayotte said:

looking at Neo Air schematic, I2C0-SCL is on PA11 and I2C0-SDA is on PA12 ...

 

[twi_para]
twi_port = 0
twi_scl = port:PA11<2><default><default><default>
twi_sda = port:PA12<2><default><default><default>

 

It seems to have been automatically changed since the update

 

but still i can't use 0x68

Do you have some other I2C devices to try, such EEPROM or GPIO Expander, and check if they appear correctly ?

Do you mean arm board?

I checked the mpu-6050 at Aduino_mega

But the mpu-6050 did not matter

I have raspberry pi, orangepi zero and orangepi zero plus 

but also same symptom in orangepi zero(not working I2C) 

before It worked in orangepi zero using I2C device

It seems to be caused by an update issue

 

  

23 hours ago, martinayotte said:

some other I2C devices

No, I really mean devices other than MPU-6050, like MCP23017 GPIO Expander.

If those works, then maybe the MPU is defective...