7 7
tkaiser

quick review Banana Pi M3

Recommended Posts

btw. how can I delete one of my posts (like this one)?



Ask a moderator to delete


Sent from my iPad using Tapatalk

Share this post


Link to post
Share on other sites
12 hours ago, M@rtin said:

debian runs stable

 

There is no Debian for this board: https://www.google.com/search?q=site.www.debian.org+bananapi+m3 Kernel 3.4.38 that is glued to Debian rootfs by Banana people stable? Hmm ... will not discus that ;)

 

12 hours ago, M@rtin said:

I heard, that for many read/write processes a sd-card is not the best media (only seen from hardware-side). That's why I changed from raspbian to bananapi.

 

Saving your SD card is a stock feature of Armbian and can also be implemented on Raspberry Pi / Raspbian.

 

12 hours ago, M@rtin said:

Best would be a singleboard-computer with a native ssd slot


https://www.armbian.com/nanopc-t4/

 

Images are the same on all but each board has different boot loader, kernel and optimization package. We also have a difference between 32 and 64bit package base. But for end user Armbian is the same on all boards.

Share this post


Link to post
Share on other sites

Hi Igor,

 

I only knew the RockPi 4 and wondered about the strange mounting option for the SSD (by cable and an extra board). The NanoPC-T4 looks great. I'll order it and try it out. Thanks so much.

Share this post


Link to post
Share on other sites
8 hours ago, Shadow3561 said:

is it possible to get 1wire over gpio to run with the m3 and armbian?

Did you try adding "w1-gpio" overlay along with it "param_w1_pin" parameter in /boot/armbianEnv.txt ?

Share this post


Link to post
Share on other sites
4 hours ago, martinayotte said:

Did you try adding "w1-gpio" overlay along with it "param_w1_pin" parameter in /boot/armbianEnv.txt ?

Yes.

My armbianEnv.txt look so

 

Quote

verbosity=1
logo=disabled
console=both
disp_mode=1920x1080p60
overlay_prefix=sun8i-a83t
rootdev=UUID=180fa47b-6f2e-4289-9297-a0ffd4752601
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
overlays=w1-gpio
param_w1_pin=PH20
param_w1_pin_int_pullup=1

but has no effect.

lsmod doesnt show any w1 module.

 

I also have edited the sun8i-a83t-bananapi-m3.dtb and paste

 

Quote

w1_pins: w1_pins {

allwinner,pins = "PH10";

allwinner,function = "gpio_in"; // in (initially)

allwinner,pull = <0>; // off };

and

Quote

w1: onewire@0 {

compatible = "w1-gpio";

pinctrl-names = "default";

pinctrl-0 = <&w1_pins>;

gpios = <&pio 3 10 0>; // PH10 

status = "okay"; };

 

this also have no effect

Share this post


Link to post
Share on other sites
1 hour ago, Shadow3561 said:

overlay_prefix=sun8i-a83t

I think the reason is that there is no overlays with that prefix ...

Just to give it a try, change this to "overlay_prefix=sun8i-h3" !

Share this post


Link to post
Share on other sites
12 minutes ago, martinayotte said:

I think the reason is that there is no overlays with that prefix ...

Just to give it a try, change this to "overlay_prefix=sun8i-h3" !

 

unfortunately no success

Quote

root@bananapim3:/sys/bus/w1/devices# dmesg | grep w1
[    6.072060] w1-gpio onewire@0: gpio_request (pin) failed
[    6.072150] w1-gpio: probe of onewire@0 failed with error -22

i have modified another overlayfile to that

 

Quote

/dts-v1/;

/ {
    compatible = "allwinner,sun8i-a83t";

    fragment@0 {
        target = <0xffffffff>;

        __overlay__ {

            w1_pins {
                pins = "PL10";
                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>;
                };
            };
        };
    };
};
 

then the output of  dmesg | grep w1 is

 

Quote

root@bananapim3:~# dmesg | grep w1
[    8.324815] w1_master_driver w1_bus_master1: w1_search: max_slave_count 64 reached, will continue next search.

and  cat /sys/kernel/debug/gpio shows me

 

Quote

gpiochip1: GPIOs 0-255, parent: platform/1c20800.pinctrl, 1c20800.pinctrl:
 gpio-120 (                    |usb1-vbus           ) out hi
 gpio-166 (                    |cd                  ) in  lo
 gpio-234 (                    |soc:onewire@0       ) in  hi

gpiochip0: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl:

gpiochip2: GPIOs 414-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep:
 gpio-414 (                    |bananapi-m3:green:us) out lo
 gpio-415 (                    |bananapi-m3:blue:usr) out lo

 

in the device/tree of w1 i have devices like 00-400000000000  00-c00000000000  w1_bus_master1

but the device numbers changes every minute

Share this post


Link to post
Share on other sites
21 minutes ago, Shadow3561 said:

in the device/tree of w1 i have devices like 00-400000000000  00-c00000000000  w1_bus_master1

but the device numbers changes every minute

Try adding an external pull-up and/or try another GPIO instead of PL10

Share this post


Link to post
Share on other sites
8 hours ago, Shadow3561 said:

The result is the same as above.

Are you sure it was connected to proper GPIO ?

Try "cat /sys/kernel/debug/gpio" to see if the proper GPIO is used ...

Share this post


Link to post
Share on other sites
8 minutes ago, martinayotte said:

Are you sure it was connected to proper GPIO ?

Try "cat /sys/kernel/debug/gpio" to see if the proper GPIO is used ...

Hi,

Yes, iam sure that is a 1wire temp sensor (DS18b20 incl. 4,7kOhm resistor) connected.

The output of  cat /sys/kernel/debug/gpio is

 

Quote

gpiochip1: GPIOs 0-255, parent: platform/1c20800.pinctrl, 1c20800.pinctrl:
 gpio-120 (                    |usb1-vbus           ) out hi
 gpio-166 (                    |cd                  ) in  lo
 gpio-234 (                    |soc:onewire@0       ) out lo

gpiochip0: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl:

gpiochip2: GPIOs 414-415, parent: platform/axp20x-gpio, axp20x-gpio, can sleep:
 gpio-414 (                    |bananapi-m3:green:us) out lo
 gpio-415 (                    |bananapi-m3:blue:usr) out lo

 

Share this post


Link to post
Share on other sites
28 minutes ago, Shadow3561 said:

gpio-234 (                    |soc:onewire@0       ) out lo

So, connected on PH10 ...

I don't have other idea ... When I've faced such randomness issue, it was pointing to another floating GPIO.

Share this post


Link to post
Share on other sites

w1 works Armbian_5.83_Bananapim3_Debian_stretch_next_4.19.38.img

there

onewire@0 { compatible = "w1-gpio"; gpios = <&pio 4 4 0>; /* pin 37 */ status = "okay"; };

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
7 7