Banana Pi M3

eternalWalker · 14 May 2016 19:48

Hi,
Is this the fake?
http://forum.banana-pi.org/t/bpi-m3-new-image-dietpi-preview-bpi-m3-sd-emmc-image-2016-5-14/1685

Great from Austria
eW

k-plan · 14 May 2016 20:54

Hi eternalWalker,

Hmm … can’t say, noting hear about it. Don’t think @Fourdee is creator of this image.

Looks like all SOC from “Banana-Pi” will be supported, if it really will work.

cat /Volumes/BPI-BOOT/dietpi/.version 
117

cat /Volumes/BPI-BOOT/dietpi/dietpi-obtain_hw_model

. . .
#BPI
	if (( $(uname -a | grep -ci -m1 'BPI-') == 1 )); then
		HW_MODEL_DESCRIPTION='Banana Pi BPI-M2+ (DietPi)'
		if (( $(uname -a | grep -ci -m1 'BPI-M2-Kernel') == 1 )); then
			HW_MODEL_DESCRIPTION='Banana Pi BPI-M2 (DietPi)'
		fi
		if (( $(uname -a | grep -ci -m1 'BPI-M3-Kernel') == 1 )); then
			HW_MODEL_DESCRIPTION='Banana Pi BPI-M3 (DietPi)'
		fi
		if (( $(uname -a | grep -ci -m1 'BPI-M2P-Kernel') == 1 )); then
			HW_MODEL_DESCRIPTION='Banana Pi BPI-M2+ (DietPi)'
		fi
		#allwinner like sunxi / sun8i BPI-M3 BPI-M2+ / sun7i BPI-M1 BPI-M1+ BPI-R1 / sun6i BPI-M2
		HW_MODEL=30
. . .

cat /Volumes/BPI-BOOT/issue.txt

Raspberry Pi reference 2016-03-18
Generated using Pi-gen, https://github.com/RPi-Distro/Pi-gen, stage4

------

df -h
Filesystem                                   Size   Used  Avail Capacity   Mounted on
/dev/boot                                256Mi   48Mi  208Mi    19%       /Volumes/BPI-BOOT
/dev/root                                6.9Gi  992Mi  6.0Gi    14%       /Volumes/BPI-ROOT


ls /Volumes

/Volumes/BPI-BOOT/bananapi
/Volumes/BPI-BOOT/bananapi/berryboot.img
/Volumes/BPI-BOOT/bananapi/bpi-m2
/Volumes/BPI-BOOT/bananapi/bpi-m2p
/Volumes/BPI-BOOT/bananapi/bpi-m3
/Volumes/BPI-BOOT/bananapi/sun6i-a31s-bananapi-m2.dtb
/Volumes/BPI-BOOT/bananapi/sun6i-a31s-sinovoip-bpi-m2.dtb
/Volumes/BPI-BOOT/bananapi/sun7i-a20-bananapi-m1-plus.dtb
/Volumes/BPI-BOOT/bananapi/sun7i-a20-bananapi-r1.dtb
/Volumes/BPI-BOOT/bananapi/sun7i-a20-bananapi.dtb
/Volumes/BPI-BOOT/bananapi/uboot
/Volumes/BPI-BOOT/bananapi/uImage/Volumes/BPI-BOOT/bananapi
/Volumes/BPI-BOOT/bcm2708-rpi-b-plus.dtb
/Volumes/BPI-BOOT/bcm2708-rpi-b.dtb
/Volumes/BPI-BOOT/bcm2708-rpi-cm.dtb
/Volumes/BPI-BOOT/bcm2709-rpi-2-b.dtb
/Volumes/BPI-BOOT/bcm2710-rpi-3-b.dtb
/Volumes/BPI-BOOT/boot.scr
/Volumes/BPI-BOOT/boot.scr.org
/Volumes/BPI-BOOT/bootcode.bin
/Volumes/BPI-BOOT/cmdline.txt
/Volumes/BPI-BOOT/config.txt
/Volumes/BPI-BOOT/COPYING.linux
/Volumes/BPI-BOOT/dietpi
/Volumes/BPI-BOOT/dietpi/.dietpi-apt-get_update
/Volumes/BPI-BOOT/dietpi/.dietpi-autostart_index
/Volumes/BPI-BOOT/dietpi/.dietpi-process_tool
/Volumes/BPI-BOOT/dietpi/.hw_model
/Volumes/BPI-BOOT/dietpi/.install_stage
/Volumes/BPI-BOOT/dietpi/.installed
/Volumes/BPI-BOOT/dietpi/.network
/Volumes/BPI-BOOT/dietpi/.update_stage
/Volumes/BPI-BOOT/dietpi/.version
/Volumes/BPI-BOOT/dietpi/boot
/Volumes/BPI-BOOT/dietpi/conf
/Volumes/BPI-BOOT/dietpi/dietpi-apt-get_update
/Volumes/BPI-BOOT/dietpi/dietpi-autostart
/Volumes/BPI-BOOT/dietpi/dietpi-backup
/Volumes/BPI-BOOT/dietpi/dietpi-banner
/Volumes/BPI-BOOT/dietpi/dietpi-bugreport
/Volumes/BPI-BOOT/dietpi/dietpi-cleaner
/Volumes/BPI-BOOT/dietpi/dietpi-cloudshell
/Volumes/BPI-BOOT/dietpi/dietpi-config
/Volumes/BPI-BOOT/dietpi/dietpi-cpu_set
/Volumes/BPI-BOOT/dietpi/dietpi-cpuinfo
/Volumes/BPI-BOOT/dietpi/dietpi-cron
/Volumes/BPI-BOOT/dietpi/dietpi-external_drive_setup
/Volumes/BPI-BOOT/dietpi/dietpi-funtime
/Volumes/BPI-BOOT/dietpi/dietpi-launcher
/Volumes/BPI-BOOT/dietpi/dietpi-letsencrypt
/Volumes/BPI-BOOT/dietpi/dietpi-logclear
/Volumes/BPI-BOOT/dietpi/dietpi-morsecode
/Volumes/BPI-BOOT/dietpi/dietpi-obtain_hw_model
/Volumes/BPI-BOOT/dietpi/dietpi-process_tool
/Volumes/BPI-BOOT/dietpi/dietpi-ramdisk
/Volumes/BPI-BOOT/dietpi/dietpi-ramlog
/Volumes/BPI-BOOT/dietpi/dietpi-services
/Volumes/BPI-BOOT/dietpi/dietpi-software
/Volumes/BPI-BOOT/dietpi/dietpi-survey
/Volumes/BPI-BOOT/dietpi/dietpi-sync
/Volumes/BPI-BOOT/dietpi/dietpi-uninstall
/Volumes/BPI-BOOT/dietpi/dietpi-update
/Volumes/BPI-BOOT/dietpi/finalise
/Volumes/BPI-BOOT/dietpi/func
/Volumes/BPI-BOOT/dietpi/login
/Volumes/BPI-BOOT/dietpi/misc
/Volumes/BPI-BOOT/dietpi.txt
/Volumes/BPI-BOOT/fixup_cd.dat
/Volumes/BPI-BOOT/fixup_db.dat
/Volumes/BPI-BOOT/fixup_x.dat
/Volumes/BPI-BOOT/fixup.dat
/Volumes/BPI-BOOT/issue.txt
/Volumes/BPI-BOOT/kernel.img
/Volumes/BPI-BOOT/kernel7.img
/Volumes/BPI-BOOT/LICENCE.broadcom
/Volumes/BPI-BOOT/LICENSE.oracle
/Volumes/BPI-BOOT/overlays
/Volumes/BPI-BOOT/overlays/ads7846-overlay.dtb
/Volumes/BPI-BOOT/overlays/at86rf233-overlay.dtb
/Volumes/BPI-BOOT/overlays/bmp085_i2c-sensor-overlay.dtb
/Volumes/BPI-BOOT/overlays/dht11-overlay.dtb
/Volumes/BPI-BOOT/overlays/enc28j60-overlay.dtb
/Volumes/BPI-BOOT/overlays/gpio-ir-overlay.dtb
/Volumes/BPI-BOOT/overlays/gpio-poweroff-overlay.dtb
/Volumes/BPI-BOOT/overlays/hifiberry-amp-overlay.dtb
/Volumes/BPI-BOOT/overlays/hifiberry-dac-overlay.dtb
/Volumes/BPI-BOOT/overlays/hifiberry-dacplus-overlay.dtb
/Volumes/BPI-BOOT/overlays/hifiberry-digi-overlay.dtb
/Volumes/BPI-BOOT/overlays/hy28a-overlay.dtb
/Volumes/BPI-BOOT/overlays/hy28b-overlay.dtb
/Volumes/BPI-BOOT/overlays/i2c-gpio-overlay.dtb
/Volumes/BPI-BOOT/overlays/i2c-rtc-overlay.dtb
/Volumes/BPI-BOOT/overlays/i2c0-bcm2708-overlay.dtb
/Volumes/BPI-BOOT/overlays/i2c1-bcm2708-overlay.dtb
/Volumes/BPI-BOOT/overlays/i2s-mmap-overlay.dtb
/Volumes/BPI-BOOT/overlays/iqaudio-dac-overlay.dtb
/Volumes/BPI-BOOT/overlays/iqaudio-dacplus-overlay.dtb
/Volumes/BPI-BOOT/overlays/lirc-rpi-overlay.dtb
/Volumes/BPI-BOOT/overlays/mcp2515-can0-overlay.dtb
/Volumes/BPI-BOOT/overlays/mcp2515-can1-overlay.dtb
/Volumes/BPI-BOOT/overlays/mmc-overlay.dtb
/Volumes/BPI-BOOT/overlays/mz61581-overlay.dtb
/Volumes/BPI-BOOT/overlays/pi3-disable-bt-overlay.dtb
/Volumes/BPI-BOOT/overlays/pi3-miniuart-bt-overlay.dtb
/Volumes/BPI-BOOT/overlays/piscreen-overlay.dtb
/Volumes/BPI-BOOT/overlays/piscreen2r-overlay.dtb
/Volumes/BPI-BOOT/overlays/pitft28-capacitive-overlay.dtb
/Volumes/BPI-BOOT/overlays/pitft28-resistive-overlay.dtb
/Volumes/BPI-BOOT/overlays/pps-gpio-overlay.dtb
/Volumes/BPI-BOOT/overlays/pwm-2chan-overlay.dtb
/Volumes/BPI-BOOT/overlays/pwm-overlay.dtb
/Volumes/BPI-BOOT/overlays/qca7000-overlay.dtb
/Volumes/BPI-BOOT/overlays/raspidac3-overlay.dtb
/Volumes/BPI-BOOT/overlays/README
/Volumes/BPI-BOOT/overlays/rpi-backlight-overlay.dtb
/Volumes/BPI-BOOT/overlays/rpi-dac-overlay.dtb
/Volumes/BPI-BOOT/overlays/rpi-display-overlay.dtb
/Volumes/BPI-BOOT/overlays/rpi-ft5406-overlay.dtb
/Volumes/BPI-BOOT/overlays/rpi-proto-overlay.dtb
/Volumes/BPI-BOOT/overlays/rpi-sense-overlay.dtb
/Volumes/BPI-BOOT/overlays/sdhost-overlay.dtb
/Volumes/BPI-BOOT/overlays/sdio-overlay.dtb
/Volumes/BPI-BOOT/overlays/smi-dev-overlay.dtb
/Volumes/BPI-BOOT/overlays/smi-nand-overlay.dtb
/Volumes/BPI-BOOT/overlays/smi-overlay.dtb
/Volumes/BPI-BOOT/overlays/spi-bcm2708-overlay.dtb
/Volumes/BPI-BOOT/overlays/spi-bcm2835-overlay.dtb
/Volumes/BPI-BOOT/overlays/spi-dma-overlay.dtb
/Volumes/BPI-BOOT/overlays/tinylcd35-overlay.dtb
/Volumes/BPI-BOOT/overlays/uart1-overlay.dtb
/Volumes/BPI-BOOT/overlays/vc4-kms-v3d-overlay.dtb
/Volumes/BPI-BOOT/overlays/vga666-overlay.dtb
/Volumes/BPI-BOOT/overlays/w1-gpio-overlay.dtb
/Volumes/BPI-BOOT/overlays/w1-gpio-pullup-overlay.dtb
/Volumes/BPI-BOOT/script.bin
/Volumes/BPI-BOOT/start_cd.elf
/Volumes/BPI-BOOT/start_db.elf
/Volumes/BPI-BOOT/start_x.elf
/Volumes/BPI-BOOT/start.elf


