Jump to content

BananaPi M1+ i2c-0 i2c-1 disappearance when i2c-2 enabled


technik007_cz

Recommended Posts

Armbianmonitor:

Banana Pi M1+, kernel 4.19.38-sunxi, Debian stretch

I needed to get bus i2c-2 working so I went to armbian-config, ticked i2c-2. After reboot I found some information from PMU were missing, some i2c buses were removed and some added.

before

crw-rw---- 1 root i2c 89, 0 May 26 18:24 /dev/i2c-0
crw-rw---- 1 root i2c 89, 1 May 26 18:24 /dev/i2c-1

after
crw-rw---- 1 root i2c 89, 2 Jun 11 10:29 /dev/i2c-2
crw-rw---- 1 root i2c 89, 3 Jun 11 10:29 /dev/i2c-3
crw-rw---- 1 root i2c 89, 4 Jun 11 10:29 /dev/i2c-4

 

armbianEnv.txt
verbosity=0
logo=disabled
console=both
disp_mode=1920x1080p60
overlay_prefix=sun7i-a20
rootdev=UUID=078696dc-d479-4821-8b2f-47fa5c0e05f1
rootfstype=btrfs
fdtfile=sun7i-a20-bananapi-m1-plus.dtb
extraargs=net.ifnames=0 biosdevname=0
overlays=i2c2 w1-gpio
param_w1_pin=PI18
param_w1_pin_int_pullup=1
usbstoragequirks=0x152d:0x1561:u,0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x61b7:u,0x152d:0x9561:u

 

I found i2c-1 changed to i2c-4:

before

1848927564_bpi2pmu.png.a3cb833d0c3c160b0b295eff4f189ab7.png

after

251528754_bpipmu.png.67fe6adbbd61958ea10a8a579e3ecfc2.png

 

So I tried "overlays=i2c2 w1-gpio" to "overlays=i2c0 i2c1 i2c2 w1-gpio" in armbianEnv.txt but after another reboot i2c-0 bus was still missing.

crw-rw---- 1 root i2c 89, 1 Jun 11 10:58 /dev/i2c-1
crw-rw---- 1 root i2c 89, 2 Jun 11 10:58 /dev/i2c-2
crw-rw---- 1 root i2c 89, 3 Jun 11 10:58 /dev/i2c-3
crw-rw---- 1 root i2c 89, 4 Jun 11 10:58 /dev/i2c-4

 

Swapping i2c1 and i2c4 in rpimonitor config files is not big problem for me, it takes lest than 1 minute, but with i2c-0 missing I lost access to information what is undefined in the picture bellow and I do not know how can I get i2c-0 and i2c-2 working at once.


892781956_pmuafter.png.70fe86d4c75588b89b116725337ed074.png

Note: This device was connected to poor power source, this is reason why USB voltage is low(4.372V) and battery charging was going very slowly (20mA). This was not I believe affecting badly this test :-).

 

bpi2 pmu.png

Link to comment
Share on other sites

1 minute ago, technik007_cz said:
Armbianmonitor:

Banana Pi M1+, kernel 4.19.38-sunxi, Debian stretch

I needed to get bus i2c-2 working so I went to armbian-config, ticked i2c-2. After reboot I found some information from PMU were missing, some i2c buses were removed and some added.

before

crw-rw---- 1 root i2c 89, 0 May 26 18:24 /dev/i2c-0
crw-rw---- 1 root i2c 89, 1 May 26 18:24 /dev/i2c-1

after
crw-rw---- 1 root i2c 89, 2 Jun 11 10:29 /dev/i2c-2
crw-rw---- 1 root i2c 89, 3 Jun 11 10:29 /dev/i2c-3
crw-rw---- 1 root i2c 89, 4 Jun 11 10:29 /dev/i2c-4

 

armbianEnv.txt
verbosity=0
logo=disabled
console=both
disp_mode=1920x1080p60
overlay_prefix=sun7i-a20
rootdev=UUID=078696dc-d479-4821-8b2f-47fa5c0e05f1
rootfstype=btrfs
fdtfile=sun7i-a20-bananapi-m1-plus.dtb
extraargs=net.ifnames=0 biosdevname=0
overlays=i2c2 w1-gpio
param_w1_pin=PI18
param_w1_pin_int_pullup=1
usbstoragequirks=0x152d:0x1561:u,0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x61b7:u,0x152d:0x9561:u

 

I found i2c-1 changed to i2c-4:

before

1848927564_bpi2pmu.png.a3cb833d0c3c160b0b295eff4f189ab7.png

after

251528754_bpipmu.png.67fe6adbbd61958ea10a8a579e3ecfc2.png

 

So I tried "overlays=i2c2 w1-gpio" to "overlays=i2c0 i2c1 i2c2 w1-gpio" in armbianEnv.txt but after another reboot i2c-0 bus was still missing.

crw-rw---- 1 root i2c 89, 1 Jun 11 10:58 /dev/i2c-1
crw-rw---- 1 root i2c 89, 2 Jun 11 10:58 /dev/i2c-2
crw-rw---- 1 root i2c 89, 3 Jun 11 10:58 /dev/i2c-3
crw-rw---- 1 root i2c 89, 4 Jun 11 10:58 /dev/i2c-4

 

Swapping i2c1 and i2c4 in rpimonitor config files is not big problem for me, it takes lest than 1 minute, but with i2c-0 missing I lost access to information what is undefined in the picture bellow and I do not know how can I get i2c-0 and i2c-2 working at once.


892781956_pmuafter.png.70fe86d4c75588b89b116725337ed074.png

Note: This device was connected to poor power source, this is reason why USB voltage is low(4.372V) and battery charging was going very slowly (20mA). This was not I believe affecting badly this test :-).

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines