I rushed that last post, so I fixed the typoes in it.
I also forgot to say:
You can get the Armbian for the O-Pi system, and for this O-Pi Zero; there is a Text/Console version of it that is perfect to run for robotics or as a headless server, more so for the 256MB version.
The 256MB version can run a Windows GUI system like the Model A/A+ Raspberry Pies do as they also have 256MB. But without video, you do not really need a GUI since you can telnet/SSH to it. I have seen though, on some systems running as a headless server with a GUI and being accessed through VNC. This might work on these systems without Video Output, as their AllWinner CPUs does have video in it.
In comparing the O-Pi Zero to the NanoPi Neo; the Neo does not have Wifi, the O-Pi Zero does. You can give the Neo Wifi through a USB Wifi adapter, that is pretty cheap but it takes away your USB Port.
Though the O-Pi Zero has Ethernet, it is turned off in the system's configuration and needs to be activated. This is not an issue with Armbian, but it with the O-Pi Raspbian system; though it is a quick and easy fix by changing a couple commands in the system's configuration file. With the NanoPi Neo, Ethernet is always on.
Both have a Serial Debug Port where one can plug in their PC and have immediate Console access to it. It is great to see how the system is booting and making changes to the config files directly with needing to know IP numbers and ports. Strangely, the NanoPi sells a TTL to Serial adapter to connect to this port, the O-Pi does not but one can use this NeoPi adapter on the O-P as I can see the pins are set the same. As seen, the adapter can be used on any of their system that has the Debug Port. They claim that one can use it on the R-Pi but the R-Pies do not have a debug port, one would have to pull out of the serial port from GPIO and turn it on through the config file. The adapter costs about $4.
http://www.friendlyarm.com/index.php?route=product/product&product_id=89 Linux, like UNIX, works best with 1GB or more of RAM. It works great with smaller RAM footprints like these units have. For me the bring back the old days of programming in that you need to write your programs as small as possible, not that one would exceed 256MB of RAM or even 512MB of RAM with their programs. For example, it one dares to write a search engine (or take out that is out there and convert to run on these systems), the database for the search engine will take up GIGs of storage space, and a hard drive is too slow to access this information! But on a Solid State system or a RAM Disk, this would be a lot faster but the RAM limitation of these boards makes it an issue so that you're stuck with the slower SSD. Creating a RAM Disk inside Linux is quite simple and easy. I'll post up a How To guide as soon as I get my information together.