-------

/Volumes/BPI-ROOT/bin
/Volumes/BPI-ROOT/boot
/Volumes/BPI-ROOT/dev
/Volumes/BPI-ROOT/DietPi
/Volumes/BPI-ROOT/etc
/Volumes/BPI-ROOT/home
/Volumes/BPI-ROOT/lib
/Volumes/BPI-ROOT/lost+found
/Volumes/BPI-ROOT/media
/Volumes/BPI-ROOT/mnt
/Volumes/BPI-ROOT/opt
/Volumes/BPI-ROOT/proc
/Volumes/BPI-ROOT/root
/Volumes/BPI-ROOT/run
/Volumes/BPI-ROOT/sbin
/Volumes/BPI-ROOT/selinux
/Volumes/BPI-ROOT/srv
/Volumes/BPI-ROOT/sys
/Volumes/BPI-ROOT/system
/Volumes/BPI-ROOT/tmp
/Volumes/BPI-ROOT/usr
/Volumes/BPI-ROOT/var

eternalWalker · 14 May 2016 21:26

This boot partition is actually a damper. Sinovoip ‘produces’ images for BPiM3 of material which he finds and leaves everything on the boot partition. I have already tested the Image
Great

…
“Looks like all SOC from “Banana-Pi” will be supported, if it really will work.” but…
you can’ find the “dtb” for BPiM3

