quick review Quick review of Banana Pi M2+
0

51 posts in this topic

Banana_Pi_M2_Plus_top.jpg

 

 

Overview:

 

SinoVoip sent me a few days ago a review sample of their new Banana Pi M2+. It's based on Allwinner's H3 SoC and tries very hard to be a 99% clone of Orange Pi Plus/PC. SinoVoip chose to stay compatible to nearly all pin mappings therefore any OS image that works on Orange Pi Plus will also work on BPi M2+ but some things need adjustments.

 

BPi M2+ features GBit Ethernet, eMMC, 2 USB host ports and one USB OTG that do not have to share bandwidth (no internal USB hub used and H3's 3rd USB host port unused unfortunately), Ampak AP6212 to provide WiFI/BT, fortunately no crappy USB-to-SATA bridge, a CSI interface to be used together with an OV5460 5MP camera module and... no programmable voltage regulator for the SoC.

 

Since it's based on the H3 SoC it's incompatible to all other Banana Pi variants and almost everything you can expect is already known. As usual you find the most recent and comprehensive information for any board based on Allwinner SoCs in the linux-sunxi wiki: http://linux-sunxi.org/Sinovoip_Banana_Pi_M2%2B

 

Compatibility:

 

The SoC's pins are routed to the externals exactly like on Orange Pi Plus/PC so it was pretty easy to create a device tree file for mainline kernel by using everything from Orange Pi Plus and replacing USB definitions with the stuff from Orange Pi PC (deleting the usb3 node since not existent) and here we are: Banana Pi M2+ is supported by mainline kernel with working USB, eMMC, GBit Ethernet and WiFi/BT already and as soon as display support and so on are available for H3 BPi M2+ benefits automagically from it.

 

Situation with kernel 3.4 is the same: In Armbian we support the board already since it was just adoption of SinoVoip's settings (and correction where they're horribly wrong -- see below when it's about performance). Since it's 'just another H3 board' software support will progress nicely and maybe the best news: You are not forced to use OS images from SinoVoip since you can rely on the community's work instead (Armbian for example).

 

Documentation and support provided by vendor:

 

To sum it up: still the usual horrible 'SinoVoip experience' we already know. They still don't get why correct information might matter. 'Documentation' is not written by engineers but instead trainees playing 'copy&paste gone wrong'. According to their website the board is either '55mm square' or 65x65mm, features 'Power led, Status led' (in reality just one led), has a 'CAN bus' (wrong for all their last SBCs, this is still moronic copy&paste from the first Banana Pi whose A20 SoC is CAN capable) and so on... you never know whether the information provided there is information or just the usual copy&paste errors they're famous for.

 

It gets even worse when you look into the vendor's so called 'documentation': There the M2+ is most of the times called M3 ("BPI-M2+ USB interface: BPI-M3 have two USB 2.0 interface on board"), the onboard WiFi chip is sometimes AP6212 and sometimes AP6181, according to the 'BPI-M2+ Quick Start' guide you can power the board through USB OTG (not true) and a '3.5mm jack audio' is available (which is also not true) and so on. And they ask you to download OS images from http://www.banan-pi.org (domain does not exist). Any more questions? If you've to rely on their information or support you're already lost since the vendor simply doesn't give a shit about stuff like this.

 

Software provided by the vendor:

 

Since SinoVoip today released an OS image for M2+ -- they call it Raspbian Jessie(debian 8) BPI-M2P (20160408) -- I thought: let's give it a try. Armbian supports this board already but maybe we missed something. OMFG, what a horrible experience! I burned this Raspbian image to a 8GB SD card and booted. Whole boot log as follows:

 

 

 

 


HELLO! BOOT0 is starting!
boot0 version : 4.0.0
boot0 commit : 368945ad3c87c1814bfe3eea5aab3ffc0e9d2d5c
 
fel_flag = 0x00000000
rtc[0] value = 0x00000000
rtc[1] value = 0x00000000
rtc[2] value = 0x00000000
rtc[3] value = 0x00000000
rtc[4] value = 0x00000000
rtc[5] value = 0x00000000
rtc[6] value = 0x00000000
rtc[7] value = 0x00000000
DRAM DRIVE INFO: V1.3
the chip id is 0x00000081
the chip id is 0x00000081
the chip id is 0x00000081
the chip id is 0x00000081
the chip id is 0x00000081
READ DQS LCDL = 001b1c1c
DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
DRAM CLK = 672 MHz
DRAM zq value: 003b3bfb
DRAM dram para1: 10f40400
DRAM dram para2: 00000000
DRAM workmode1: 000009f4
DRAM SIZE =1024 M
odt delay 
dram size =1024
card boot number = 0
card no is 0
sdcard 0 line count 4
[mmc]: mmc driver ver 2015-04-13 16:07:39
[mmc]: ***Try SD card 0***
[mmc]: SD/MMC Card: 4bit, capacity: 7580MB
[mmc]: vendor: Man 00035344 Snr 10133156
[mmc]: product: SU08G
[mmc]: revision: 8.0
[mmc]: ***SD/MMC 0 init OK!!!***
sdcard 0 init ok
The size of uboot is 000e4000.
sum=c416973f
src_sum=c416973f
Succeed in loading uboot from sdmmc flash.
Ready to disable icache.
Jump to secend Boot.
SUNXI_NORMAL_MODE   
[      0.390]e mode

U-Boot 2011.09-rc1-00000-g6e2e33f (Apr 01 2016 - 08:58:35) Allwinner Technology 

[      0.399]version: 1.1.0
[      0.402]uboot commit : 6e2e33fb1a0c2be4eaf849f6e543ad34707a03ed
 
normal mode
[      0.413]pmbus:   ready
not set main pmu id
axp_probe error
[board_vendor] vid_used not used
[      0.431]PMU: pll1 1008 Mhz,PLL6=600 Mhz
AXI=336 Mhz,AHB=200 Mhz, APB1=100 Mhz 
sid read already 
fel key new mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
normal mode
[      0.462]DRAM:  1 GiB
relocation Offset is: 35af0000
[box standby] read rtc = 0x0
[box_start_os] mag be start_type no use
user_gpio config
user_gpio ok
gic: normal or no secure os mode
workmode = 0
MMC:     0
[      0.540][mmc]: mmc driver ver 2015-04-13 14:50:00
[      0.545][mmc]: get sdc_phy_wipe fail.
[      0.549][mmc]: get sdc0 sdc_erase fail.
[      0.553][mmc]: get sdc_f_max fail,use default 50000000Hz
[      0.558][mmc]: get sdc_ex_dly_used fail,use default dly
[      0.564][mmc]: SUNXI SD/MMC: 0
[      0.577][mmc]: *Try SD card 0*
[      0.622][mmc]: CID 0x3534453 0x55303847 0x80101331 0x5600d69b
[      0.627][mmc]: mmc clk 50000000
[      0.631][mmc]: SD/MMC Card: 4bit, capacity: 7580MB
[      0.635][mmc]: boot0 capacity: 0KB,boot1 capacity: 0KB
[      0.641][mmc]: ***SD/MMC 0 init OK!!!***
[      0.645][mmc]: erase_grp_size:0x1WrBlk * 0x200 = 0x200 Byte
[      0.651][mmc]: secure_feature 0x0
[      0.654][mmc]: secure_removal_type  0x0
[      0.658]sunxi flash init ok
script config pll_de to 864 Mhz
Not Found clk pll_video1 in script 
script config pll_video to 297 Mhz
script config pll_periph0 to 600 Mhz
[boot]disp_init_tv
[DISP_TV] disp_init_tv enter g_tv_used
screen 0 do not support TV TYPE!
[BOOOT_DISP_TV] disp tv device_registered
unable to find regulator vcc-hdmi-18 from [pmu1_regu] or [pmu2_regu] 
enable power vcc-hdmi-18, ret=-1
DRV_DISP_Init end
[disk_read_fs] no the partition
error: open tv_vdid.fex, maybe it is not exist
[disk_read_fs] no the partition
error: open disp_rsl.fex, maybe it is not exist
[disk_read_fs] no the partition
error: open disp_rsl.fex, maybe it is not exist
boot_disp.auto_hpd=1
auto hpd check has 0 times!
attched ok, mgr0<-->device0, type=4, mode=4----
ready to set mode
[      1.558]finally, output_type=0x4, output_mode=0x4, screen_id=0x0, disp_para=0x404
In:    serial
Out:   serial
Err:   serial
--------fastboot partitions--------
-total partitions:6-
-name-        -start-       -size-      
boot-res    : 1000000       2000000     
env         : 3000000       1000000     
boot        : 4000000       1000000     
rootfs      : 5000000       20000000    
klog        : 25000000      1000000     
UDISK       : 26000000      0           
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_mmc
key 0
cant find rcvy value
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_mmc boot_normal
[      1.626][mmc]: MMC Device 2 not found
[      1.630][mmc]: Can not find mmc dev
[      1.634][mmc]: read first backup failed in fun sdmmc_secure_storage_read line 1854
sunxi_secstorage_read fail
get secure storage map err
check user data form private
the private part isn't exist
WORK_MODE_BOOT
adver not need show
sunxi_bmp_logo_display
f_read btr over hd12896
read byte = 2764854
[      1.800]screen_id =0, screen_width =1280, screen_height =720
[      1.806]frame buffer address 46400036
[      1.809]Hit any key to stop autoboot:  0 
[      5.065][mmc]: MMC Device 2 not found

** Invalid boot device **
[      5.081][mmc]: blkcnt should not be 0
Loaded environment from uEnv.txt
Running uenvcmd ...
Banaan Pi bpi-m2p chip: h3 Service: linux

** Unable to read "bananapi/berryboot.img" from mmc 0:1 **
## Booting kernel from Legacy Image at 48000000 ...
   Image Name:   Linux-3.4.39-02-lobo
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5246608 Bytes = 5 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
[      5.429][mmc]: MMC Device 2 not found
[      5.433][mmc]:  mmc  not find,so not exit
[      5.437]
Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   1024MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_common: ion reserve: [0x70000000, 0x80000000]!
[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.4.39-02-lobo (root@5dc305e529bb) (gcc version 4.6.3 20120201 (prerelease) (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) ) #1 SMP PREEMPT Fri Apr 1 09:06:07 UTC 2016
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: sun8i
[    0.000000] cma: CMA: reserved 256 MiB at 70000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] On node 0 totalpages: 262144
[    0.000000] free_area_init_node: node 0, pgdat c0ad24c0, node_mem_map c0bb1000
[    0.000000]   Normal zone: 1404 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 158340 pages, LIFO batch:31
[    0.000000]   HighMem zone: 900 pages used for memmap
[    0.000000]   HighMem zone: 101500 pages, LIFO batch:31
[    0.000000] script_init enter!
[    0.000000] script_init exit!
[    0.000000] PERCPU: Embedded 8 pages/cpu @c14c8000 s11840 r8192 d12736 u32768
[    0.000000] pcpu-alloc: s11840 r8192 d12736 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 259840
[    0.000000] Kernel command line: enforcing=1 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootwait init=/init vmalloc=384M loglevel=8 bootmenutimeout=10 datadev=mmcblk0p2
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] allocated 2097152 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Memory: 1024MB = 1024MB total
[    0.000000] Memory: 761924k/761924k available, 286652k reserved, 147456K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xe7800000 - 0xff000000   ( 376 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe7000000   ( 624 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0a0145c   (10214 kB)
[    0.000000]       .init : 0xc0a02000 - 0xc0a55e40   ( 336 kB)
[    0.000000]       .data : 0xc0a56000 - 0xc0ad4f38   ( 508 kB)
[    0.000000]        .bss : 0xc0ad56ec - 0xc0bb01a8   ( 875 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Additional per-CPU info printed with stalls.
[    0.000000] NR_IRQS:544
[    0.000000] Architected local timer running at 24.00MHz.
[    0.000000] Switching to timer-based delay loop
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] Console: colour dummy device 80x30
[    0.000000] console [tty1] enabled
[    0.001414] Calibrating delay loop (skipped), value calculated using timer frequency.. 4800.00 BogoMIPS (lpj=24000000)
[    0.001482] pid_max: default: 32768 minimum: 301
[    0.001847] Mount-cache hash table entries: 512
[    0.002880] Initializing cgroup subsys cpuacct
[    0.002920] Initializing cgroup subsys memory
[    0.002987] Initializing cgroup subsys devices
[    0.003019] Initializing cgroup subsys freezer
[    0.003049] Initializing cgroup subsys blkio
[    0.003091] Initializing cgroup subsys perf_event
[    0.003168] CPU: Testing write buffer coherency: ok
[    0.003240] ftrace: allocating 27613 entries in 81 pages
[    0.040292] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.040337] [sunxi_smp_prepare_cpus] enter
[    0.040387] Setting up static identity map for 0x4072d8f8 - 0x4072d950
[    0.041364] CPU1: Booted secondary processor
[    0.041364] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.041497] CPU2: Booted secondary processor
[    0.041497] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.041497] CPU3: Booted secondary processor
[    0.041497] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.050207] Brought up 4 CPUs
[    0.050321] SMP: Total of 4 processors activated (19200.00 BogoMIPS).
[    0.051046] devtmpfs: initialized
[    0.054008] wakeup src cnt is : 1. 
[    0.054033] [exstandby]leave extended_standby_enable_wakeup_src : event 0x800000
[    0.054065] [exstandby]leave extended_standby_enable_wakeup_src : wakeup_gpio_map 0x0
[    0.054097] [exstandby]leave extended_standby_enable_wakeup_src : wakeup_gpio_group 0x40
[    0.054131] sunxi pm init
[    0.054283] pinctrl core: initialized pinctrl subsystem
[    0.067287] NET: Registered protocol family 16
[    0.068166] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.068166] script_sysfs_init success
[    0.068166] sunxi_dump_init success
[    0.068166] gpiochip_add: registered GPIOs 0 to 383 on device: sunxi-pinctrl
[    0.068166] sunxi-pinctrl sunxi-pinctrl: initialized sunXi PIO driver
[    0.068166] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.068166] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.068166] [sunxi-module]: [sunxi-module.0] probe success
[    0.068166] script config pll_video to 297 Mhz
[    0.068166] script config pll_de to 864 Mhz
[    0.068166] script config pll_ve to 402 Mhz
[    0.068166] sunxi_default_clk_init
[    0.068166] try to set pll6ahb1 to 200000000
[    0.068166] try to set ahb clk source to pll6ahb1
[    0.068166] set ahb clk source to pll6ahb1
[    0.068166] try to set ahb1 to 200000000
[    0.068166] try to set apb1 to 100000000
[    0.070219] ===fe3o4==== sunxi_root_procfs_attach ret:0
[    0.080246] bio: create slab <bio-0> at 0
[    0.080370] [ARISC] :sunxi-arisc driver v1.04
[    0.091325] [ARISC] :arisc version: [v0.1.34]
[    0.091367] [sunxi-module]: arisc register success
[    0.160846] [ARISC] :sunxi-arisc driver v1.04 startup succeeded
[    0.170442] SCSI subsystem initialized
[    0.170667] usbcore: registered new interface driver usbfs
[    0.170756] usbcore: registered new interface driver hub
[    0.170801] usbcore: registered new device driver usb
[    0.170801] twi_chan_cfg()335 - [twi0] has no twi_regulator.
[    0.170801] twi_chan_cfg()335 - [twi1] has no twi_regulator.
[    0.170801] twi_chan_cfg()335 - [twi2] has no twi_regulator.
[    0.170863] Linux video capture interface: v2.00
[    0.171086] Advanced Linux Sound Architecture Driver Version 1.0.25.
[    0.171643] Bluetooth: Core ver 2.16
[    0.171696] NET: Registered protocol family 31
[    0.171722] Bluetooth: HCI device and connection manager initialized
[    0.171754] Bluetooth: HCI socket layer initialized
[    0.171777] Bluetooth: L2CAP socket layer initialized
[    0.171825] Bluetooth: SCO socket layer initialized
[    0.172068] cfg80211: Calling CRDA to update world regulatory domain
[    0.172151] Switching to clocksource arch_sys_counter
[    0.183939] FS-Cache: Loaded
[    0.184261] CacheFiles: Loaded
[    0.195772] NET: Registered protocol family 2
[    0.196074] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.196682] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.198597] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[    0.199539] TCP: Hash tables configured (established 131072 bind 65536)
[    0.199567] TCP: reno registered
[    0.199589] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.199642] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.199965] NET: Registered protocol family 1
[    0.200407] RPC: Registered named UNIX socket transport module.
[    0.200440] RPC: Registered udp transport module.
[    0.200462] RPC: Registered tcp transport module.
[    0.200483] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.201087] hw perfevents: enabled with ARMv7 Cortex_A7 PMU driver, 5 counters available
[    0.201217] sunxi_reg_init enter
[    0.201939] audit: initializing netlink socket (disabled)
[    0.201996] type=2000 audit(0.200:1): initialized
[    0.203048] highmem bounce pool size: 64 pages
[    0.203994] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.204129] NFS: Registering the id_resolver key type
[    0.204493] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.205271] NTFS driver 2.1.30 [Flags: R/W].
[    0.205416] fuse init (API version 7.18)
[    0.206182] Btrfs loaded
[    0.206304] ceph: loaded (mds proto 32)
[    0.206340] msgmni has been set to 1200
[    0.207836] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.207887] io scheduler noop registered
[    0.207908] io scheduler deadline registered
[    0.207990] io scheduler cfq registered (default)
[    0.208423] [DISP]disp_module_init
[    0.208764] cmdline,disp=
[    0.217069] [DISP] Fb_map_kernel_logo,line:927:Fb_map_kernel_logo failed!
[    0.232204] Console: switching to colour frame buffer device 160x45
[    0.248478] [DISP]disp_module_init finish
[    0.248821] sw_uart_get_devinfo()1503 - uart0 has no uart_regulator.
[    0.249006] sw_uart_get_devinfo()1503 - uart1 has no uart_regulator.
[    0.249188] sw_uart_get_devinfo()1503 - uart3 has no uart_regulator.
[    0.249840] uart0: ttyS0 at MMIO 0x1c28000 (irq = 32) is a SUNXI
[    0.250088] sw_uart_pm()890 - uart0 clk is already enable
[    0.250254] sw_console_setup()1233 - console setup baud 115200 parity n bits 8, flow n
[    0.442897] console [ttyS0] enabled
[    0.582094] uart1: ttyS1 at MMIO 0x1c28400 (irq = 33) is a SUNXI
[    0.770380] uart3: ttyS3 at MMIO 0x1c28c00 (irq = 35) is a SUNXI
[    0.770918] sunxi_cmatest_init enter
[    0.770959] sunxi_cmatest_init success
[    0.771142] sunxi_di_init get di_by_pass err!
[    0.775533] loop: module loaded
[    0.775558] Loading iSCSI transport class v2.0-870.
[    0.775875] iscsi: registered transport (tcp)
[    0.910591] sunxi_spi_chan_cfg()1355 - [spi-0] has no spi_regulator.
[    1.079459] sunxi_spi_chan_cfg()1355 - [spi-1] has no spi_regulator.
[    1.244372] spi spi0: master is unqueued, this is deprecated
[    1.430382] tun: Universal TUN/TAP device driver, 1.6
[    1.430390] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.431630] PPP generic driver version 2.4.2
[    1.431821] PPP BSD Compression module registered
[    1.431830] PPP Deflate Compression module registered
[    1.432602] PPP MPPE Compression module registered
[    1.432614] NET: Registered protocol family 24
[    1.432652] PPTP driver version 0.8.5
[    1.432920] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.453003] sunxi-ehci sunxi-ehci.1: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.453036] sunxi-ehci sunxi-ehci.1: new USB bus registered, assigned bus number 1
[    1.574869] sunxi-ehci sunxi-ehci.1: irq 104, io mem 0xf1c1a000
[    1.760051] sunxi-ehci sunxi-ehci.1: USB 0.0 started, EHCI 1.00
[    1.936236] hub 1-0:1.0: USB hub found
[    2.030151] hub 1-0:1.0: 1 port detected
[    2.059198] sunxi-ehci sunxi-ehci.2: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.072617] sunxi-ehci sunxi-ehci.2: new USB bus registered, assigned bus number 2
[    2.086063] sunxi-ehci sunxi-ehci.2: irq 106, io mem 0xf1c1b000
[    2.110031] sunxi-ehci sunxi-ehci.2: USB 0.0 started, EHCI 1.00
[    2.120987] ehci_irq: highspeed device connect
[    2.130971] hub 2-0:1.0: USB hub found
[    2.139544] hub 2-0:1.0: 1 port detected
[    2.168668] sunxi-ehci sunxi-ehci.3: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.182156] sunxi-ehci sunxi-ehci.3: new USB bus registered, assigned bus number 3
[    2.195645] sunxi-ehci sunxi-ehci.3: irq 108, io mem 0xf1c1c000
[    2.220041] sunxi-ehci sunxi-ehci.3: USB 0.0 started, EHCI 1.00
[    2.231567] hub 3-0:1.0: USB hub found
[    2.240134] hub 3-0:1.0: 1 port detected
[    2.249266] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.280729] sunxi-ohci sunxi-ohci.1: SW USB2.0 'Open' Host Controller (OHCI) Driver
[    2.293868] sunxi-ohci sunxi-ohci.1: new USB bus registered, assigned bus number 4
[    2.306892] sunxi-ohci sunxi-ohci.1: irq 105, io mem 0xf1c1a400
[    2.374533] hub 4-0:1.0: USB hub found
[    2.383127] hub 4-0:1.0: 1 port detected
[    2.412177] sunxi-ohci sunxi-ohci.2: SW USB2.0 'Open' Host Controller (OHCI) Driver
[    2.425270] sunxi-ohci sunxi-ohci.2: new USB bus registered, assigned bus number 5
[    2.438262] sunxi-ohci sunxi-ohci.2: irq 107, io mem 0xf1c1b400
[    2.460056] usb 2-1: new high-speed USB device number 2 using sunxi-ehci
[    2.504539] hub 5-0:1.0: USB hub found
[    2.513373] hub 5-0:1.0: 1 port detected
[    2.542715] sunxi-ohci sunxi-ohci.3: SW USB2.0 'Open' Host Controller (OHCI) Driver
[    2.556008] sunxi-ohci sunxi-ohci.3: new USB bus registered, assigned bus number 6
[    2.569188] sunxi-ohci sunxi-ohci.3: irq 109, io mem 0xf1c1c400
[    2.629502] hub 2-1:1.0: USB hub found
[    2.638494] hub 2-1:1.0: 3 ports detected
[    2.651341] ehci_irq: highspeed device disconnect
[    2.652167] hub 6-0:1.0: USB hub found
[    2.652186] hub 6-0:1.0: 1 port detected
[    2.652576] Initializing USB Mass Storage driver...
[    2.652796] usbcore: registered new interface driver usb-storage
[    2.652804] USB Mass Storage support registered.
[    2.652863] usbcore: registered new interface driver ums-alauda
[    2.652910] usbcore: registered new interface driver ums-cypress
[    2.652960] usbcore: registered new interface driver ums-datafab
[    2.653005] usbcore: registered new interface driver ums_eneub6250
[    2.653057] usbcore: registered new interface driver ums-freecom
[    2.653105] usbcore: registered new interface driver ums-isd200
[    2.653159] usbcore: registered new interface driver ums-jumpshot
[    2.653204] usbcore: registered new interface driver ums-karma
[    2.653252] usbcore: registered new interface driver ums-onetouch
[    2.653311] usbcore: registered new interface driver ums-realtek
[    2.653360] usbcore: registered new interface driver ums-sddr09
[    2.653414] usbcore: registered new interface driver ums-sddr55
[    2.653460] usbcore: registered new interface driver ums-usbat
[    2.653585] usbcore: registered new interface driver usbserial
[    2.653594] usbserial: USB Serial Driver core
[    2.653649] usbcore: registered new interface driver option
[    2.653695] USB Serial support registered for GSM modem (1-port)
[    2.654318] file system registered
[    2.822987] usb 2-1: USB disconnect, device number 2
[    2.823110] hub 2-1:1.0: hub_port_status failed (err = -19)
[    2.823122] hub 2-1:1.0: hub_port_status failed (err = -19)
[    2.823132] hub 2-1:1.0: hub_port_status failed (err = -19)
[    2.823142] hub 2-1:1.0: activate --> -19
[    2.838545] ehci_irq: highspeed device connect
[    2.952255] android_usb gadget: Mass Storage Function, version: 2009/09/11
[    2.963439] android_usb gadget: Number of LUNs=3
[    2.972000]  lun0: LUN: removable file: (no medium)
[    2.981066]  lun1: LUN: removable file: (no medium)
[    2.989826]  lun2: LUN: removable file: (no medium)
[    2.998886] android_usb gadget: android_usb ready
[    3.007640]  uinput result 0 , vmouse_init 
[    3.016137] mousedev: PS/2 mouse device common for all mice
[    3.025814] sunxikbd_init failed. 
[    3.032818] ls_fetch_sysconfig_para: type err  device_used = 0. 
[    3.042719] =========script_get_err============
[    3.050944] ltr_init: ls_fetch_sysconfig_para err.
[    3.059979] sunxi-rtc sunxi-rtc: rtc core: registered sunxi-rtc as rtc0
[    3.070638] i2c /dev entries driver
[    3.078179] IR RC5(x) protocol handler initialized
[    3.086906] sunxi tsc version 0.1 
[    3.093995] tscdev_init: tsc driver is disabled
[    3.102461] sunxi cedar version 0.1 
[    3.109768] [cedar]: install start!!!
[    3.117324] [cedar]: install end!!!
[    3.124415] sunxi_wdt_init_module: sunxi WatchDog Timer Driver v1.0
[    3.134795] sunxi_wdt_probe: devm_ioremap return wdt_reg 0xf1c20ca0, res->start 0x01c20ca0, res->end 0x01c20cbf
[    3.146241] sunxi_wdt_probe: initialized (g_timeout=16s, g_nowayout=0)
[    3.160525] wdt_enable, write reg 0xf1c20cb8 val 0x00000000
[    3.170379] timeout_to_interv, line 167
[    3.178310] interv_to_timeout, line 189
[    3.186283] wdt_set_tmout, write 0x000000b0 to mode reg 0xf1c20cb8, actual timeout 16 sec
[    3.199729] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
[    3.213312] Bluetooth: HCI UART driver ver 2.2
[    3.222408] Bluetooth: HCI H4 protocol initialized
[    3.231984] [cpu_freq] ERR:get cpu extremity frequency from sysconfig failed, use max_freq
[    3.240047] usb 2-1: new high-speed USB device number 3 using sunxi-ehci
[    3.257847] [mmc]: SD/MMC/SDIO Host Controller Driver(v1.111 2015-4-13 15:24) Compiled in Apr  1 2016 at 09:02:54
[    3.274099] [mmc]: get mmc0's sdc_power is null!
[    3.284065] [mmc]: get mmc1's sdc_power is null!
[    3.293941] [mmc]: get mmc1's 2xmode ok, val = 1
[    3.303769] [mmc]: get mmc1's ddrmode ok, val = 1
[    3.313658] [mmc]: get mmc2's sdc_power is null!
[    3.323374] [mmc]: get mmc2's 2xmode ok, val = 1
[    3.333044] [mmc]: get mmc2's ddrmode ok, val = 1
[    3.342776] [mmc]: MMC host used card: 0x7, boot card: 0x5, io_card 2
[    3.356310] [mmc]: sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.372080] [mmc]: sdc0 set ios: clk 0Hz bm PP pm UP vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.386979] [mmc]: sdc2 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.388209] [mmc]: sdc0 power_supply is null
[    3.399773] hub 2-1:1.0: USB hub found
[    3.399871] hub 2-1:1.0: 3 ports detected
[    3.400058] [mmc]: sdc0 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.420862] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 0 err, cmd 52,  RTO !!
[    3.421711] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 0 err, cmd 52,  RTO !!
[    3.421748] [mmc]: sdc0 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.424263] [mmc]: sdc0 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.425724] *******************Try sdio*******************
[    3.426542] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 0 err, cmd 5,  RTO !!
[    3.427379] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 0 err, cmd 5,  RTO !!
[    3.428217] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 0 err, cmd 5,  RTO !!
[    3.429055] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 0 err, cmd 5,  RTO !!
[    3.429084] *******************Try sd *******************
[    3.429739] [mmc]: sdc0 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.429867] [mmc]: sdc0 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.432375] [mmc]: sdc0 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.491540] [mmc]: sdc0 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.495949] [mmc]: sdc0 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing SD-HS(SDR25) dt B
[    3.496044] [mmc]: sdc0 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing SD-HS(SDR25) dt B
[    3.496193] [mmc]: sdc0 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[    3.496289] mmc0: new high speed SDHC card at address e624
[    3.496808] mmcblk0: mmc0:e624 SU08G 7.40 GiB 
[    3.498101]  mmcblk0: p1 p2
[    3.498842] *******************sd init ok*******************
[    3.621140] [mmc]: sdc2 set ios: clk 0Hz bm PP pm UP vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.622677] [mmc]: sdc2 power_supply is null
[    3.640056] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.660867] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 52,  RTO !!
[    3.661708] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 52,  RTO !!
[    3.661743] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.664251] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.666176] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 8,  RTO !!
[    3.666207] *******************Try sdio*******************
[    3.667024] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 5,  RTO !!
[    3.667861] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 5,  RTO !!
[    3.668699] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 5,  RTO !!
[    3.669536] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 5,  RTO !!
[    3.669566] *******************Try sd *******************
[    3.670384] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 55,  RTO !!
[    3.671221] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 55,  RTO !!
[    3.672056] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 55,  RTO !!
[    3.672891] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 2 err, cmd 55,  RTO !!
[    3.672917] *******************Try mmc*******************
[    3.672929] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.673369] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.673490] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.673608] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.676105] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.680193] usb 2-1.2: new low-speed USB device number 4 using sunxi-ehci
[    3.720323] [mmc]: sdc1 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.791258] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.803250] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.803700] [mmc]: sdc2 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.803827] [mmc]: sdc2 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    3.803943] [mmc]: sdc2 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing MMC-HS(SDR20) dt B
[    3.804029] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing MMC-HS(SDR20) dt B
[    3.804146] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing MMC-HS(SDR20) dt B
[    3.804259] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing MMC-HS(SDR20) dt B
[    3.804426] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing MMC-HS(SDR20) dt B
[    3.804534] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B
[    3.804621] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B
[    3.804728] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B
[    3.804839] mmc1: new high speed DDR MMC card at address 0001
[    3.805353] mmcblk1: mmc1:0001 8WMB3R 7.28 GiB 
[    3.805608] mmcblk1boot0: mmc1:0001 8WMB3R partition 1 4.00 MiB
[    3.805836] mmcblk1boot1: mmc1:0001 8WMB3R partition 2 4.00 MiB
[    3.810047]  mmcblk1: p1
[    3.811144] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B
[    3.813444]  mmcblk1boot1: unknown partition table
[    3.814144] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B
[    3.814938]  mmcblk1boot0: unknown partition table
[    3.815167] *******************mmc init ok *******************
[    4.018314] sunxi_leds_fetch_sysconfig_para script_parser_fetch "leds_para" leds_used = -1063118592
[    4.090308] usb 2-1.3: new low-speed USB device number 5 using sunxi-ehci
[    4.151952] =========script_get_err============
[    4.298654] usbcore: registered new interface driver usbhid
[    4.374310] usbhid: USB HID core driver
[    4.387296] asoc: sndcodec <-> sunxi-codec mapping ok
[    4.400624] asoc: sndhdmi <-> sunxi-hdmiaudio.0 mapping ok
[    4.411667] oprofile: using arm/armv7-ca7
[    4.420301] u32 classifier
[    4.427314]     Actions configured
[    4.435071] Netfilter messages via NETLINK v0.30.
[    4.444323] nf_conntrack version 0.5.0 (16001 buckets, 64004 max)
[    4.455646] ctnetlink v0.93: registering with nfnetlink.
[    4.465791] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[    4.477878] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[    4.488976] xt_time: kernel timezone is -0000
[    4.498199] IPv4 over IPv4 tunneling driver
[    4.507572] gre: GRE over IPv4 demultiplexor driver
[    4.517363] ip_gre: GRE over IPv4 tunneling driver
[    4.527821] ip_tables: (C) 2000-2006 Netfilter Core Team
[    4.538508] arp_tables: (C) 2002 David S. Miller
[    4.548141] TCP: cubic registered
[    4.556130] Initializing XFRM netlink socket
[    4.565366] NET: Registered protocol family 10
[    4.575872] Mobile IPv6
[    4.582883] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    4.593503] IPv6 over IPv4 tunneling driver
[    4.603740] NET: Registered protocol family 17
[    4.613244] NET: Registered protocol family 15
[    4.622894] Bluetooth: RFCOMM TTY layer initialized
[    4.632945] Bluetooth: RFCOMM socket layer initialized
[    4.643319] Bluetooth: RFCOMM ver 1.11
[    4.652123] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.662781] Bluetooth: BNEP filters: protocol multicast
[    4.673393] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    4.684862] L2TP core driver, V2.0
[    4.693337] PPPoL2TP kernel driver, V2.0
[    4.702366] L2TP IP encapsulation support (L2TPv3)
[    4.712531] L2TP netlink interface
[    4.721037] L2TP ethernet pseudowire support (L2TPv3)
[    4.731312] Registering the dns_resolver key type
[    4.741206] libceph: loaded (mon/osd proto 15/24, osdmap 5/6 5/6)
[    4.752877] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[    4.766028] ThumbEE CPU extension supported.
[    4.775337] Registering SWP/SWPB emulation handler
[    4.786073] cmdline,disp=
[    4.793340] [HDMI] power vcc-hdmi-18
[    4.832377] sunxi-rtc sunxi-rtc: setting system clock to 1970-01-01 00:00:10 UTC (10)
[    4.845529] ths_fetch_sysconfig_para: type err  device_used = 1. 
[    4.858162] CPU Budget:Register notifier
[    4.866938] CPU Budget:register Success
[    4.875521] sunxi-budget-cooling sunxi-budget-cooling: Cooling device registered: thermal-budget-0
[    4.893195] [rf_pm]: Did not config module_power0 in sys_config
[    4.904415] [rf_pm]: Did not config module_power1 in sys_config
[    4.915532] [rf_pm]: Did not config module_power2 in sys_config
[    4.926576] [rf_pm]: Did not config module_power3 in sys_config
[    4.937514] [rf_pm]: mod has no chip_en gpio
[    4.946549] [rf_pm]: regulator on.
[    4.954571] [rf_pm]: set losc_out 32k out[wifi_pm]: wifi gpio init is OK !!
[    4.967367] ALSA device list:
[    4.974882]   #0: audiocodec
[    4.982460]   #1: sndhdmi
[    4.991209] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities
[    5.100670] EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities
[    5.319815] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null)
[    5.332501] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    5.351929] devtmpfs: mounted
[    5.359837] Freeing init memory: 332K
[    5.368225] Failed to execute /init.  Attempting defaults...
[    5.440081] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr0<-->device0, type=4, mode=4
[    6.290350] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    6.310404] systemd[1]: Detected architecture 'arm'.
[    6.381221] systemd[1]: Failed to insert module 'autofs4'
[    6.393823] systemd[1]: Set hostname to <bananapi>.
[    6.719606] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    6.733646] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    6.747252] systemd[1]: Expecting device dev-ttyS0.device...
[    6.764333] systemd[1]: Starting Remote File Systems (Pre).
[    6.781270] systemd[1]: Reached target Remote File Systems (Pre).
[    6.793482] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    6.809376] systemd[1]: Starting Encrypted Volumes.
[    6.825825] systemd[1]: Reached target Encrypted Volumes.
[    6.837151] systemd[1]: Starting Swap.
[    6.852149] systemd[1]: Reached target Swap.
[    6.862200] systemd[1]: Expecting device dev-mmcblk0p1.device...
[    6.879689] systemd[1]: Starting Root Slice.
[    6.895301] systemd[1]: Created slice Root Slice.
[    6.905709] systemd[1]: Starting User and Session Slice.
[    6.922393] systemd[1]: Created slice User and Session Slice.
[    6.934088] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    6.953046] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    6.966382] systemd[1]: Starting Delayed Shutdown Socket.
[    6.983922] systemd[1]: Listening on Delayed Shutdown Socket.
[    6.995930] systemd[1]: Starting Journal Socket (/dev/log).
[    7.013897] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.026263] systemd[1]: Starting udev Control Socket.
[    7.043713] systemd[1]: Listening on udev Control Socket.
[    7.055405] systemd[1]: Starting udev Kernel Socket.
[    7.072719] systemd[1]: Listening on udev Kernel Socket.
[    7.084276] systemd[1]: Starting Journal Socket.
[    7.100504] systemd[1]: Listening on Journal Socket.
[    7.111362] systemd[1]: Starting System Slice.
[    7.127269] systemd[1]: Created slice System Slice.
[    7.138012] systemd[1]: Started File System Check on Root Device.
[    7.150079] systemd[1]: Starting system-systemd\x2dfsck.slice.
[    7.167619] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    7.179883] systemd[1]: Starting system-autologin.slice.
[    7.196765] systemd[1]: Created slice system-autologin.slice.
[    7.208412] systemd[1]: Starting system-serial\x2dgetty.slice.
[    7.225783] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    7.237989] systemd[1]: Starting Increase datagram queue length...
[    7.311274] systemd[1]: Starting Restore / save the current clock...
[    7.420800] systemd[1]: Starting udev Coldplug all Devices...
[    7.530855] systemd[1]: Mounted POSIX Message Queue File System.
[    7.553078] systemd[1]: Starting Load Kernel Modules...
[    7.655279] systemd[1]: Started Set Up Additional Binary Formats.
[    7.668073] systemd[1]: Mounting Debug File System...
[    7.710363] UMP: UMP device driver -6e2e33f loaded
[    7.781014] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[    7.860947] systemd[1]: Mounted Huge Pages File System.
[    7.872558] systemd[1]: Starting Slices.
[    7.888752] systemd[1]: Reached target Slices.
[    7.933317] Get mali parameter successfully
[    7.943894] Init Mali gpu successfully
[    7.954562] Mali: Mali device driver loaded
[    8.006252] systemd[1]: Started Increase datagram queue length.
[    8.126246] systemd[1]: Started Restore / save the current clock.
[    8.200719] [drm] Initialized drm 1.1.0 20060810
[    8.226590] mali_platform_drm_init(), driver name: mali_drm, version 0.1
[    8.239735] DRM: mali_platform_drm_probe()
[    8.249906] mali_drm_init(), driver name: mali_drm, version 0.1
[    8.262481] DRM: mali_driver_load start
[    8.262520] DRM: mali_driver_load done
[    8.262532] [drm] Initialized mali_drm 0.1.0 20100520 on minor 0
[    8.299357] systemd[1]: Mounted Debug File System.
[    8.370848] dhd_module_init: in
[    8.379747] ======== bcm_wlan_set_plat_data ========
[    8.390622] bcm_wlan_get_oob_irq enter.
[    8.400202] gpio [202] map to virq [10] ok
[    8.400210] host_oob_irq: 10 
[    8.400218] host_oob_irq_flags=4
[    8.400225] dhd_wifi_platform_load: Enter
[    8.400255] Power-up adapter 'DHD generic adapter'
[    8.400334] wifi_platform_set_power = 1
[    8.400341] ======== PULL WL_REG_ON HIGH! ========
[    8.400349] [wifi_pm]: set wl_reg_on 1 !
[    8.481048] systemd[1]: Started Create list of required static device nodes for the current kernel.
[    8.565738] systemd[1]: Started udev Coldplug all Devices.
[    8.579933] systemd[1]: Time has been changed
[    8.590493] systemd[1]: Starting Create Static Device Nodes in /dev...
[    8.700727] systemd[1]: Starting Syslog Socket.
[    8.710113] wifi_platform_bus_enumerate device present 1
[    8.710122] ======== Card detection to detect SDIO card! ========
[    8.710169] [mmc]: sdc1 set ios: clk 0Hz bm PP pm UP vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    8.711708] [mmc]: sdc1 power_supply is null
[    8.740040] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    8.779620] systemd[1]: Listening on Syslog Socket.
[    8.790233] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 1 err, cmd 52,  RTO !!
[    8.803992] systemd[1]: Starting Journal Service...
[    8.814977] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 1 err, cmd 52,  RTO !!
[    8.828513] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    8.846762] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    8.848714] [mmc]: *** sunxi_mci_dump_errinfo(L826): smc 1 err, cmd 8,  RTO !!
[    8.848745] *******************Try sdio*******************
[    8.849074] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B
[    8.915703] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[    8.929197] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    8.942563] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    8.957060] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[    8.987439] systemd[1]: Started Journal Service.
[    9.070045] [mmc]: sdc1 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing SD-HS(SDR25) dt B
[    9.086775] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing SD-HS(SDR25) dt B
[    9.103329] [mmc]: sdc1 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 4 timing SD-HS(SDR25) dt B
[    9.121348] mmc2: new high speed SDIO card at address 0001
[    9.133684] *******************sdio init ok*******************
[    9.149827] bcmsdh_register: register client driver
[    9.161156] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[    9.172231] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[    9.172241] bus num (host idx)=2, slot num (rca)=1
[    9.172249] found adapter info 'DHD generic adapter'
[    9.172749] F1 signature read @0x18000000=0x1530a9a6
[    9.175343] F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x3
[    9.176386] DHD: dongle ram size is set to 524288(orig 524288) at 0x0
[    9.176524] wifi_platform_get_mac_addr
[    9.176533] dhd_custom_get_mac_address Enter
[    9.176543] dhd_custom_get_mac_address wifi_mac=
[    9.177333] wl_create_event_handler(): thread:wl_event_handler:6f started
[    9.177346] tsk Enter, tsk = 0xe5861430
[    9.178294] p2p0: P2P Interface Registered
[    9.178402] dhd_attach(): thread:dhd_watchdog_thread:70 started
[    9.178483] dhd_attach(): thread:dhd_dpc:71 started
[    9.178559] dhd_attach(): thread:dhd_rxf:72 started
[    9.178577] dhd_deferred_work_init: work queue initialized 
[    9.178860] dhd_custom_get_mac_address Enter
[    9.178870] dhd_custom_get_mac_address wifi_mac=
[    9.178881] Dongle Host Driver, version 1.201.34.2 (r491657)
[    9.178886] Compiled in drivers/net/wireless/bcmdhd on Apr  1 2016 at 09:03:23
[    9.179505] Register interface [wlan0]  MAC: 00:90:4c:11:22:33
[    9.179511] 
[    9.179520] dhd_prot_ioctl : bus is down. we have nothing to do
[    9.179582] bcmsdh_oob_intr_unregister: Enter
[    9.179589] bcmsdh_oob_intr_unregister: irq is not registered
[    9.179604] dhd_txglom_enable: enable 0
[    9.179611] dhd_bus_devreset:  WLAN OFF DONE
[    9.179664] wifi_platform_set_power = 0
[    9.179671] ======== PULL WL_REG_ON LOW! ========
[    9.179679] [wifi_pm]: set wl_reg_on 0 !
[    9.179757] dhd_module_init: Exit err=0

Raspbian GNU/Linux 8 bananapi ttyS0

bananapi login: root
Password: 
Linux bananapi 3.4.39-02-lobo #1 SMP PREEMPT Fri Apr 1 09:06:07 UTC 2016 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@bananapi:~# uname -a
Linux bananapi 3.4.39-02-lobo #1 SMP PREEMPT Fri Apr 1 09:06:07 UTC 2016 armv7l GNU/Linux 

 

 

 

And then I had an installation with zero free space. You can't do anything with it:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.9G  3.7G     0 100% /
devtmpfs        373M     0  373M   0% /dev
tmpfs           501M   68K  501M   1% /dev/shm
tmpfs           501M  6.9M  494M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           501M     0  501M   0% /sys/fs/cgroup
/dev/mmcblk0p1  256M   45M  211M  18% /boot
tmpfs           101M  4.0K  101M   1% /run/user/1000
/dev/mmcblk1p1  7.2G  145M  6.7G   3% /media/pi/3684f9bd-1ea5-4cd0-a75b-b47af6147d77
tmpfs           101M     0  101M   0% /run/user/0

I quickly used Armbian's tools to resize the partition to the maximum and rebooted just to realise that they really use raspbian.org repositories for this OS image (how moronic is it to use ARMv6 code on a H3 board?!). I tried to get RPi-Monitor installed which didn't work out of the box, wasted almost an hour to fix this stuff and then gave up. Since I simply copied our armbianmonitor tool to the installation I gave up on RPi-Monitor and used armbianmonitor instead to monitor temperatures, CPU clockspeed and so on when running a few benchmarks:

 

The bad news:

 

BPi M2+ is a 99% clone of Orange Pi Plus/PC. Why didn't they do a 100% copy but instead chose to f*ck up the missing one percent? The Orange Pi variants all use a programmable voltage regulator to provide the SoC's VDD_CPUX voltage (lower clockspeeds --> lower voltage --> less heat --> more efficient throttling behaviour if SoC starts to overheat). On BPi M2+ the SoC is always fed with 1.3V which prevents best performance with heavy multithreaded workloads. Be prepared that due to this high voltage even throttling down to half of the maximum clockspeed doesn't help that much:

 

Bildschirmfoto%202016-04-07%20um%2011.48

 

This is a not so demanding benchmark running with Armbian settings. Any Orange Pi variant would reduce voltages when reduding clockspeeds which is responsible for less heat emissions and therefore with the very same settings a H3 used on an Orange Pi would still run with 816, 912 or even 960 MHz due to reduced VDD_CPUX voltage where BPi M2+ remains at 648 MHz.

 

SinoVoip not only tried to copy the hardware very closely, they also use loboris' kernel 3.4 sources developed for Orange Pis (Armbian uses a different code base) and they chose to copy the most important mistake Xunlong made so far (the Orange Pi vendor, that developed also the 1st Banana Pi that has been manufactured by SinoVoip from then on).

 

Their throttling settings prefer killing CPU cores instead of throttling if the SoC starts to overheat. This is the main reason why Orange Pi boards get that bad scores on openbenchmarking.org: Since the multithreaded benchmarks increase temperatures that much that CPU cores are killed and never come back.

 

This is exactly what happens with SinoVoip's software settings: I started an usual run of Phoronix Test Suite, the 1st benchmark already killed cpu3, the next one cpu2 and due to their moronic THS settings the maximum clockspeed is 1008 MHz anyway. So a SBC advertised as 'quad core @ 1.2GHz' is already just a 'dual core @ 1.0GHz' when running a few boring benchmarks:

[ 2749.050080] CPU Budget:Try to down cpu 3, cluster0 online 4, limit 3
[ 2749.051406] [hotplug]: cpu(0) try to kill cpu(3)
[ 2749.052482] [hotplug]: cpu3 is killed! .
[ 4575.080090] CPU Budget:Try to down cpu 2, cluster0 online 3, limit 2
[ 4575.081791] [hotplug]: cpu(0) try to kill cpu(2)
[ 4575.081853] [hotplug]: cpu2 is killed! .

And benchmark results look as expected: The worst combination is SinoVoip hardware combined with SinoVoip software: http://openbenchmarking.org/result/1604082-GA-1604074GA00

 

We implemented a special corekeeper service especially for M2+ in Armbian two days ago to help recover from killed CPU cores (since we can't prevent this as long as we've to rely on kernel 3.4 and the M2+'s fixed voltage is a real problem). Be prepared that if you run really demanding workloads on the BPi M2+ with their OS images that you end up with a single core board pretty soon.

 

The good news:

 

Since it's 'just another H3 board' trying very hard to be as compatible as possible to the Oranges you benefit automagically from every software effort made by the community. You don't need to use software from SinoVoip, you don't need to rely on their (non existing) support, you simply can use any of the community's stuff. Mainlining efforts are progressing nicely and by simply mixing device tree stuff from Orange Pi Plus and PC I've been able to get the BPi M2+ with working GBit Ethernet and maximum USB throughput running with kernel 4.6.

 

As a reference iozone measurements of a USB connected HDD (UASP capable enclosure which is responsible for better performance with mainline kernel) and the onboard eMMC:

 

'SinoVoip' 3.4.39-lobo kernel:

USB disk:                                                   random  random
              KB  reclen   write rewrite    read    reread    read   write
          102400       4    6347    8163     8494     8473     506    1603
          102400      16   15420   18110    16543    16674    1885    5445
          102400     512   23024   33610    32381    32779   23049   23276
          102400    1024   17930   30673    23079    24077   23051   24331
          102400   16384   22468   35098    34304    34148   34189   35090
          
eMMC:                                                       random  random
              KB  reclen   write rewrite    read    reread    read   write
          102400       4    5323    5683    14130    14135   12028    5573
          102400      16   17531   18513    34499    34598   31193   17278
          102400     512   24868   24626    61687    61697   61581   23991
          102400    1024   25134   24949    66979    67180   67140   24553
          102400   16384   26165   25950    76265    76649   76701   25931

4.6.0-rc1:

USB disk:                                                       random  random
              KB  reclen    write  rewrite     read   reread     read    write
          102400       4     7760     7917     7845     7868      505     1445
          102400      16    17647    20568    20593    20945     1945     4729
          102400     512    27334    35579    38033    38553    24980    35320
          102400    1024    27419    36866    38764    39026    30661    36766
          102400   16384    28267    37358    38540    38558    38988    37542

eMMC:                                                           random  random
              KB  reclen    write  rewrite     read   reread     read    write
          102400       4     5233     5708    14953    14951    12650     5916
          102400      16    19776    20609    37958    38023    34206    19403
          102400     512    26981    27200    78648    78752    77930    26121
          102400    1024    27188    27173    78793    78764    78431    26651
          102400   16384    27276    27135    79341    79440    79406    27334

Open questions:

 

The board is designed to be used with an OmniVision OV5460 camera module (Xunlong sells a cheap GalaxyCore gc2035 camera module instead). The very same camera module has already been sold for Banana Pi. And the state of the driver prevented any resolutions above 640x480 (video). So unless someone is able to check the state of the drivers the use of this 'superiour' 5MP module is questionable (at least when you try to run the board with Linux -- Android might be a different story)

 

Conclusion:

 

If the price will be competitive this board is worth a look unlike other SinoVoip boards (M2/M3). It's already fully supported by Armbian so there's no need to use any of the crappy OS images the vendor provides (it's easy to use our Armbian build system to create OS images for non Debian based distros, just read the docs!)

mamaligadoc, RonaldNet and slinde like this

Share this post


Link to post
Share on other sites

So Banana pi M2+ will be not supported by armbian?? Your img working very well on m2+

Share this post


Link to post
Share on other sites

How much did they save using non programmable voltage regulator? And risking the whole project.

I bet you did not receive the camera, maybe that guy who worked on OV5460 was right.

Share this post


Link to post
Share on other sites

So Banana pi M2+ will be not supported by armbian?? Your img working very well on m2+

 

Sorry? BPi M2+ is... 'just another H3 device' and already fully supported by Armbian.

 

We include

 

- a fex file for kernel 3.4 not showing moronic THS (throttling) behaviour like SinoVoip's

- device tree stuff for mainline kernel

 

So unlike SinoVoip's offers (only crappy OS images from hell) BPi M2+ is fully supported by Armbian with both legacy and vanilla kernel. Many thanks to the many linux-sunxi community members that made this possible in such a short time.

Share this post


Link to post
Share on other sites

when i used armbian in December on my opi pc it sucks,now  with 5.07 working better than rpi3 and i plane to use it as small desktop replace,thank you for your work

Share this post


Link to post
Share on other sites

How much did they save using non programmable voltage regulator? And risking the whole project.

I bet you did not receive the camera, maybe that guy who worked on OV5460 was right.

 

it not about cost .  for it is hard to procurement.  it is just about  supply chain management.

Share this post


Link to post
Share on other sites

thank you very much for do the test.  i like you , brother.

 

if i want to do a product,  i do not need to copy everyone. we just do we want to do . for hardware ,if i want , i can do everything , MTK ,allwinner ,TI ,  samsung, RK ,qualcomm .....  so ....if i do any S805 S905, you also can say i copy ODROID :)

 

 

for all news about Xunlong, lemaker and sinovoip , many is very crazy. for all , i am not try to do any explain, even lemaker advertise they are founder for banana pi . time will tell you fact. :)

 

