1-Wire works, I put the explanation at the end of this post.
Hello There,
yesterday I burned a fresh image of Armbian_20.02.5_Bananapi_buster_current_5.4.26 to replace my current setup (Armbian_5.91_Bananapi_Debian_buster_next_4.19.59) and I run into some trouble with 1-Wire. I tried everything I knew and found on the web but 1-Wire still won't work. So I need some help.
My hardware setup was not changed and it worked for at least two years. So would rule out a wiring problem at the moment. My SoC is a Banana PI M1 ( http://www.banana-pi.org/m1.html )
The strange thing is, that 1-Wire wont come up by itself, I have to run modproble after reboot to get at lease the the folders at /sys/bus/w1/* but it show no devices. And the pin (PH2) seems not to be claimed by 1-Wire anyway.
Here some output from my old system (armbianmonitor seems not to be available there)
root@bananapi:~# dtc -I dtb -O dts sun7i-a20-w1-gpio.dtbo
Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /fragment@1 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /fragment@1/__overlay__/onewire@0 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /__local_fixups__/fragment@1 has a unit name, but no reg property
Warning (unit_address_vs_reg): Node /__local_fixups__/fragment@1/__overlay__/onewire@0 has a unit name, but no reg property
/dts-v1/;
/ {
compatible = "allwinner,sun7i-a20";
fragment@0 {
target = <0xffffffff>;
__overlay__ {
w1_pins {
pins = "PI15";
function = "gpio_in";
phandle = <0x1>;
};
};
};
fragment@1 {
target-path = [2f 00];
__overlay__ {
onewire@0 {
compatible = "w1-gpio";
pinctrl-names = "default";
pinctrl-0 = <0x1>;
gpios = <0xffffffff 0x8 0xf 0x0>;
status = "okay";
};
};
};
__symbols__ {
w1_pins = "/fragment@0/__overlay__/w1_pins";
};
__fixups__ {
pio = "/fragment@0:target:0", "/fragment@1/__overlay__/onewire@0:gpios:0";
};
__local_fixups__ {
fragment@1 {
__overlay__ {
onewire@0 {
pinctrl-0 = <0x0>;
};
};
};
};
};
root@bananapi:~# cat /sys/kernel/debug/pinctrl/1c20800.pinctrl/pinmux-pins | grep PH2
pin 226 (PH2): onewire@0 1c20800.pinctrl:226 function gpio_in group PH2
I'm pretty sure I miss something, maybe someone can help me with that.
SOLVED
When I remove then can module in /boot/armbianEnv.txt 1-Wire works as expected. When I add uart2 module and reboot, 1-Wire still works. So it might have something to do with can module.
1-Wire issues with Armbian_20.02.5_Bananapi_buster_current_5.4.26 (SOLVED)
in Allwinner sunxi
Posted · Edited by bastelix
Solved
1-Wire works, I put the explanation at the end of this post.
Hello There,
yesterday I burned a fresh image of Armbian_20.02.5_Bananapi_buster_current_5.4.26 to replace my current setup (Armbian_5.91_Bananapi_Debian_buster_next_4.19.59) and I run into some trouble with 1-Wire. I tried everything I knew and found on the web but 1-Wire still won't work. So I need some help.
My hardware setup was not changed and it worked for at least two years. So would rule out a wiring problem at the moment. My SoC is a Banana PI M1 ( http://www.banana-pi.org/m1.html )
The strange thing is, that 1-Wire wont come up by itself, I have to run modproble after reboot to get at lease the the folders at /sys/bus/w1/* but it show no devices. And the pin (PH2) seems not to be claimed by 1-Wire anyway.
Here some output from my old system (armbianmonitor seems not to be available there)
I'm pretty sure I miss something, maybe someone can help me with that.
SOLVED
When I remove then can module in /boot/armbianEnv.txt 1-Wire works as expected. When I add uart2 module and reboot, 1-Wire still works. So it might have something to do with can module.