Fourdee · 15 May 2016 12:11

This is news to me, so many thanks for letting us know.

I’ll try to contact the BPi team and see what their plans are for this unofficial image. As I dont currently own any BPi SBC’s, hopefully we can come to some arrangement that allows DietPi to officially support their devices.

Done, waiting for their reply: BPI-M3 new image：dietpi-preview-bpi-m3-sd-emmc.image 2016-5-14 - #5 by Fourdee - Image - banana pi single board computer open source project official forum BPI team

Failing that, I dont have the funds available at the moment, so, I could try starting a donation plea to try and cover the costs of a Banana Pi.

k-plan · 15 May 2016 12:45

Hi Fourdee,

Hmm … apart from that the course of whole action is no characterful style by sinoviop (and you not a supplicator!!)

just contact: > jasonye@banana-pi.com >

or

Banana Pi | Mehr Power für Open-Source Anwendungen – Ab jetzt gibt es keine Grenzen mehr!

marketing@allnet.de
knappe@allnet.de > (Mrs. Claudia Knappe - Feedback)
unterums@allnet.at > (Herr Thomas Unterumsberger - Marketing)

or

Contact Us – Banana Pi

order@bananapiwarehouse.com > (Frau Leuwer)

If users donating for funding reach the limit to buy one or Sinovoip/LeMark/Allnet sponsor a SoC, I will splash out some SD-Cards or a case/PSU for this project.

cu
k-plan

k-plan · 16 May 2016 08:59

… and here we go:

k-plan · 16 May 2016 09:39

Hi,

I don’t want to blur pleasant anticipation, but when looking around …

Sinovoip Banana Pi M3

Quick review of Banana Pi M3

tkaiser:

Why are you thinking about this Banana Pi M3 in the first place? It name tries to suggest it’s being compatible with the original Banana Pi but it isn’t. It’s incompatible in the following areas:

hardware: way less I/O bandwidth compared to A20 based Banana Pi/Pro/M1/M1+, based on totally different SoC

software: simply sucks, it will take months until ‘Team BPi’ might deliver OS images where everything works as it should and that can be upgraded to a newer version

support/community: sucks totally, nothing you’ll find on the net regarding Raspberry or Banana Pi applies to M2/M3 and if you ask questions in their forum you’ll either get no or most of the times wrong answers

I had to learn that people still think the well known Banana brand would mean something regarding the totally incompatible M3 even if you tell them ten times that it’s not the case. And also people seem to be impressed by (false) hardware specifications:

octa-cora CPU @ 2 GHz (no way to get there without a huge fan and resoldering a sane DC-IN solution since if thermal throttling won’t prevent the CPUs clocking at 1.8GHz or above the board will power off due to undercurrent situation since ‘Team BPi’ chose the crappiest DC-IN connector ever: Micro USB)

SATA (not true, they chose the crappiest USB-to-SATA bridge in the crappiest possible mode ever: only one of the 2 SoC’s USB host ports used to connect to an internal USB hub and connecting the USB-to-SATA bridge to this hub and not the other available USB host port the A83T features)

2 GB RAM: So what? Time to read/understand http://www.linuxatemyram.com

onboard Wi-Fi: I’ve not heard of anyone using AP6212 on the M3 in AP mode and would suspect it’s the same situation as with nearly every other onboard Wi-Fi on SBCs: crap

Considering all that and adding both software/support situation and the price of this device the conclusion should be rather simple.

. . .

This board has three main hardware issues:

crappy DC-IN connector

unable to use the SoC under heavy load since thermal throttling prevents clocking all cores at high speeds

worst USB-to-SATA bridge ever

If you’re not willing to fix issue 1) then issue 2) becomes a feature and not a bug any more. Improve heat dissipation only if you fixed DC-IN otherwise the board will shut down under full load. And also think about ignoring the ‘SATA port’ since it’s slow as hell an adds to the powering problems. Please read carefully through Sinovoip Banana Pi M3 - linux-sunxi.org and then either try to get a refund or throw it away.

Regarding OS images… they all suck and AFAIK they still haven’t implemented online updates. But who cares? The hardware bugs alone are reason enough to stay away from this device (at least for me – I still have not the slightest idea why anyone wants to buy this thing)

============================================

Sinovoip Banana Pi M2+

Quick review of Banana Pi M2+

linux-sunxi:

CPU clock speed limit

Sinovoip chose to not use a programmable voltage generator therefore VDD_CPUX is always at 1.3V which allows a maximum clockspeed of 1200 MHz. Due to yet unknown reasons all released OS images by SinoVoip are limited to 1008 MHz maximum clockspeed anyway. They also prefer to kill CPU cores when the SoC starts to overheat instead of implementing sane throttling so be prepared to end up with a single core H3 board running at 1008 MHz maximum. While this is not that much of a problem for their Linux images since you can adjust the wrong THS settings yourself

Fixed voltage / overheating

Unfortunately SinoVoip chose to use a primitive voltage regulator that feeds the H3 all the time with 1.3V. In this mode throttling is rather inefficient since temperatures do not decrease that much when only clockspeed will be reduced but not VDD_CPUX. Therefore expect severe performance problems unless you choose to apply a large heatsink and an additional fan. It’s also easy to get killed CPU cores with BSP kernel since with real heavy workloads throttling isn’t enough and the kernel driver devices to kill cores instead. Please note that with normal settings vendor OS images normally use you’ll never get killed CPU cores back. Armbian implemented an ugly corekeeper hack to overcome this and the results look then like this: The 2 last rows are SinoVoip settings taken from their BPI-M2+ github repo and the new Armbian settings.
While running the multithreaded parts of the ‘Phoronix test suite’, almost all the time max cpufreq will be throttled down to 816 MHz. An Orange Pi PC with the same cheap passive heatsink would still run at 1008 MHz or even 1104 MHz since the lower VDD_CPUX voltage at these dvfs operating points results in less emitted heat. Please be aware that currently no throttling is implemented with mainline kernel therefore you risk serious damage when running even lighter workloads on the BPi M2+ with mainline kernel!

Fourdee · 16 May 2016 13:26

Email sent

I don’t want to blur pleasant anticipation, but when looking around …

Thanks for the links, very information and some good reading.

It does seem that 8 core (octo) ARM boards all suffer with heat issues during full load, the XU4 is very similar, hitting the thermal safety limit @ 95’c after 3 seconds (4x 2ghz, 4x 1.4ghz), then throttles all cores down to 1.4ghz (8x 1.4ghz).

Elluminatus · 12 February 2018 20:35

Did you receive a banana M3? Is it possible to get an image for dietpi 6.1?
Greetings Elluminatus