yes, you are right, we not good at open source .we just can say , we just can do  linux development , driver ,hardware ...  we only try to Study with you and all community. 

 

Share this post


Link to post
Share on other sites

when i used armbian in December on my opi pc it sucks

 

Back in December Igor collected all the available patches for mainline kernel and then we were able to build a very rudimental Armbian image for Orange Pi PC running kernel 4.4 with only clocks, USB and UART working. In case you tested that, then... hmm... maybe it sucked. At least no network and no display. We started supporting 3.4 kernel on H3 in February this year and the OS images are still considered experimental (yes, also applies to the 5.07 version you tested).

 

So no idea what you're really talking about.

 

for hardware ,if i want , i can do everything , MTK ,allwinner ,TI ,  samsung, RK ,qualcomm .....  so ....if i do any S805 S905, you also can say i copy ODROID

 

You know exactly why I call the BPi M2+ a clone. Since you chose to be 99% compatible to the Oranges: Exactly same DRAM type used so you can't mess up DRAM initialisation, same pin mappings vor every connected hardware so you can't mess up with sys_config.fex or device tree stuff.

 

So all that's left to mess up is the state of your OS images. And that is what's happened. I don't get why you don't test this stuff? Your current combination of kernel + sys_config.fex stuff limits the clockspeeds to 1008 MHz and the THS settings lead to killed CPU cores as soon as short load peaks happen. And you do not even notice that's something's going wrong? Why do you spend ressources on software if the result is still that horrible?

