Review Banana Pi M3

[lanefu]

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

Ask a moderator to delete


Sent from my iPad using Tapatalk

[Igor]

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.

[M@rtin]

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.

[Shadow3561]

 

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

 

[martinayotte]

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 ?

[Shadow3561]

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

[martinayotte]

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" !

[Shadow3561]

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

[martinayotte]

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

[Shadow3561]

I have tryed 5 another gpio's and i have installed a pullup resistor 4,7kohm. 

The result is the same as above. 

[martinayotte]

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 ...

[Shadow3561]

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

 

[martinayotte]

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.

[atula]

w1 works Armbian_5.83_Bananapim3_Debian_stretch_next_4.19.38.img

@nkahl

onewire@0 {

            compatible = "w1-gpio";

            gpios = <&pio 4 4 0>; /* PE4 */

            status = "okay"; };

[atula]

can anyone help me how to use uart2  PB0,PB1 and uart3 PG10,PG11

uart0 works PB9, PB10

all serialpots is enabled in xxx.dtb "okay" but not work

 

edit:

all uarts works now

[JerryPenguin]

Hi,

 

with the newest image (buster 5.3) I con not boot.

It end in a bootloop.

 

Has someone the same issue?

 

Greets

[Igor]

3 hours ago, JerryPenguin said:

Has someone the same issue?

Yes its broken.

[JerryPenguin]

1 hour ago, Igor said:

Yes its broken.

Thx for your answere.

 

I will wait for a new image and try again a new and fresh installation.

 

:-)

[Igor]

5 minutes ago, JerryPenguin said:

I will wait for a new image and try again a new and fresh installation.

 

It might take several months before someone fixes the problem. I tried twice and will not try again.

[JerryPenguin]

1 hour ago, Igor said:

It might take several months before someone fixes the problem. I tried twice and will not try again.

 

That's sad.

I hope to find an old 4.4 image on my disks.

[Igor]

18 minutes ago, JerryPenguin said:

That's sad.

You are supporting support with nothing. Indeed it is sad that you expect that someone will fix and fix and fix this cheap hardware which was anyway never officially supported.

[JerryPenguin]

47 minutes ago, Igor said:

You are supporting support with nothing. 

 

1. I only asked one question and didn't ask for support or immediate bug fixing, because I know it's an OpenSource project and I'm thankful that Armbian exists.

2. I support other projects and know how difficult and pointless this is. I cannot actively support every project I use.

3. It is sad, but I have not made a demand or a bad word about this fact.

4. I've already looked around the download pages for supported hardware but can't find a suitable alternative for my requirement.

 

Maybe you can recommend a hardware (which is supported) that meets the following requirements:

- EMMC (>=8GB)
- 64bit (if already then)
- Memory (>= 2GB)
- 1000mbit Ethernet

- passive cooling, no fan

 

primarily for use as Wireguard Gateway and Pi-Hole.

I would be grateful for a tip :-)

 

Greetings

 

[Igor]

7 minutes ago, JerryPenguin said:

I would be grateful for a tip

I have seen others asking for something similar. Do some forum / site searching.
 

9 minutes ago, JerryPenguin said:

Wireguard Gateway and Pi-Hole.

Why on earth you need 2GB for this? 

We are going off topic so please find another more appropriate topic to continue with.

[JerryPenguin]

First of all thanks for your patience.

I have also just taken the chance to ask you the last question for a tip, I know it officially does not belong in this thread, so just forget it.

 

6 minutes ago, Igor said:

Why on earth you need 2GB for this?

 

Maybe Munin will come up with the newly planned SBC, and why shouldn't I take this into account when buying new hardware?

 

Greetings and thank you very much.

[Adrián Rivelli]

Hello Folks,

So, I have a bananapi m3 too, and I tried armbian focal and buster succesfully from a sd card but I couldn't boot from emmc... I used nand-stata-install,  dd and all the things aroung with no success... the output from uart from emmc is this:
 

HELLO! BOOT0 is starting!
boot0 version : 4.0.0
rtc[1] value = 0x00010000
rtc[2] value = 0x00020000
rtc[3] value = 0x00030000
DRAM DRIVE INFO: V1.1 
DRAM Type =7 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM normal_mode value: 00000001
DRAM CLK =672 MHZ
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1200 mv
ID CHECK VERSION: V0.2
using ic A83T
using axp AXP813
DRAM zq value: 00003bfb
dram size =2048
card boot number = 2
card no is 2
sdcard 2 line count 8
[mmc]: mmc driver ver 2015-04-13 16:05:39
[mmc]: ***Try SD card 2***
[mmc]: mmc 2 cmd 8 err 00000100
[mmc]: mmc 2 cmd 8 err 00000100
[mmc]: mmc 2 send if cond failed
[mmc]: mmc 2 cmd 55 err 00000100
[mmc]: mmc 2 cmd 55 err 00000100
[mmc]: mmc 2 send app cmd failed
[mmc]: ***Try MMC card 2***
[mmc]: mmc re-update_phase
[mmc]: mmc re-update_phase
[mmc]: 8bit ddr!!! 
[mmc]: mmc re-update_phase
[mmc]: MMC ver 5.0
[mmc]: SD/MMC Card: 8bit, capacity: 7456MB
[mmc]: vendor: Man 00150100 Snr 0032bbf4
[mmc]: product: 8WPD3
[mmc]: revision: 5.2
[mmc]: ***SD/MMC 2 init OK!!!***
sdcard 2 init ok
ERROR! NOT find the head of uboot.
ERROR! NOT find the head of uboot.
read all u-boot blk failed
Ready to disable icache.

PD: thanks for your great job with this

[WidHorn]

On 6/30/2020 at 2:08 AM, Adrián Rivelli said:

Hello Folks,

So, I have a bananapi m3 too, and I tried armbian focal and buster succesfully from a sd card but I couldn't boot from emmc... I used nand-stata-install,  dd and all the things aroung with no success... the output from uart from emmc is this:
 

HELLO! BOOT0 is starting!
boot0 version : 4.0.0
rtc[1] value = 0x00010000
rtc[2] value = 0x00020000
rtc[3] value = 0x00030000
DRAM DRIVE INFO: V1.1 
DRAM Type =7 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM normal_mode value: 00000001
DRAM CLK =672 MHZ
rsb_send_initseq: rsb clk 400Khz -> 3Mhz
PMU: AXP81X
ddr voltage = 1200 mv
ID CHECK VERSION: V0.2
using ic A83T
using axp AXP813
DRAM zq value: 00003bfb
dram size =2048
card boot number = 2
card no is 2
sdcard 2 line count 8
[mmc]: mmc driver ver 2015-04-13 16:05:39
[mmc]: ***Try SD card 2***
[mmc]: mmc 2 cmd 8 err 00000100
[mmc]: mmc 2 cmd 8 err 00000100
[mmc]: mmc 2 send if cond failed
[mmc]: mmc 2 cmd 55 err 00000100
[mmc]: mmc 2 cmd 55 err 00000100
[mmc]: mmc 2 send app cmd failed
[mmc]: ***Try MMC card 2***
[mmc]: mmc re-update_phase
[mmc]: mmc re-update_phase
[mmc]: 8bit ddr!!! 
[mmc]: mmc re-update_phase
[mmc]: MMC ver 5.0
[mmc]: SD/MMC Card: 8bit, capacity: 7456MB
[mmc]: vendor: Man 00150100 Snr 0032bbf4
[mmc]: product: 8WPD3
[mmc]: revision: 5.2
[mmc]: ***SD/MMC 2 init OK!!!***
sdcard 2 init ok
ERROR! NOT find the head of uboot.
ERROR! NOT find the head of uboot.
read all u-boot blk failed
Ready to disable icache.

PD: thanks for your great job with this

I'm have exactly the same problem and I have solve it.

The problem is in bootloader on eMMC. It's locked by default and armbian-config does not unlock it while install on emmc. And the old BOOT0 bootloader can't load new kernel. But we have new bootloader in armbian image. It located in /usr/lib/linux-u-boot-current-bananapim3_20.08.1_armhf/u-boot-sunxi-with-spl.bin in my case. Check your image and fix pathces in further instruction before wiping anything!

 

