Lion Wang

Members
  • Content Count

    78
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Lion Wang got a reaction from NicoD in Banana Pi BPI-M5 with Amlogic S905X3 chip design   
    Banana Pi BPI-M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port.

    main spec:
    * Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor
    * Mali-G31 GPU
    * 4GB LPDDR4
    * 16GB eMMC flash on board.
    * 4 USB 3.0 port
    * 1 GbE LAN por
    * HDMI output
    hardware interface:
     

     
    more please see wiki page, we will keep update on wiki documents.
    http://wiki.banana-pi.org/Banana_Pi_BPI-M5
  2. Like
    Lion Wang got a reaction from Werner in Banana Pi BPI-M5 with Amlogic S905X3 chip design   
    SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:F;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;CHK:1F;READ:0;CHK:1F;SD?:0;SD:0;READ:0;0.0;CHK:0; bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 no sdio debug board detected  L0:00000000 L1:00000703 L2:00008067 L3:15000020 S1:00000000 B2:20282000 B1:a0f83180 TE: 411275 BL2 Built : 15:21:42, Mar 26 2020. g12a g486bc38 - gongwei.chen@droid11-sz Board ID = 1 Set cpu clk to 24M Set clk81 to 24M Use GP1_pll as DSU clk. DSU clk: 1200 Mhz CPU clk: 1200 MHz Set clk81 to 166.6M board id: 1 Load FIP HDR DDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 fw parse done PIEI prepare done fastboot data verify result: 255 Cfg max: 12, cur: 1. Board id: 255. Force loop cfg DDR4 probe LPDDR4_PHY_V_0_1_21-Built : 15:37:51, Mar 26 2020. g12a gf098346 - gongwei.chen@droid11-sz ddr clk to 1320MHz dmc_version 0001 Check phy result INFO : End of initialization INFO : ERROR : Training has failed! 1D training failed Cfg max: 12, cur: 2. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1320MHz dmc_version 0001 Check phy result INFO : End of initialization INFO : ERROR : Training has failed! 1D training failed Cfg max: 12, cur: 3. Board id: 255. Force loop cfg DDR3 probe ddr clk to 912MHz dmc_version 0001 Check phy result INFO : End of initialization INFO : ERROR : Training has failed! 1D training failed Cfg max: 12, cur: 4. Board id: 255. Force loop cfg DDR3 probe ddr clk to 912MHz dmc_version 0001 Check phy result INFO : End of initialization INFO : ERROR : Training has failed! 1D training failed Cfg max: 12, cur: 5. Board id: 255. Force loop cfg LPDDR4 probe ddr clk to 1392MHz dmc_version 0001 Check phy result INFO : ERROR : Training has failed! 1D training failed Cfg max: 12, cur: 6. Board id: 255. Force loop cfg LPDDR4 probe ddr clk to 1392MHz dmc_version 0001 Check phy result INFO : End of CA training INFO : End of initialization INFO : Training has run successfully! Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : End of Write leveling coarse delay INFO : Training has run successfully! Check phy result INFO : End of initialization INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Training has run successfully! 1D training succeed Check phy result INFO : End of initialization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : Training has run successfully! soc_vref_reg_value 0x 00000016 00000017 00000017 00000016 00000018 00000018 00000017 00000015 00000015 00000013 00000017 00000014 00000015 00000014 00000016 00000016 00000016 00000016 00000017 00000016 00000016 00000017 00000017 00000018 00000019 00000019 00000018 00000019 00000016 00000016 00000017 00000017 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0004   dram_vref_reg_value 0x 0000005e 2D training succeed auto size-- 65535DDR cs0 size: 2048MB DDR cs1 size: 0MB DMC_DDR_CTRL: 00c0002cDDR size: 2048MB cs0 DataBus test pass cs0 AddrBus test pass non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 454 result report boot times 0Enable ddr reg access Load FIP HDR from SD, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3X from SD, src: 0x00078200, des: 0x01768000, size: 0x00095200, part: 0 0.0;M3 CHK:0;cm4_sp_mode 0 [Image: g12a_v1.1.3394-7d43064d5 2020-05-07 15:37:06 gongwei.chen@droid11-sz] OPS=0x01 ring efuse init 2b 0b 01 00 01 2a 13 00 00 17 35 38 57 4b 52 50 [0.014467 Inits done] secure task start! high task start! low task start! boot bl31 NOTICE:  BL31: v1.3(release):5d6723eeb NOTICE:  BL31: Built : 15:05:59, Mar 17 2020 NOTICE:  BL31: G12A normal boot! NOTICE:  BL31: BL33 decompress pass ERROR:   Error initializing runtime service opteed_fast U-Boot 2020.04 (Sep 16 2020 - 21:47:01 +0800) odroid-c4 Model: Hardkernel ODROID-C4 SoC:   Amlogic Meson SM1 (Unknown) Revision 2b:b (1:2) DRAM:  2 GiB MMC:   sd@ffe05000: 0, mmc@ffe07000: 1 In:    serial Out:   serial Err:   serial Net:   Warning: ethernet@ff3f0000 (eth0) using random MAC address - a6:61:90:37:1d:e0 eth0: ethernet@ff3f0000 Hit any key to stop autoboot:  2 ��� 1 ��� 0  switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3252 bytes read in 2 ms (1.6 MiB/s) ## Executing script at 08000000 201 bytes read in 5 ms (39.1 KiB/s) 15825064 bytes read in 1396 ms (10.8 MiB/s) 24576512 bytes read in 2168 ms (10.8 MiB/s) 72339 bytes read in 11 ms (6.3 MiB/s) 232 bytes read in 4 ms (56.6 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 34000000 ## Loading init Ramdisk from Legacy Image at 13000000 ...    Image Name:   uInitrd    Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)    Data Size:    15825000 Bytes = 15.1 MiB    Load Address: 00000000    Entry Point:  00000000    Verifying Checksum ... OK ## Flattened Device Tree blob at 08008000    Booting using the fdt blob at 0x8008000    Loading Ramdisk to 7b032000, end 7bf49868 ... OK    Loading Device Tree to 000000007afb7000, end 000000007b031fff ... OK Starting kernel ... [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd050] [    0.000000] Linux version 5.8.7-meson64 (root@bpi-iot-ros-ai-x64-66-gtx1050) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #trunk SMP PREEMPT Wed Sep 9 21:20:25 CST 2020 [    0.000000] Machine model: Banana Pi BPI-M5 (20200920A2) [    0.000000] efi: UEFI not found. [    0.000000] [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader! [    0.000000] Reserved memory: created CMA memory pool at 0x0000000042c00000, size 896 MiB [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [    0.000000] NUMA: No NUMA configuration found [    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000007fffffff] [    0.000000] NUMA: NODE_DATA [mem 0x7fba5100-0x7fba6fff] [    0.000000] Zone ranges: [    0.000000]   DMA      [mem 0x0000000000000000-0x000000003fffffff] [    0.000000]   DMA32    [mem 0x0000000040000000-0x000000007fffffff] [    0.000000]   Normal   empty [    0.000000] Movable zone start for each node [    0.000000] Early memory node ranges [    0.000000]   node   0: [mem 0x0000000000000000-0x0000000004ffffff] [    0.000000]   node   0: [mem 0x0000000005300000-0x000000007fffffff] [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff] [    0.000000] On node 0 totalpages: 523520 [    0.000000]   DMA zone: 4096 pages used for memmap [    0.000000]   DMA zone: 0 pages reserved [    0.000000]   DMA zone: 261376 pages, LIFO batch:63 [    0.000000]   DMA32 zone: 4096 pages used for memmap [    0.000000]   DMA32 zone: 262144 pages, LIFO batch:63 [    0.000000] psci: probing for conduit method from DT. [    0.000000] psci: PSCIv1.0 detected in firmware. [    0.000000] psci: Using standard PSCI v0.2 function IDs [    0.000000] psci: MIGRATE_INFO_TYPE not supported. [    0.000000] psci: SMC Calling Convention v1.1 [    0.000000] percpu: Embedded 23 pages/cpu s54360 r8192 d31656 u94208 [    0.000000] pcpu-alloc: s54360 r8192 d31656 u94208 alloc=23*4096 [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3  [    0.000000] Detected VIPT I-cache on CPU0 [    0.000000] CPU features: detected: Virtualization Host Extensions [    0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [    0.000000] alternatives: patching kernel code [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 515328 [    0.000000] Policy zone: DMA32 [    0.000000] Kernel command line: root=UUID=c86ab25f-9e55-4201-9780-9ebb42548fd2 rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=8 ubootpart=667f95c4-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=memory swapaccount=1 [    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) [    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [    0.000000] software IO TLB: mapped [mem 0x3bfff000-0x3ffff000] (64MB) [    0.000000] Memory: 1029804K/2094080K available (13756K kernel code, 1280K rwdata, 5568K rodata, 3328K init, 587K bss, 146772K reserved, 917504K cma-reserved) [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [    0.000000] rcu: Preemptible hierarchical RCU implementation. [    0.000000] rcu:     RCU event tracing is enabled. [    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [    0.000000]     Trampoline variant of Tasks RCU enabled. [    0.000000]     Rude variant of Tasks RCU enabled. [    0.000000]     Tracing variant of Tasks RCU enabled. [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [    0.000000] GIC: Using split EOI/Deactivate mode [    0.000000] irq_meson_gpio: 100 to 8 gpio interrupt mux initialized [    0.000000] random: get_random_bytes called from start_kernel+0x35c/0x528 with crng_init=0 [    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [    0.000003] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [    0.000175] Console: colour dummy device 80x25 [    0.000658] printk: console [tty1] enabled [    0.000738] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [    0.000761] pid_max: default: 32768 minimum: 301 [    0.000846] LSM: Security Framework initializing [    0.000879] Yama: becoming mindful. [    0.000971] AppArmor: AppArmor initialized [    0.001023] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [    0.001044] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) [    0.002465] rcu: Hierarchical SRCU implementation. [    0.005169] EFI services will not be available. [    0.005506] smp: Bringing up secondary CPUs ... [    0.006305] Detected VIPT I-cache on CPU1 [    0.006362] CPU1: Booted secondary processor 0x0000000100 [0x411fd050] [    0.007173] Detected VIPT I-cache on CPU2 [    0.007210] CPU2: Booted secondary processor 0x0000000200 [0x411fd050] [    0.007963] Detected VIPT I-cache on CPU3 [    0.007994] CPU3: Booted secondary processor 0x0000000300 [0x411fd050] [    0.008065] smp: Brought up 1 node, 4 CPUs [    0.008125] SMP: Total of 4 processors activated. [    0.008135] CPU features: detected: Privileged Access Never [    0.008145] CPU features: detected: LSE atomic instructions [    0.008155] CPU features: detected: User Access Override [    0.008164] CPU features: detected: 32-bit EL0 Support [    0.008174] CPU features: detected: Common not Private translations [    0.008185] CPU features: detected: RAS Extension Support [    0.008194] CPU features: detected: Data cache clean to the PoU not required for I/D coherence [    0.008208] CPU features: detected: CRC32 instructions [    0.008218] CPU features: detected: 32-bit EL1 Support [    0.028175] CPU: All CPU(s) started at EL2 [    0.030103] devtmpfs: initialized [    0.040239] Registered cp15_barrier emulation handler [    0.040268] Registered setend emulation handler [    0.040770] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [    0.040814] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [    0.059870] xor: measuring software checksum speed [    0.096173]    8regs     :  2243.000 MB/sec [    0.136213]    32regs    :  2834.000 MB/sec [    0.176259]    arm64_neon:  2486.000 MB/sec [    0.176270] xor: using function: 32regs (2834.000 MB/sec) [    0.176288] pinctrl core: initialized pinctrl subsystem [    0.176997] thermal_sys: Registered thermal governor 'fair_share' [    0.177001] thermal_sys: Registered thermal governor 'bang_bang' [    0.177025] thermal_sys: Registered thermal governor 'step_wise' [    0.177036] thermal_sys: Registered thermal governor 'user_space' [    0.177788] DMI not present or invalid. [    0.178277] NET: Registered protocol family 16 [    0.179521] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations [    0.180113] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [    0.180414] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [    0.180492] audit: initializing netlink subsys (disabled) [    0.180659] audit: type=2000 audit(0.180:1): state=initialized audit_enabled=0 res=1 [    0.182151] cpuidle: using governor menu [    0.182449] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [    0.182549] ASID allocator initialised with 65536 entries [    0.183567] Serial: AMBA PL011 UART driver [    0.212929] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [    0.212955] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [    0.212968] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [    0.212980] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [    0.215070] cryptd: max_cpu_qlen set to 1000 [    0.284530] raid6: neonx8   gen()  2131 MB/s [    0.352562] raid6: neonx8   xor()  1657 MB/s [    0.420630] raid6: neonx4   gen()  2192 MB/s [    0.488687] raid6: neonx4   xor()  1649 MB/s [    0.556753] raid6: neonx2   gen()  2069 MB/s [    0.624805] raid6: neonx2   xor()  1511 MB/s [    0.692865] raid6: neonx1   gen()  1766 MB/s [    0.760927] raid6: neonx1   xor()  1279 MB/s [    0.828984] raid6: int64x8  gen()  1522 MB/s [    0.897077] raid6: int64x8  xor()   784 MB/s [    0.965122] raid6: int64x4  gen()  1645 MB/s [    1.033180] raid6: int64x4  xor()   840 MB/s [    1.101237] raid6: int64x2  gen()  1473 MB/s [    1.169284] raid6: int64x2  xor()   747 MB/s [    1.237356] raid6: int64x1  gen()  1115 MB/s [    1.305412] raid6: int64x1  xor()   580 MB/s [    1.305423] raid6: using algorithm neonx4 gen() 2192 MB/s [    1.305432] raid6: .... xor() 1649 MB/s, rmw enabled [    1.305442] raid6: using neon recovery algorithm [    1.306040] ACPI: Interpreter disabled. [    1.306966] 5V: supplied by 12V [    1.308054] VDDAO_3V3: supplied by 12V [    1.308767] iommu: Default domain type: Translated  [    1.308940] vgaarb: loaded [    1.309920] SCSI subsystem initialized [    1.310246] usbcore: registered new interface driver usbfs [    1.310313] usbcore: registered new interface driver hub [    1.310420] usbcore: registered new device driver usb [    1.310762] pps_core: LinuxPPS API ver. 1 registered [    1.310779] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [    1.310811] PTP clock support registered [    1.311071] EDAC MC: Ver: 3.0.0 [    1.312434] NetLabel: Initializing [    1.312456] NetLabel:  domain hash size = 128 [    1.312465] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO [    1.312521] NetLabel:  unlabeled traffic allowed by default [    1.312922] clocksource: Switched to clocksource arch_sys_counter [    1.313323] VFS: Disk quotas dquot_6.6.0 [    1.313396] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [    1.313874] AppArmor: AppArmor Filesystem Enabled [    1.313955] pnp: PnP ACPI: disabled [    1.320864] NET: Registered protocol family 2 [    1.321380] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) [    1.321445] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) [    1.321602] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear) [    1.321773] TCP: Hash tables configured (established 16384 bind 16384) [    1.322157] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) [    1.322207] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) [    1.322383] NET: Registered protocol family 1 [    1.322413] PCI: CLS 0 bytes, default 64 [    1.322615] Trying to unpack rootfs image as initramfs... [    1.940357] Freeing initrd memory: 15452K [    1.941258] kvm [1]: IPA Size Limit: 40bits [    1.941411] kvm [1]: vgic interrupt IRQ1 [    1.941550] kvm [1]: VHE mode initialized successfully [    1.947240] Initialise system trusted keyrings [    1.947295] Key type blacklist registered [    1.947415] workingset: timestamp_bits=44 max_order=19 bucket_order=0 [    1.952050] zbud: loaded [    1.953348] squashfs: version 4.0 (2009/01/31) Phillip Lougher [    1.954074] fuse: init (API version 7.31) [    1.955132] integrity: Platform Keyring initialized [    1.990356] Key type asymmetric registered [    1.990375] Asymmetric key parser 'x509' registered [    1.990445] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245) [    1.990589] io scheduler mq-deadline registered [    1.990605] io scheduler kyber registered [    1.990741] io scheduler bfq registered [    1.994006] gpio-447 (usb-hub-reset): hogged as output/high [    1.997525] EINJ: ACPI disabled. [    2.004268] soc soc0: Amlogic Meson SM1 (Unknown) Revision 2b:b (1:2) Detected [    2.005892] pwm-regulator: supplied by regulator-dummy [    2.006135] VCC_3V3: supplied by VDDAO_3V3 [    2.006185] FLASH_1V8: supplied by VCC_3V3 [    2.006234] VCC_1V8: supplied by VCC_3V3 [    2.006286] VDDAO_1V8: supplied by VDDAO_3V3 [    2.007089] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled [    2.009924] Serial: AMBA driver [    2.010373] ff803000.serial: ttyAML0 at MMIO 0xff803000 (irq = 13, base_baud = 1500000) is a meson_uart [    3.119704] printk: console [ttyAML0] enabled [    3.124729] ffd24000.serial: ttyAML1 at MMIO 0xffd24000 (irq = 22, base_baud = 1500000) is a meson_uart [    3.139867] loop: module loaded [    3.144603] libphy: Fixed MDIO Bus: probed [    3.145290] tun: Universal TUN/TAP device driver, 1.6 [    3.149060] thunder_xcv, ver 1.0 [    3.151311] thunder_bgx, ver 1.0 [    3.154520] nicpf, ver 1.0 [    3.157907] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [    3.162931] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [    3.168839] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k [    3.175692] igb: Copyright (c) 2007-2014 Intel Corporation. [    3.181259] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k [    3.188973] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [    3.195041] sky2: driver version 1.30 [    3.198987] VFIO - User Level meta-driver version: 0.3 [    3.205244] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [    3.210042] ehci-pci: EHCI PCI platform driver [    3.214472] ehci-platform: EHCI generic platform driver [    3.219773] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [    3.225731] ohci-pci: OHCI PCI platform driver [    3.230164] ohci-platform: OHCI generic platform driver [    3.235793] usbcore: registered new interface driver usb-storage [    3.242855] mousedev: PS/2 mouse device common for all mice [    3.247399] i2c /dev entries driver [    3.256768] thermal thermal_zone0: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed:-17 [    3.260992] sdhci: Secure Digital Host Controller Interface driver [    3.266236] sdhci: Copyright(c) Pierre Ossman [    3.270799] Synopsys Designware Multimedia Card Interface Driver [    3.277817] meson-gx-mmc ffe07000.mmc: allocated mmc-pwrseq [    3.308933] sdhci-pltfm: SDHCI platform and OF driver helper [    3.310181] ledtrig-cpu: registered to indicate activity on CPUs [    3.315445] meson-sm: secure-monitor enabled [    3.319434] hid: raw HID events driver (C) Jiri Kosina [    3.324362] usbcore: registered new interface driver usbhid [    3.329762] usbhid: USB HID core driver [    3.335042] NET: Registered protocol family 10 [    3.338619] Segment Routing with IPv6 [    3.341657] NET: Registered protocol family 17 [    3.346065] 8021q: 802.1Q VLAN Support v1.8 [    3.350227] Key type dns_resolver registered [    3.354680] registered taskstats version 1 [    3.358402] Loading compiled-in X.509 certificates [    3.364798] Loaded X.509 cert 'Build time autogenerated kernel key: e57a8865a56fa2714e522a1b383c5dc4bf89cb23' [    3.373082] zswap: loaded using pool lzo/zbud [    3.377547] Key type ._fscrypt registered [    3.381251] Key type .fscrypt registered [    3.383706] mmc0: new HS200 MMC card at address 0001 [    3.385162] Key type fscrypt-provisioning registered [    3.390618] mmcblk0: mmc0:0001 AJTD4R 14.6 GiB [    3.396688] Btrfs loaded, crc32c=crc32c-generic [    3.399818] mmcblk0boot0: mmc0:0001 AJTD4R partition 1 4.00 MiB [    3.410204] mmcblk0boot1: mmc0:0001 AJTD4R partition 2 4.00 MiB [    3.412078] Key type encrypted registered [    3.415834] mmcblk0rpmb: mmc0:0001 AJTD4R partition 3 4.00 MiB, chardev (242:0) [    3.419646] AppArmor: AppArmor sha1 policy hashing enabled [    3.442165] HUB_5V: supplied by 5V [    3.442436] USB_PWR_EN: supplied by 5V [    3.446313] dwc3-meson-g12a ffe09000.usb: USB2 ports: 2 [    3.448835] dwc3-meson-g12a ffe09000.usb: USB3 ports: 1 [    3.456891] dwc2 ff400000.usb: supply vusb_d not found, using dummy regulator [    3.461158] dwc2 ff400000.usb: supply vusb_a not found, using dummy regulator [    3.468350] dwc2 ff400000.usb: EPs: 7, dedicated fifos, 712 entries in SPRAM [    3.476065] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [    3.480612] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 [    3.488297] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228fe6c hci version 0x110 quirks 0x0000000000010010 [    3.497523] xhci-hcd xhci-hcd.0.auto: irq 30, io mem 0xff500000 [    3.503548] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.08 [    3.511555] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [    3.518726] usb usb1: Product: xHCI Host Controller [    3.523535] usb usb1: Manufacturer: Linux 5.8.7-meson64 xhci-hcd [    3.529486] usb usb1: SerialNumber: xhci-hcd.0.auto [    3.534651] hub 1-0:1.0: USB hub found [    3.538051] hub 1-0:1.0: 2 ports detected [    3.542215] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [    3.547436] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 [    3.555024] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [    3.561523] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [    3.569583] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08 [    3.577702] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [    3.584858] usb usb2: Product: xHCI Host Controller [    3.589687] usb usb2: Manufacturer: Linux 5.8.7-meson64 xhci-hcd [    3.595638] usb usb2: SerialNumber: xhci-hcd.0.auto [    3.600769] hub 2-0:1.0: USB hub found [    3.604201] hub 2-0:1.0: 1 port detected [    3.608483] dwc3-meson-g12a ffe09000.usb: switching to Device Mode [    3.614970] meson-gx-mmc ffe05000.sd: Got CD GPIO [    3.648743] Freeing unused kernel memory: 3328K [    3.668967] Run /init as init process [    3.668991]   with arguments: [    3.669926]     /init [    3.672168]   with environment: [    3.675295]     HOME=/ [    3.677610]     TERM=linux [    3.680276]     ubootpart=667f95c4-01 [    3.683906]     cgroup_enable=memory [    3.702915] mmc1: new high speed SDHC card at address aaaa [    3.703599] mmcblk1: mmc1:aaaa SL08G 7.40 GiB  [    3.708903]  mmcblk1: p1 [    3.942960] meson8b-dwmac ff3f0000.ethernet: IRQ eth_wake_irq not found [    3.943939] meson8b-dwmac ff3f0000.ethernet: IRQ eth_lpi not found [    3.988386] meson8b-dwmac ff3f0000.ethernet: PTP uses main clock [    3.988762] meson8b-dwmac ff3f0000.ethernet: no reset control found [    4.006807] meson-vrtc ff8000a8.rtc: registered as rtc0 [    4.006876] meson-vrtc ff8000a8.rtc: setting system clock to 1970-01-01T00:00:04 UTC (4) [    4.018928] meson8b-dwmac ff3f0000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [    4.021551] meson8b-dwmac ff3f0000.ethernet:     DWMAC1000 [    4.026722] meson8b-dwmac ff3f0000.ethernet: DMA HW capability register supported [    4.034113] meson8b-dwmac ff3f0000.ethernet: RX Checksum Offload Engine supported [    4.041558] meson8b-dwmac ff3f0000.ethernet: COE Type 2 [    4.046742] meson8b-dwmac ff3f0000.ethernet: TX Checksum insertion supported [    4.053734] meson8b-dwmac ff3f0000.ethernet: Wake-Up On Lan supported [    4.057013] spidev spi0.0: probing from DT [    4.060107] meson8b-dwmac ff3f0000.ethernet: Normal descriptors [    4.070075] meson8b-dwmac ff3f0000.ethernet: Ring mode enabled [    4.075866] meson8b-dwmac ff3f0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [    4.076251] random: fast init done [    4.084131] libphy: stmmac: probed [    4.091898] libphy: mdio_mux: probed [    4.103929] libphy: mdio_mux: probed [    4.489382] EXT4-fs (mmcblk1p1): mounted filesystem with writeback data mode. Opts: (null) [    4.916949] usb 1-1: new high-speed USB device number 2 using xhci-hcd [    5.044967] usb 1-1: device descriptor read/64, error -71 [    5.195121] systemd[1]: System time before build time, advancing clock. [    5.219209] systemd[1]: Inserted module 'autofs4' [    5.271965] systemd[1]: systemd 245.4-4ubuntu3.2 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [    5.280972] usb 1-1: device descriptor read/64, error -71 [    5.289074] systemd[1]: Detected architecture arm64. [    5.334576] systemd[1]: Set hostname to <bpi-iot-ros-ai>. [    5.528969] usb 1-1: new high-speed USB device number 3 using xhci-hcd [    5.656972] usb 1-1: device descriptor read/64, error -71 [    5.696295] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket 鈫?/run/dbus/system_bus_socket; please update the unit file accordingly. [    5.875897] random: systemd: uninitialized urandom read (16 bytes read) [    5.879266] systemd[1]: Created slice system-modprobe.slice. [    5.882923] random: systemd: uninitialized urandom read (16 bytes read) [    5.889943] systemd[1]: Created slice system-serial\x2dgetty.slice. [    5.892987] usb 1-1: device descriptor read/64, error -71 [    5.900822] random: systemd: uninitialized urandom read (16 bytes read) [    5.907999] systemd[1]: Created slice User and Session Slice. [    5.913313] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [    5.921209] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [    5.930030] systemd[1]: Reached target User and Group Name Lookups. [    5.936071] systemd[1]: Reached target Remote File Systems. [    5.941549] systemd[1]: Reached target Slices. [    5.945955] systemd[1]: Reached target Swap. [    5.950165] systemd[1]: Reached target System Time Set. [    5.955748] systemd[1]: Listening on Syslog Socket. [    5.960509] systemd[1]: Listening on fsck to fsckd communication Socket. [    5.967022] systemd[1]: Listening on initctl Compatibility Named Pipe. [    5.973882] systemd[1]: Listening on Journal Audit Socket. [    5.979056] systemd[1]: Listening on Journal Socket (/dev/log). [    5.985004] systemd[1]: Listening on Journal Socket. [    5.989942] systemd[1]: Listening on udev Control Socket. [    5.995100] systemd[1]: Listening on udev Kernel Socket. [    6.003384] systemd[1]: Mounting Huge Pages File System... [    6.005101] usb usb1-port1: attempt power cycle [    6.013321] systemd[1]: Mounting POSIX Message Queue File System... [    6.019812] systemd[1]: Mounting Kernel Debug File System... [    6.022270] systemd[1]: Condition check resulted in Kernel Trace File System being skipped. [    6.034262] systemd[1]: Starting Restore / save the current clock... [    6.039896] systemd[1]: Starting Set the console keyboard layout... [    6.046327] systemd[1]: Starting Create list of static device nodes for the current kernel... [    6.055281] systemd[1]: Starting Load Kernel Module drm... [    6.060459] systemd[1]: Started Nameserver information manager. [    6.063109] systemd[1]: Reached target Network (Pre). [    6.075433] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [    6.079230] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [    6.086570] systemd[1]: Starting Load Kernel Modules... [    6.096599] systemd[1]: Starting Remount Root and Kernel File Systems... [    6.104055] systemd[1]: Starting udev Coldplug all Devices... [    6.110464] systemd[1]: Mounted Huge Pages File System. [    6.111204] systemd[1]: Mounted POSIX Message Queue File System. [    6.117218] systemd[1]: Mounted Kernel Debug File System. [    6.123962] systemd[1]: Finished Restore / save the current clock. [    6.130132] systemd[1]: Finished Create list of static device nodes for the current kernel. [    6.148710] systemd[1]: modprobe@drm.service: Succeeded. [    6.150050] systemd[1]: Finished Load Kernel Module drm. [    6.156091] systemd[1]: Finished Load Kernel Modules. [    6.162425] systemd[1]: Mounting FUSE Control File System... [    6.166151] EXT4-fs (mmcblk1p1): re-mounted. Opts: commit=600,errors=remount-ro [    6.168016] systemd[1]: Mounting Kernel Configuration File System... [    6.180977] systemd[1]: Starting Apply Kernel Variables... [    6.190718] systemd[1]: Finished Remount Root and Kernel File Systems. [    6.192628] systemd[1]: Mounted FUSE Control File System. [    6.198213] systemd[1]: Mounted Kernel Configuration File System. [    6.206067] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [    6.212167] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [    6.225586] systemd[1]: Starting Load/Save Random Seed... [    6.233400] systemd[1]: Starting Create System Users... Armbian 20.11.0-trunk Focal ttyAML0  bpi-iot-ros-ai login:  test armbian log
  3. Like
    Lion Wang got a reaction from Werner in Banana Pi BPI-M5 with Amlogic S905X3 chip design   
    Banana Pi BPI-M5 is a new generation single board computer design , use Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor. Mali-G31 MP2 GPU with 4 x Execution Engines (650Mhz). support 4GB LPDDR4 and 16G eMMC flash. it have 4 USB 3.0 port,1GbE LAN port.

    main spec:
    * Amlogic S905X3 Quad-Core Cortex-A55 (2.0xxGHz) Processor
    * Mali-G31 GPU
    * 4GB LPDDR4
    * 16GB eMMC flash on board.
    * 4 USB 3.0 port
    * 1 GbE LAN por
    * HDMI output
    hardware interface:
     

     
    more please see wiki page, we will keep update on wiki documents.
    http://wiki.banana-pi.org/Banana_Pi_BPI-M5
  4. Like
    Lion Wang got a reaction from lanefu in Banana PI BPI-W2   
    Realtek RTD1296 Intelligent voice, video processing platform
     
    Main spec:
    Realtek RTD1296, Quad-core ARM Cortex-A53
    Mali T820 MP3 GPU
    4G DDR4 SDRAM
    8G eMMC flash (Max to 32 G)
    Realtek rtl8275 b/g/n wifi and BT 4.0 support
    M.2 Key E interface
    MicroSD slot supports up to 256GB expansion
    1 SATA interface
    1XGigabit LAN
    1xUSB 3.0 1xUSB 2.0
    HDMI in & HDMI out support HDMI bypass function
    TYPE C /Power
    IR support
     
     
    http://forum.banana-pi.org/t/realtek-rtd1296-intelligent-voice-video-processing-platform/10727
  5. Like
    Lion Wang reacted to Юрий Долгорукий in Banana PI BPI-W2   
    Realtek RTD1296, Quad-core ARM Cortex-A53 Mali T820 MP3 GPU 2G DDR4 SDRAM PCIE 2.0 interface.PCEe 1.1&SDIO 2 SATA interface Mini DP HDMI In/Out  

    Is it planned to support (create an ARMBIAN firmware) this board?
  6. Like
    Lion Wang reacted to Jens Bauer in Banana Pi M4   
    Fairly understandable.
    Cortex-A73 is by design (eg. ARM) using lower power and produces lower heat than Cortex-A72.
    Cortex-A75 even lower power and quicker than Cortex-A73.
    -So it will likely pay to choose the latter implementation over the former, even if the price of the CPU is higher.
     
    For build-farms and quick data-processing, it's interesting having high-speed CPU cores and high speed network (this can be spread out on several GbE ports or just a single 10GbE port). 2GB or 4GB LPDDR4 would also be attractive for this kind of configuration. Native 6G SATA would be a huge advantage here as well.
     
    For storage (eg. NAS), one could likely go with the old Cortex-A7, native 6G SATA support and 1GB to 2GB RAM (still 4GB will be interesting when you're using RAID configurations a'la FreeNAS, where each 1TB storage space requires 1GB RAM). Again as many (independent, full speed) GbE ports will be attractive for this configuration.
     
    If the CPU you choose have PCIe, you can basically do anything you want; just please don't waste the PCIe on USB3. Adding PCIe switches would be interesting too.
     
    As I've mentioned earlier, it's not easy to find an affordable board that has both native 6G SATA, GbE network and PCIe. I picked the EspressoBIN due to the low price and that it "technically" would cover my needs, but I've had many problems with it for several years. It still has problems when I make software-reboots (sometimes hangs), so that's a board I will not recommend. Some boards also have problems with the RAM being affected by EMI due to bad board design. The EspressoBIN was an empty promise; it can't be used as a router/firewall unless you add an external USB3-to-Ethernet adapter. The speed on the 3 ports is limited to 1Gbit for all three [eg. they share 1Gbps!], so I fail to see why they even bothered making the board more expensive by adding the Topaz switch.
    (Perhaps so that other board designers, such  as you, can learn from their mistakes?)
  7. Like
    Lion Wang reacted to NicoD in Banana Pi M4   
    Isn't there a simular SoC with HDMI-in? I thought I red somewere this was the cheaper version of that SoC.  Here-> https://www.cnx-software.com/2019/02/13/banana-pi-bpi-m4-rtd1395-board-raspberry-pi/
    A small, cheap SBC with HDMI-in and Linux support for encoding it. That I'd buy and many of my viewers.

    Then I wouldn't mind having 100Mbit/s ethernet and USB2.
    Having an SBC for this would make life easier compared to the HDMI-capture box I'm using now. I never know what it is recording until I see it afterwards.

    The W2 looks great, but it's too expensive not knowing if it'll work well for my goal.
    Keep on making great stuff. I love all SBC's.
    Greetings.
  8. Like
    Lion Wang got a reaction from NicoD in Banana Pi M4   
    just BPI-W2 support HDMI-in  , this is limited by chip .
     
    BPI-M4 with M.2 interface and 8G eMMC flash on board.
     
    have public sale : https://pt.aliexpress.com/store/302756
  9. Like
    Lion Wang reacted to malvcr in BananaPi R2 (.csc mt7623 as new boardfamily)   
    This is a picture with an R2 located in a RACK assembly.
     

     
    The set has an Orange Pi Zero as a "communication/firewall device", together with a Banana Pi M2+ as the Application Server and the Banana Pi R2 (v1) as a Database/NFS/ClamAV server.  I am configuring a Moodle on the machine.
     
    As a recommendation from TKaiser in a previous post, the R2 it is managing two 2TB hard disks with BTRFS and not RAID1 (really it is smoother and easier to configure than a software RAID).  The disks power it is provided directly by the 430W power supply (not the R2 power connectors) ... I know this is as a 12 cylinder engine in a Beetle :-) ... The enclosure has 3 fan, so no machine arrive to 50C degrees.
     
    It can be improved.  There are details, but in the future things will be better.  In this moment only the power led it is attached to something, and the Power Supply has a wire in the CPU connector to "simulate" something there (if not, the Power Supply will not work).  The machines are located in a presentation cardboard piece painted with temperature resistance silver paint, as no screw post in the enclosure match the SBC machines holes.  They are suspended on the board with metal posts.
     
    One if my "nightmares" with this machine has been the internal networking.  Basically the old style ifup-ifdown doesn't work.  Armbian it is a complex thing because it keeps the ifup-ifdown together with the NetworkManager and the SystemD.NetworkD, all at the same time.  So, sometimes you do something but it doesn't work because "the other guy" works against you and you really have no idea what it is happening, and things go wild when working three machines at the same time.
     
    At the end, The M2+ and the Zero were configured with NetworkManager and the R2 with SystemD.NetworkD ... in this respect, they are not compatible in the Armbian setup methodology.
     
    --
     
    The Zero and the M2+ take their power from the R2 (later I will use the Power Supply directly).  I remember when having the legacy 3 kernels and the zero was possible to use the USB cables for networking with the g_ether module.  But I never was able to do this to work well with the 4 series kernels.  In fact, now Armbian comes loaded with the g_serial instead.  Could be interesting to recover that functionality, as this could reduce the complexity with this type of machine combinations.  By now, I am relying in the old friend RG45.
     
  10. Like
    Lion Wang reacted to Ryder.Lee in Banana Pi R64   
    The best news is that the final patchset version for HNAT framework was accepted ( kernel 4.16) and it's based on nftables. - https://www.spinics.net/lists/netfilter-devel/msg50973.html

    We will try to add netfilter-base HNAT support for MT7622 & MT7623  in the future.
  11. Like
    Lion Wang reacted to TonyMac32 in Banana PI BPI-W2   
    I think it's more like the dentist, always complaining that I'm not flossing enough...  I don't want to hear it, but the dentist is right.  
     
     
    4.9 kernel, ok, 2015 u-boot, .  Looks like an interesting board, but I worry about drivers and any hope of mainline support. 
  12. Like
    Lion Wang got a reaction from lanefu in Banana PI BPI-W2   
    When I'm in a bad mood, I'm glad to see your posts, because you're like my wife, always chattering, but I can't say no   hope you can help us to development BPI-W2
  13. Like
    Lion Wang reacted to hjc in Banana PI BPI-W2   
    You're not alone, many board makers have to sign NDA with chip vendors. For example, when Dragonboard 820c was under development, they signed NDA with Qualcomm, and they must get approval before releasing Qualcomm kernel/bootloader sources.
    However before they got the approval to release kernel/bootloader source code, they didn't even release the board, nor any GPL-licensed binaries. You should follow the rules, too.
  14. Like
    Lion Wang reacted to Larry Bank in Banana Pi Zero   
    I just received my BPI-M2 Zero board and put it through its paces. Seems to perform similar to other H2+ boards. I added a Pin->GPIO map to my SPI_LCD and ArmbianIO projects (https://github.com/bitbank2).
     
    Observations:
     
    1) The SPI driver has that same odd issue where it occasionally spits out errors and runs a little slower than it should. 
    2) It doesn't come with an IPX antenna, but you need to add one to use wifi unless you're sitting on top of your access point.
    3) A small passive heat sink seems to be plenty when running the mainline (4.1x) kernel.
    4) The default HDMI out resolution is 1920x1080p@60fps. This causes a "jumpy" display on my monitor. Switching to 1280x720 fixed it. I've seen this on other AllWinner H2/H3 boards, so it's probably something strange with the mainline kernel hdmi code.
     
    Overall I'm happy with the board.  It would be nice to use the bluetooth. Does anyone know how to enable it?
     
  15. Like
    Lion Wang reacted to lvmc in Banana Pi Zero   
    booting with kernel 4.14.3-sunix
     
  16. Like
    Lion Wang reacted to @lex in Banana Pi Zero   
    BTW, banana pi zero and nano pi air makes a perfect board for using OV5640 sensor, so i would like to ask @Robert LabTeam if you are going to share your work on the OV5640 to be able to reach 60 fps or 90 fps, will you?
     
     
  17. Like
    Lion Wang got a reaction from lvmc in Banana Pi Zero   
    let me think about it , it mean we need do CE,FCC test,again . and many user have use BPI-M2+ inside they are product . mean we need do double inventory
  18. Like
    Lion Wang reacted to lvmc in Banana Pi Zero   
    The key point is CSI camera support without extension board, the missing point is no eMMC and tiny embedded RTC module.
  19. Like
    Lion Wang got a reaction from TonyMac32 in Banana Pi Zero   
    https://github.com/BPI-SINOVOIP/BPI-files/commit/f4a6651ae5cd4f5ebb2fba5101454fcabfedd2d5
     
    MIKEY have update it.
  20. Like
    Lion Wang reacted to guidol in Banana Pi Zero   
    if the costs are rising to fast - how about installing a standard-eMMC socket like on the ODROID C2 or inside the Pinebook?
    I think this would cost only a few cents?
    For me that would be fine - then while I upgraded my Pinebook to 32GB eMMC I could use the old 16Gb eMMC on my ODROID C2
    AND if the market will supply faster/bigger eMMC modules I can swap out the slower/smaller against a faster/bigger one
  21. Like
    Lion Wang reacted to TonyMac32 in Banana Pi Zero   
    Right, my comment on eMMC is purely about reducing/removing interconnects, the primary failure point in most systems.  Speed is secondary in such embedded systems.  I would ideally use the SD card only for data storage, for instance data logging/etc.  
  22. Like
    Lion Wang reacted to guidol in Banana Pi Zero   
    I think nobody has a complete "perfect" product....neither "Orange Pi" nor "Banana Pi" nor "Nano Pi" nor "Raspberry Pi".
    Every product has some details that could be better (lower heat, better documentation, better linux-images, better cases, less binary blobs).
    So I got some of every sort
    But - I personally - like the wiki from FriendlyElec/FriendlyARM at
    http://wiki.friendlyarm.com/wiki/index.php/Main_Page

    Most - NOT ALL - pages does include very interesting and valuable informations for me (PinOuts and HowTos, FAQ).
    OK some should be more actual - but there are many pages for many diffrent models and if ne page hasnt the information then I could find mostly the information at a page of a other model. 
     
    The downside - their forum seems mostly supported from users to users. No technican seem to take a look here on a daily basis
  23. Like
    Lion Wang reacted to lvmc in Banana Pi Zero   
    @Lion Wang SinoVoip's gitbooks has to be reviewed. Technical information is not consistent and English is not good enough, it has to be fixed urgently. Over the last years I have been seeing many Chinese companies doing good products or at least pursuing to build good products but failing on how to communicate and support customers, think about it. Never forget that customers don't care about how hard is to build a new product or how insane is to run a business, they only care about how good the product is.
     
    @Tido gave a good suggestion... before releasing any new product and during the entire product lifespan do short technical / writing meetings with your technical team to consolidate knowledge.
     
    The entire problem here seems to be about communication, as always. Most of Chinese companies have good engineers that doesn't even speak or write in English. If it is the case, hire someone that could help you to fulfil this gap, as soon as possible.
     
    @TonyMac32, @chwe thank you for focusing on the real problems, not at person level discussions. In just a few questions I think you got the answers you were looking for. That is a good start point.
     
    @tkaiser I would like to suggest you to just 'stop' buddy, please.
     
    Let's give the last chance to SinoVoip understand, change, react and SOLVE the main issues. Everything said here is applicable for any hardware supplier.
  24. Like
    Lion Wang reacted to TonyMac32 in Banana Pi Zero   
    Indeed you do, however it does not have "CON4" anywhere on the board silkscreen that I see, and being a 2x2 header alignment is still a bit of a question, especially when Pin1 is marked to be on the right-hand side, which is non-conventional compared to the rest of the board.  Not saying anything is inherently wrong, the schematic is there, is labelled, but I for one, a senior electrical engineer, did not notice it, instead seeing an unlabelled 2x2 on the physical device.  This should be on your page explicitly labelled, and probably a silkscreen adjustment made.
     
    [wishlist]
     
    Now, were it a 2x3 with 2 of those pins being a V_in....  Now that would certainly be useful and meet the approval of many.  Not to mention making orientation a non-issue as it would then be non-ambiguous.  ;-)
     
    [feedback]
     
    Do the various test points exist in hardware, such as the "TV-out" (TP8?)?  If not they need removed, simply because you are referring to the schematic as an ultimate resource (as it should be)  That said, TV-out is a Pi Zero feature...
     
    If you are open to a feedback, I would say a good variant would be one of these without wifi, but instead with the additional USB's available via header, a position for a barrel jack or direct-solder power input, and an eMMC.
     
     
  25. Like
    Lion Wang reacted to chwe in Banana Pi Zero   
    Nice to get a fast response. But when you've ethernet there, this should be on your schematics! and described somewhere.  Most people would expect that the connector might be for powering (or maybe the USB otg). And to improve things, make sure that this information is not only visible here in the armbian forum.  It should also be in your documentation for this board.