Share this post


Link to post
Share on other sites

So Banana pi M2+ will be not supported by armbian?? Your img working very well on m2+

 

Can you do us a favour? Testing a possible increase in GPU acceleration? If so please do an

sudo armbianmonitor -r

to install RPi-Monitor, then do some gaming (or run a Quake benchmark if such thing exists) and provide a screenshot from the thermal graphs. Then please download this package unpack it and install all three packages using 'sudo dpkg -i *.deb', try again and report back with a second screenshot.

 

Some background information on RPi-Monitor with Armbian here. And the expected result of the new kernel would be higher framerates but thermal settings might also need some adjustments. Therefore reporting back with before/after settings showing this is important. Otherwise trying out the new kernel package is useless!

Share this post


Link to post
Share on other sites

@tkaiser

 

if you were given the task of buying the OrangPi or this Banana Offering, which would you spend you hard earned money on

 

Today =

 

6months =

 

Peace and Respect to you.

Share this post


Link to post
Share on other sites

Can you do us a favour? Testing a possible increase in GPU acceleration? If so please do an

sudo armbianmonitor -r

to install RPi-Monitor, then do some gaming (or run a Quake benchmark if such thing exists) and provide a screenshot from the thermal graphs. Then please download this package unpack it and install all three packages using 'sudo dpkg -i *.deb', try again and report back with a second screenshot.

 

Some background information on RPi-Monitor with Armbian here. And the expected result of the new kernel would be higher framerates but thermal settings might also need some adjustments. Therefore reporting back with before/after settings showing this is important. Otherwise trying out the new kernel package is useless!

of course,I would be honored to help you.I make it now.

Share this post


Link to post
Share on other sites

if you were given the task of buying the OrangPi or this Banana Offering, which would you spend you hard earned money on

 

Why should I choose between only two alternatives, especially since 'the Orange Pi' does not exist and no price for the M2+ is known yet? We have nearly 10 different Orange Pi variants with the announced OPi PC Plus (8GB eMMC and WiFi) being close to M2+ feature-wise (or OPi Plus).

 

I will ask the European distributor on monday but the last time I tried to get information from them it didn't work (they did not even know that they do not sell the Banana Pro but the M1+ instead). And 'specifications' there already look funny: there the M2+ is just 65x5mm in size (oh how I love this copy&paste crap done by trainees and sales persons!)

 

The most interesting thing regarding H3 boards has always been the low price. Something I'm interested in are also the camera/video capabilities (completely unknown yet how M2+ with OV5460 might work and maybe things improve a lot regarding GC2305 as sold by Xunlong). And everything else depends on the use case.

 

I'm still curious whether we'll see the announced quad core A20 successor in a few months. Since pin-compatible means we get the same features (SATA, 2 USB host ports), twice the speed and finally throttling problems :)

 

And the whole review above was mostly not about a specific hardware or a vendor but about Armbian's and the community's role. Since the linux-sunxi community does such a great job and since projects like Armbian exist the only thing you have to check first... "Is or will the board be supported by Armbian?" Since then software and support quality the specific vendor provides becomes completely irrelevant and you also have not to stick with crappy vendor kernels or Allwinner BSPs but can enjoy mainline kernel running on your device.

 

Maybe hardware vendors will get the idea sometimes in the future to better throw their crappy OS images in the bin and sponsor projects like Armbian instead. But some of them seem to love getting a bad reputation... I don't know.

Share this post


Link to post
Share on other sites

BTW: I wanted to try out mainline kernel patches that would implement cpufreq/dvfs/throttling when used with vanilla kernel but failed and decided to give up for now. As a measure of precaution we will limit BPi M2+ max cpufreq to 816MHz in the meantime when we start to provide vanilla CLI images for H3 boards.

Share this post


Link to post
Share on other sites

RPImonitor install with issue,sorry for that,i use -m mode for now,with original kernel on quake3 27 fps,first image for thermal monitor,after update impressive 39 fps,second image for temperature.
 

post-1074-0-07568800-1460215383_thumb.png

post-1074-0-21325600-1460215395_thumb.png

Share this post


Link to post
Share on other sites

if you need more accurate result i use fan for same condition (new kernel tested on warm system after first test)

Share this post


Link to post
Share on other sites

it not about cost .  for it is hard to procurement.  it is just about  supply chain management.

 

I understand the decision now and thank you for understanding my question, i should learn about supply chain management from now on.

Wish you good luck to your new product.

Share this post


Link to post
Share on other sites

it not about cost .  for it is hard to procurement.  it is just about  supply chain management.

 

If I understand correctly, the implications of a fixed voltage regulator is that the BPi M2+ will need a fan to achieve the same CPU performance under load as the OPI PC AND it won't support a low power 'idle'.  I would consider that a FATAL FLAW for most ARM board use-cases.

Tido likes this

Share this post


Link to post
Share on other sites

if you need more accurate result i use fan for same condition (new kernel tested on warm system after first test)

 

Nope, thx for the test! Future Armbian releases will show +40 fps

 

If I understand correctly, the implications of a fixed voltage regulator is that the BPi M2+ will need a fan to achieve the same CPU performance under load as the OPI PC AND it won't support a low power 'idle'.  I would consider that a FATAL FLAW for most ARM board use-cases.

 

Fortunately it's not like this. The fixed voltage is somewhat annoying but the main issue is throttling behaviour under full load conditions. With next Armbian images it's fixed and killed CPU cores come back automagically within seconds. And since mainlining efforts are still progressing nicely in a few months no one will think about situation with 3.4 BSP kernels anyway.

 
So while M2+ will still consume more energy and will be a bit slower due to overheating earlier it's not that much of an issue. Think about the use case. If you want to run irrelevant benchmarks then BPi M2+ is a bad choice. If network performance is something you're interested in, BPi M2+ might be a good choice. And so on...

