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
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
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
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?)
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.
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.
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.
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
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.
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?
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?
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
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
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.
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
@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.
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.
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.