zador.blood.stained

Or here: https://github.com/apritzel/linux/commits/sunxi64-4.9-testing
 
In any case: no proper vendor support and no proper community support means no official Armbian images. At least until mainline reaches stable and functional enough state so WIP/test images can be made with minimal effort.

Ok, guys ! I found my hardware issue : I've been caught myself with an SDCard that becames crappy !
 
For the xradio issue, I don't know if it was also related, but I've created image with Zador stuff, although I had to tweak a bit the DT, and it is now working fine.
 
@Zador, the tweak needed is related to the fact that PL7 was already defined in PiOne, but due was slipped into pio instead of r_pio (same issue found few weeks ago for PiPC https://github.com/igorpecovnik/lib/commit/31c3133cf65af66197b0e78f92eae835615a90b1 )
I will commit this fix in few minutes along some removal in PiZero since we can reuse the PL7 from PiOne, simply by using same names.
 
EDIT : here is the first fix : https://github.com/igorpecovnik/lib/commit/5fff38add9873b50bc71d540573e4294bc97c10d, and here the redundancy cleanup : https://github.com/igorpecovnik/lib/commit/fdaadb42d7587371a7cb7f1184ade5915cd77924#diff-ef59beeea2dd85451fb9bf2905fb7ebf and https://github.com/igorpecovnik/lib/commit/369d3928e7154ac12c34f0e2bc4ce0e24636cb4e#diff-ef59beeea2dd85451fb9bf2905fb7ebf

@tkaiser, @Igor
 
Any objections against adding an issue template like this to our build script repository?
IMO it would be nice to keep the issues clean and split build script support from everything else.
So far I came up with this:
 
 

Probably some generic userspace related instructions like setting up /etc/network/interfaces. Allwinner specific stuff like xradio kernel module should work out of the box and doesn't need any instructions in stable leleases AFAIK.

https://github.com/fifteenhex/u-boot/commit/56160c82d5f273bee8fdf1045eb415f9ae0c002c

With this board it's tricky - why would an "average Joe" buy a board with no display output (CVBS requires soldering or making a special cable - so not an option for an "average Joe") in the first place? It can't be a good media player or a desktop replacement, so you'll need to find a good use case to choose it over Orange Pi Lite/One for example.
 
OK. That's good, because while hardware situation usually doesn't change over time, software will improve and end users need to be aware about that.
 
As a relatively small Chinese company Xunlong does its best - produces cheap hardware in large quantities and different variations.
 
Well, just look at Pine64 kickstarter page. I'm sure that if they didn't advertise a development board with smartphone/tablet grade hardware as a "super computer" people would have less problems with current software support.

With this board it's tricky - why would an "average Joe" buy a board with no display output (CVBS requires soldering or making a special cable - so not an option for an "average Joe") in the first place? It can't be a good media player or a desktop replacement, so you'll need to find a good use case to choose it over Orange Pi Lite/One for example.
 
OK. That's good, because while hardware situation usually doesn't change over time, software will improve and end users need to be aware about that.
 
As a relatively small Chinese company Xunlong does its best - produces cheap hardware in large quantities and different variations.
 
Well, just look at Pine64 kickstarter page. I'm sure that if they didn't advertise a development board with smartphone/tablet grade hardware as a "super computer" people would have less problems with current software support.

USB VID/PID suggest that this device is compatible with the Easycap driver, so I enabled it in the kernel config: https://github.com/igorpecovnik/lib/commit/c336b6e7034933584f269f874c49ccdebfd4573e

I mean that outside links should not contain exact kernel and release versions, they should look like
http://image.armbian.com/betaimages/Armbian_Nightly_Orangepizero_Ubuntu_xenial_default.7z
or
http://armbian.com/download?type=nightly&board=orangepizero&release=xenial&kernel=default
that should get HTTP 302 redirect to actual image file Armbian_5.24.161208_Orangepizero_Ubuntu_xenial_3.4.113.7z
 
 
Meaning of "legacy" or "vanilla" depends on board family/SoC and it needs to be stated on the download page (like it was before, but it should be shorter)
I don't have a better word to replace "legacy", but "vanilla" should probably be changed to "mainline"
For example in case of sun4i/sun7i it would be good to have at least this:
Legacy kernel - optimal for multimedia and desktop usage scenarios Mainline kernel - optimal for headless server usage See "Status matrix" for detailed comparison and we could have a table (I'm assuming Markdown tables are supported) that would show that currently HDMI audio, VE accelerated video decoding, DRM video driver and Mali are not available on mainline
 
Maybe nightly tab should also have "buttons" instead of links for consistency, and images buttons/links should be on top and repository info/instructions should be lower

Overall comparing OPi Zero (in its current state and with its design decisions and target use cases) to Raspberry Pi is not adequate in my opinion. Double inadequate if you can't figure out how to enable SPI/spidev and compare CPU performance between H2+ and BCM283* before complaining about SoC temperatures.
 
Since there will be updates to the review according to @MickMake this review is OK as a quick look / first impressions.

If it says that pkg-config wasn't found, then it may be a good idea to install it (it should be present in the package with the same name)

Hm. Since this is not the first time similar error happens, we could use a timeout command in postinstall script to run headers compilation with a reasonable value of 10 minutes.

I know it is just shouting in the desert but nowbody should buy a board and then ask a third party for support.
Instead we all should write the seller and say: You know what? Your product looks great but I will not buy a single one neither advice anyone to buy until third parties (sunxi, armbian...) say yes, this board has released all required docs to support it.
 
Or if you have purchased one return it back: You sell it as open source. I have found your sources are missing. Here it is and give me my money back

I suggest you use the search function in the forum for an answer. Before opening a new topic

Which doesn't change anything: https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
 
Most of the features (Ethernet, DVFS, THS, display) are still not done, so until they are present in official releases there will be no mainline images for H3 based boards for end users.

What do you expect to hear? Some magic spells that will turn a crappy SD card into a Samsung Evo Plus? Sorry, this probably won't happen. If sequential write/read tests don't show you any errors it doesn't mean that this card will behave perfectly in other scenarios - i.e. combined reads and writes of blocks of different sizes.
 
There is only one reliable solution:
 
 

I don't agree that bringing here Raspberry Pi users would benefit the Armbian project.
First, another Debian/Ubuntu derivative means fragmentation of user base - not an improvement for Raspberry Pi project.
Second, IMO Armbian project needs more developers, experienced users/experts and maybe sponsors, and not a lot of inexperienced users who bought an SBC for no reason and now don't know what to do with it.

I don't agree that bringing here Raspberry Pi users would benefit the Armbian project.
First, another Debian/Ubuntu derivative means fragmentation of user base - not an improvement for Raspberry Pi project.
Second, IMO Armbian project needs more developers, experienced users/experts and maybe sponsors, and not a lot of inexperienced users who bought an SBC for no reason and now don't know what to do with it.

If you place your changed config in userpatches/linux-$LINUXFAMILY-$BRANCH.config (i.e. linux-sun8i-default.config) it should be loaded instead of default one from lib/config/kernel/

Fixed done and committed as explain in https://forum.armbian.com/index.php/topic/3029-mainline-ethernet-driver-h3/

I mean that outside links should not contain exact kernel and release versions, they should look like
http://image.armbian.com/betaimages/Armbian_Nightly_Orangepizero_Ubuntu_xenial_default.7z
or
http://armbian.com/download?type=nightly&board=orangepizero&release=xenial&kernel=default
that should get HTTP 302 redirect to actual image file Armbian_5.24.161208_Orangepizero_Ubuntu_xenial_3.4.113.7z
 
 
Meaning of "legacy" or "vanilla" depends on board family/SoC and it needs to be stated on the download page (like it was before, but it should be shorter)
I don't have a better word to replace "legacy", but "vanilla" should probably be changed to "mainline"
For example in case of sun4i/sun7i it would be good to have at least this:
Legacy kernel - optimal for multimedia and desktop usage scenarios Mainline kernel - optimal for headless server usage See "Status matrix" for detailed comparison and we could have a table (I'm assuming Markdown tables are supported) that would show that currently HDMI audio, VE accelerated video decoding, DRM video driver and Mali are not available on mainline
 
Maybe nightly tab should also have "buttons" instead of links for consistency, and images buttons/links should be on top and repository info/instructions should be lower

Tried with Armbian_5.24.161207_Pine64_Ubuntu_xenial_3.10.104_desktop.7z: http://pastebin.com/rR8QKUqq
 
1 GB pre-production sample. First boot took quite some time while being in u-boot but I've to admit that I did not pay that much attention.

You can find some info and datasheet here: https://linux-sunxi.org/AXP209
Section "Control and operation" in the datasheet should answer most of your questions.
 
AXP209 comes from standby and enables all necessary regulators to boot the board
 
AXP209 processes long press and shuts down most of regulators
 
AXP209 IRQ output is connected to A20 NMI input, this way it can send power related events to the CPU.
In case of short power button press, AXP209 sends an IRQ to the CPU, and the kernel driver exposes this as a press of power button of a virtual input device.
In case of long power button press, A20 doesn't have a choice - AXP209 will simply cut off the power.

You can't run a motor directly from GPIO since it won't provide even near enough current. You need to use a relay, a transistor or a special motor control IC, otherwise it won't work.
 
Also physical pin 10 is GPIO G7 which would be pin 199 for sysfs interface.

@Dani_RM
There were some u-boot related issues with older Armbian images related to boot device detection. If you have any Linux based host or another board, can you please
download http://apt.armbian.com/pool/main/l/linux-u-boot-orangepiplus2e-default/linux-u-boot-orangepiplus2e_5.23_armhf.deb extract u-boot-sunxi-with-spl.bin from this package (using dpkg-deb -R or any archive manager that can open .deb files) update u-boot on SD card with Armbian image using dd: dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8 where /dev/sdX is a device node representing your SD card in card reader
 
... or just wait for beta image release or new official release for this board