So:

1. Flash armbian image to SD, boot normaly and log in (through SSH or phisycal keyboard and monitor - does not matter).

2. We have two boot section on eMMC (mmcblk1boot0 and mmcblk1boot1). I don't know "who is who", so I flash both of them.

Unlock it: echo 0 | sudo tee /sys/block/mmcblk1boot0/force_ro && echo 0 | sudo tee /sys/block/mmcblk1boot1/force_ro
Two zeros in output says it unlocked.

3. Wipe it: sudo dd if=/dev/zero of=/dev/mmcblk1boot0 bs=1k count=1023 seek=1 status=noxfer && sudo dd if=/dev/zero of=/dev/mmcblk1boot1 bs=1k count=1023 seek=1 status=noxfer

4. Now flash new u-boot bootloader into boot partitions:
sudo dd if=/usr/lib/linux-u-boot-current-bananapim3_20.08.1_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk1boot0 bs=1024 seek=8 status=noxfer && sudo dd if=/usr/lib/linux-u-boot-current-bananapim3_20.08.1_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk1boot1 bs=1024 seek=8 status=noxfer

5. Run "sudo armbian-config" and go to: System>Install>Install/Update the bootloader on SD/eMMC (just in case)

 

Now you can install armbian through armbian-config as usual. After reboot bootloader partition lock by itself. You can check it's blocked by typing: cat /sys/block/mmcblk1boot0/force_ro && cat /sys/block/mmcblk1boot1/force_ro
Output must be like "1 1" in two lines.

Edited September 28, 2020 by WidHorn
Typos. Sorry, but my English is terrible.

[dolphs]

Hello,

 

Looks like meanwhile the M3 entered a matured state , at least from " compile.sh " menu - did not notice till recent.

 

Anyway was wondering if things improved running kernel 5.8 and onwards , mainly in terms of " A83T chip isn’t SATA capable and therefore the SATA port is provided by a (very) slow GL830 USB-to-SATA-bridge "

So therefore still worth buying a separate USB-to-SATA bridge if you want to connect a hard disk? bummer it is "just" 2.0 but what to expect as board is being produced from somewhere 2015 I believe.

 

In terms of octa core systems ( 1,8Ghz ) this looks still a nice pick

[RES]

On 10/24/2020 at 12:42 AM, dolphs said:

Hello,

 

Looks like meanwhile the M3 entered a matured state , at least from " compile.sh " menu - did not notice till recent.

 

 

 

 

 

Hi

 

This is what I have figured out thus far for the Banana Pi M3 development board.

I have compiled one of the three supported images via Armbian build system (./compile.sh) on my PC for my BPI M3 (v1.2) board (21.04 hirsute 5.10.43), but there are kernel modules and/or drivers missing to get it fully operational. Mainly AXP813 supply / audio codec SoC drivers, but also gpio pin control, CSI and MIPI (all related to the AXP813 I think) 

When compilation is going on you can see it is using linux-mainline-orangepi-5.10, this is the reason why for example gpio readall reads and shows only 26 pins instead of 40 pins, and the AXP813 is not fully operational because the analog-codec / hdmi won't work (ALSA won't detect any sound card/driver), dmesg shows a lot of failures.

 

So who knows how to compile these modules and/or drivers for these hardware problems? Where to start? Every little info/detail or hint is welcome. 

 

Thanks.

[fred0815]

Same here, no sound card found, but there is no support for BPI M3 at all.

I dont know how to find a solution, every hint would be great.

How did you install gpio for command gpio readall ?

Didnt work for me.

[RES]

sudo apt install wiringpi or sudo apt-get install wiringpi

 

ps. if you write this latest image (armbian_21.08.1_bpim3_hirsute_edge_5.13.12.img) on a microsd card at least one thing has changed, that HDMI audio is now supported (did not test it) aplay -l shows a HDMI audio ALSA driver. In the pavucontrol (if you have installed xorg and xfce4 desktop) mixer it shows a mono output.

 

http://armbian.hosthatch.com/archive/bananapim3/archive/Armbian_21.08.1_Bananapim3_hirsute_edge_5.13.12.img.xz