trewq

Ok, so, I went a little overboard with this but here is my current NanoPi Neo setup. They are all running the latest Ubuntu build, if anyone wants the output of anything let me know. 20 units in total.
 

 

Ok, so, I went a little overboard with this but here is my current NanoPi Neo setup. They are all running the latest Ubuntu build, if anyone wants the output of anything let me know. 20 units in total.
 

 

Well, support for eMMC was obvious since weeks (by looking into FA's github repo) but we didn't know whether SD card slot is still present (when missing like on the C.H.I.P for example that would lead to some trouble flashing a new OS -- now confirmed that slot is present and eMMC has to be populated by a tool/script) and we still don't know whether eMMC is optional or not.
 
At least the name of the OS image they provide (nanopi-air-eflasher-sd8g.img.zip) let me believe that the eMMC will be 8 GB in size.

There we go. Sorry, wasn't sure what was actually needed so I played it safe and included the same as the ones you linked further above on github.

Well, at least it's obvious from the graphs that cpuburn-a7 was not running at all (or to be more precise: it ran few milliseconds and then it crashed) so you ran into the same problem as @eperie above: Increasing load --> dropping voltage --> board freezing or starting to behave totally weird.
 
Ok, lesson learned. I shouldn't encourage users to run heavy stuff on boards with an inappropriate DC-IN connector. Since you either need ultra short USB cables that are rated 20AWG or 22AWG or power the board reliably with Dupont jumper wires through the 4 pin header next to the upright USB jack.

No one is delayed.

my new USB disk 

BTW: I use passive PoE with RPi B+ (surveillance cameras) with 24V or 48V PSUs and utilizing the 2 unused Ethernet cable pairs for power with simple step-down converters at the 'camera' side (24V is ok since cables aren't that long, 48V are only needed when trying to get close to specification limits of 100m).
 
When starting to play with Oranges I did some research about input voltage range: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=751 
 
So depending on cable lengths one might save the step-down converters and simply inject 6.5V to end up with 4.5V - 5.5V based on distance and unfortunately also load (the latter is important since load peaks will automagically lead to temporarely voltage drops). I also suggested to Steven/Xunlong to provide this passive PoE approach directly on board (connecting the 2 PoE cable pairs to VCC/GND directly) but he didn't liked the idea.
 
The power requirements FriendlyARM wrote in their Wiki are reasonable since H3 doesn't come with a PMIC and therefore USB consumers might easily exceed power requirements according to specs (500mA per port -- at least with Orange Pi PC it works perfectly to attach one 2.5" HDD to each USB port that consume close to 3A at spin-up! Maybe that's the reason Xunlong provides a 5V/3A PSU for the boards)