Share this post


Link to post
Share on other sites

 

Nope, thx for the test! Future Armbian releases will show +40 fps

 

 

Fortunately it's not like this. The fixed voltage is somewhat annoying but the main issue is throttling behaviour under full load conditions. With next Armbian images it's fixed and killed CPU cores come back automagically within seconds. And since mainlining efforts are still progressing nicely in a few months no one will think about situation with 3.4 BSP kernels anyway.

 
So while M2+ will still consume more energy and will be a bit slower due to overheating earlier it's not that much of an issue. Think about the use case. If you want to run irrelevant benchmarks then BPi M2+ is a bad choice. If network performance is something you're interested in, BPi M2+ might be a good choice. And so on...

 

Awesome job,i tested to retroarch,psp emulator get 26-30 fps in 3d,60fps in 2d,pretty awesome :) now try get kodi on it,build in player can run 4K video ,not fast as 1080p but pretty impressive,you configured cma to 256Mb i gues

Share this post


Link to post
Share on other sites

Agreed, I think that the hardware vendors should sponsor projects such as this one, which will benefit not only them but the community as a whole

 

Maybe hardware vendors will get the idea sometimes in the future to better throw their crappy OS images in the bin and sponsor projects like Armbian instead.
 

Share this post


Link to post
Share on other sites

Awesome job,i tested to retroarch,psp emulator get 26-30 fps in 3d,60fps in 2d,pretty awesome :) now try get kodi on it,build in player can run 4K video ,not fast as 1080p but pretty impressive,you configured cma to 256Mb i gues

 

Regarding Kodi this page might be interesting: http://linux-sunxi.org/User:Rellla/Armbian

 

And OpenELEC will run smoothly if you use Armbian's bananapim2plus.fex instead of Orange Pi One's (don't use the fex from SinoVoip, there the THS settings are wrong and lead to a slow board)

 

And out of curiosity: Do you have also a heatsink on H3 or just the fan?

Share this post


Link to post
Share on other sites

Regarding Kodi this page might be interesting: http://linux-sunxi.org/User:Rellla/Armbian

 

And OpenELEC will run smoothly if you use Armbian's bananapim2plus.fex instead of Orange Pi One's (don't use the fex from SinoVoip, there the THS settings are wrong and lead to a slow board)

 

And out of curiosity: Do you have also a heatsink on H3 or just the fan?

on my openelec opi pc (working 24h/24h) in self made case on cnc machine i have heatsink and 12v fan(run well on 5v),temperature max on retroarch or 2K movie max 40 grade of celcius,idle or sd iptv 30,on m2+ only fan without case,i will make photo,temperature 2k movie in armbian or psp emu about 45Grad,idle 32.Thanks for openelec sugestion,i try it. All case of temperature on max 1200Mhz cpu clock.

post-1074-0-82210800-1460309253_thumb.jpg

post-1074-0-47629000-1460309256_thumb.jpg

Share this post


Link to post
Share on other sites

one question ,your done to install armbian on emmc? how do this? i want check how fast is, install-nand-sata script not work

Thanks

Share this post


Link to post
Share on other sites

one question ,your done to install armbian on emmc? how do this? i want check how fast is, install-nand-sata script not work

Thanks

 

It's resolved but not implemented ... yet.

Share this post


Link to post
Share on other sites

Back in December Igor collected all the available patches for mainline kernel and then we were able to build a very rudimental Armbian image for Orange Pi PC running kernel 4.4 with only clocks, USB and UART working. In case you tested that, then... hmm... maybe it sucked. At least no network and no display. We started supporting 3.4 kernel on H3 in February this year and the OS images are still considered experimental (yes, also applies to the 5.07 version you tested).

 

So no idea what you're really talking about.

 

 

You know exactly why I call the BPi M2+ a clone. Since you chose to be 99% compatible to the Oranges: Exactly same DRAM type used so you can't mess up DRAM initialisation, same pin mappings vor every connected hardware so you can't mess up with sys_config.fex or device tree stuff.

 

So all that's left to mess up is the state of your OS images. And that is what's happened. I don't get why you don't test this stuff? Your current combination of kernel + sys_config.fex stuff limits the clockspeeds to 1008 MHz and the THS settings lead to killed CPU cores as soon as short load peaks happen. And you do not even notice that's something's going wrong? Why do you spend ressources on software if the result is still that horrible?

 

 

yes, i know , but for H3 chip , all  reference design is same , if we use H3 chip as a development board, all hardware function is same, for GPIO ,USB,camera...... we not space to do some change. :)   A20, A31S ,A83T,R58,H8 .....all the same. 

 

for open source , many many work need to do , even allwinner also have many many bad issue ,they not good at  linux development, just support android at first.

 

if we use all arm chip to do linux , all kernel version is too old , but you need to konw, all driver , such as 3G /4G /wifi/, switch chip ..... it is hard to begin with mainline linux , so we just can begin with old kernel  and let it work . this is why ,we need base on allwinner BSP.

 

i have some R&D  coworker with allwinner,  i also hope we can get all full support from you  and allwinner . 

Share this post


Link to post
Share on other sites

for H3 chip , all  reference design is same , if we use H3 chip as a development board, all hardware function is same, for GPIO ,USB,camera...

 

Not true. I've been talking about pin mappings and you use exactly the same as Xunlong for everything. Maybe trying to avoid more mistakes when it's about software settings.

 

Anyway: This is again the usual horrible SinoVoip experience: You ignore even active attempts to help you. I showed you several times why the thermal/throttling/cpufreq settings you use now for BPi M2+ are wrong (see above, see the low benchmarks scores you get). What do you do? Ignore it as usual and release the slowest Android image in the world AFTER I explained the problem in depth: http://forum.banana-pi.org/t/bpi-m2-new-image-android-4-4-vsersion-v1/1429/2

 

Same with Banana Pi M3: https://github.com/BPI-SINOVOIP/BPI-M3-bsp/issues/3

Well known issue, I reported it already pointing to the solution and what do you do? Close the issue and ignore the problem.

 

Unfortunately you simply don't care about your customer's problems and ignore them all the time.

Share this post


Link to post
Share on other sites

Slightly off-topic: A quick look on SinoVoip's Android build: http://forum.banana-pi.org/t/bpi-m2-new-image-android-4-4-vsersion-v1/1429/2

 

It's Android 4.4 and since Allwinner never provides updates and SinoVoip doesn't develop themselve you won't see Lollipop or Marshmallow on this device. For newbies it will be impossible to use Android at all since SinoVoip does not tell their users to use Phoenix Card or Phoenix Suit to burn the aforementioned Android image to a SD card or directly to the device in FEL mode (you start Phoenix Suit, then the M2+ connected through USB to the USB-OTG port holding down the misnamed 'u-boot' button and can then flash an image directly). But if you can deal with screenshots in chinese, find the relevant Android chapter in their gitbook 'documentation' and are able to deal with broken links then you might succeed.

 

In the link above they write "Bluetooth 4.0 supported" and "Camera ov5640 supported" which is not true since they use the same kernel as with their Raspbian image and there it's clearly written that neither BT nor camera work and at least BT isn't working at all (same applies to WiFi with this Android but you never know: SinoVoip thinks it's a good idea to let people desolder chips from their SBCs to get working WiFi).

 

The kernel shows the usual quirks: when connected to a DVI display you get wrong colors (and unless you switch your display from RGB to YPbPr mode as can be seen below or you are an Linux expert able to play with kernel sources you're already lost when you only have a DVI display), average load is always above 1 since they don't care about problems that could be solved that easily and you're stuck with 720p display resolution (or you are an Linux expert, see link before).

 

Will you be able to tweak kernel stuff with their Android (changing display resolution, switching from HDMI to DVI, adding drivers and so on): the usual SinoVoip answer applies: http://forum.banana-pi.org/t/please-update-specs-of-m3/640/53 (no answer)

 

So in case you have to use their OS images be prepared that everything will remain as already known from M2 and M3, simply look through their forums first to get an impression what you can expect. And since the first retailers here in Germany list the M2+ already (+50€ shipping included) the whole board isn't interesting at all anymore.

 

Wrong colors can be so nice:

 

IMG_6090.jpg

 

 

IMG_6092.jpg

 

You would have to change the color mode of your display to fix that:

 

IMG_6093.jpg

 

720p by default:

 

IMG_6097.jpg

 

And the typical SinoVoip 'trade mark': Average load above 1 also on Android!

 

IMG_6100.jpg

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
0

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.