FriendlyARM NanoPi NEO & AIR
|FriendlyARM NanoPi NEO & AIR|
|Dimensions||40mm x 40mm|
|Release Date||July (NEO) / Oct (Air) 2016|
|Website||NanoPi NEO / NanoPi Air|
|SoC||H3 @ 1.2Ghz|
|DRAM||256MiB (K4B2G1646Q-BCK0) or 512MiB (K4B4G1646Q-BCK0) DDR3|
|Power||DC 5V @ 2A via microUSB or pin headers|
|Audio||microphone, stereo line-out, I²S and S/PDIF on pin headers|
|Network||10/100Mbps Ethernet (H3 built-in PHY) or BT4.0/WiFi 802.11 b/g/n (Ampak AP6212)|
|Storage||µSD and 8GB eMMC (Air)|
|USB||1 USB2.0 Host (NEO), 1 USB2.0 OTG|
Small, square board, blue soldermask, ⌀3mm mounting holes in the corners. USB type-A, Ethernet jack (with integrated magnetics) and four-pin header for UART/power near one of the edges, microSD and USB micro-B at opposite edge mounted on top side, 12 and 24 GPIO pin headers (not fitted, pads only) near other edges. Allwinner H3 and single DDR3 chip mounted on the bottom. Sticker indicating amount of RAM is placed on the Ethernet jack. Device can also be ordered without USB and Ethernet soldered (see gallery below)
On the top side of the board, next to USB A connector, the following is silkscreened:
FRIENDLYARM NanoPi NEO
Starting in September 2016 a new PCB revision 1.1 is available (changes: audio signals on the GPIO header, voltage regulator)
The H3 chipset support for NanoPi NEO and NEO Air has been included in mainline kernels since 4.2. Most of the board functionality works out of the box, but support for many features has been added rather recently, which means that a fairly recent kernel version is required. Some features (hw accelerated crypto, graphics/video features, thermal, and DVFS) are still being worked on. For a more comprehensive list of supported features, see the status matrix for mainline kernels. In addition, legacy 3.4 kernels are available in various work-in-progress git branches.
See the Manual build section for more details.
FriendlyARM's UbuntuCore with Qt-Embedded image can be found here. It boots a new variant of Allwinner's 3.4.39 BSP kernel, USB and Ethernet are working fine. Armbian images for NEO based on 3.4.112 (containing new IoT low power settings) or 4.6.7 can be found here.
FriendlyARM provides a BSP based on a newer Allwinner 3.4.39 variant on Github.
You can build things for yourself by following our Manual build howto and by choosing from the configurations available below.
Use the nanopi_neo (supported since v2016.11). For NanoPi NEO Air, there is an upcoming U-Boot configuration patch. If it is not yet configuration available, instead pick the orangepi_one build target. The U-Boot repository and toolchain is described in the Mainline U-Boot howto.
The H3 boards can boot from SD, eMMC, NAND or NOR flash (if available), and via FEL using the OTG USB port. In U-Boot, loading the kernel is also supported from USB or ethernet (netboot).
- Siarhei Siamashka's branch '20151207-embedded-lima-memtester-h3'
- Yann Dirson's fork added a few more fixes and adopted most of
- Boris Lovosevic' great initial work on Allwinner's H3 kernel
Configure this kernel using sun8i_h3_defconfig, the rest is explained in the kernel compilation guide.
When booting the legacy 3.4 kernel with the mainline U-Boot, add the following line to boot.cmd:
setenv machid 1029 setenv bootm_boot_mode sec
Some other legacy kernel repositories:
- 3.4-lichee-based kernel, based on work by ssvb and loboris
- Yocto support here glues together all the required parts to get this kernel to work with mainline u-boot, as well as accelerated X11/GLES support
- A newer H3 BSP variant appeared with tons of fixes which has been made available by FriendlyARM.
- A cleaned up fork has been adopted by Armbian project. On top of that Armbian maintains a bunch of 3.4.x patches for H3 devices.
The H3 SoC is supported by the mainline kernels. For cpufreq, thermal, and HDMI audio support a) third party patches or b) a pre-patched distro (e.g. Armbian) is still needed (cpufreq support will appear in 4.18). A number of features have stabilized only recently (Ethernet in 4.15 HDMI in 4.17), so make sure you're running a recent kernel if these features are needed.
The development process, links to patches and links to kernel fork repositories are listed on the Linux mainlining effort page. Patches can also be found from the arm-linux mailing list.
Repositories with H3 patches:
- Ondřej Jirman's branch for H3 based orange Pi (kernel 4.17) (work-in-progress DVFS)
- CPU frequency and voltage scaling (cpufreq)
- Thermal regulation (if CPU heats above certain temperature, it will try to cool itself down by reducing CPU frequency)
- HDMI audio support (from Jernej Skrabec)
- Configure on-board micro-switches to perform system power off function
- Wireguard (https://www.wireguard.com/)
Use the sun8i-h3-nanopi-neo.dtb or sun8i-h3-nanopi-neo-air.dtb (depending on the board) device-tree binary.
Both NanoPi NEO and NEO Air feature one 12-pin and one 24-pin GPIO header. Air's pin-out for those headers and the DVP camera connector can be found here. On NEO PCB rev. 1.0 analog audio signals were present on the 12-pin header that were replaced by digital audio starting with PCB rev. 1.1. With PCB rev. 1.3 position of the UART debug header has changed and a new 5-pin analog audio header has been added (same as on NEO 2 and NEO Plus 2). All pin-out information in FriendlyELEC's wiki page.
Tips, Tricks, Caveats
No FEL button. UBOOT/FEL signal pulled-up by R254 (10kΩ, mounted on the bottom side, close to H3).
The board has two LEDs, mounted on the top side, between micro USB and microSD:
- A red LED, labelled "PWR", connected to the PL10 pin and to 3.3V via weak pull-up, thus being able to represent three states:
- full brightness when GPIO is set to output high
- reduced brightness when GPIO is set to high impedance state
- turned off when GPIO is set to output low.
- A blue LED, labelled "STAT", connected to the PA10 pin.
Voltage regulators / heat
NanoPi NEO/Air use the same voltage regulator as NanoPi M1 and Orange Pi One/Lite switching between 1.1V and 1.3V (SY8113B datasheet). Unlike the Xunlong boards which contain a thick copper layer inside the PCB to spread heat away from the SoC FriendlyARM chose a different design. This and maybe the smaller PCB size lead to higher temperatures compared to Orange Pis and in case you want to operate the NEO under constant high load think about adding a heatsink (FriendlyARM provides one combined with a 2mm heat pad that can be securely mounted on the board -- see gallery images below.
On NanoPi NEO PCB rev 1.0 U7 next to DRAM is an LDO voltage regulator that provides 1.2V for various SoC parts and 1.1V for the internal Ethernet PHY. It overheats a lot and is rated 500mA max. When ordering FriendlyARM's heatsink maybe combining it with a larger heatpad that covers the whole SBC's surface is a better option than now (using a small 15x15 heat pad that connects SoC with heat sink but decreases heat dissipation for all other SBC components this way).
NanoPi NEO is available with 256 MiB or 512 MiB but only in single bank configuration. NanoPi Air is available with 512 MiB (also single bank).
DRAM is clocked at 432 MHz by the hardware vendor. User:Tkaiser did some consumption and thermal measurements just to find out that the board deadlocks pretty fast when running lima-memtester regardless of DRAM clockspeed (happens within minutes) but as soon as an annoying fan is added to FriendlyARM's heatsink blowing air between heatsink and SoC the board survives lima-memtester running at 600 MHz for several hours (board found powered off after increasing up to 672 from userspace after another hour). Since visual feedback is impossible on a board that lacks any display output we should consider 432 MHz to be a sane default since it both helps decreasing heat and consumption.
Based on User:Tkaiser's tests reducing DRAM clockspeed by 24 MHz more (with BSP kernel 408 MHz is the lowest allowed clockspeed) is even better since it does not affect performance that much (negligible according to tinymembench) but both temperature and consumption are lowered a lot by switching from 432 MHz to 408 MHz. Test results here and description of test setup there (using another sunxi board's AXP209 to do consumption measurements). BSP kernel boots happily with CONFIG_DRAM_CLK=408 and CONFIG_SYS_CLK_FREQ=480000000 set in u-boot 2016.07.
The single bank DRAM configuration is slower than dual bank configuration on all other H3 devices. Even more when taking the different DRAM clockspeeds into account. Using tinymembench and looking at standard memcpy numbers, NEO/Air clocked with 408 or 432 MHz show ~435 MB/s while other H3 boards with dual bank DRAM clocked at 624 MHz reach ~900 MB/s (for more details see post #13 in this thread in Armbian forums). When using cpuminer then NEO/Air clocked with 1200 MHz achieve 1.83/1.85833 khash/s with DRAM clocked at 408/432 MHz while an Orange Pi Lite with identical settings (HDMI/Mali disabled and also clocking at 1200 MHz) achieves 2.10867 khash/s with DRAM clocked at 624 MHz (that's a ~12 percent performance loss with this specific workload only due to different DRAM configuration and clockspeed)
The one USB host port exposed as type A receptacle is usb3. Both usb1 and usb2 are available via solder holes.
On NanoPi Air analog audio out and mic in is available on 4 solder pads next to the camera connector. Please check schematic for details.
Locating the UART
Four-pin UART0 header is placed next to USB type-A connector. Pinout: GND, 5V, TX, RX. Pin 1 (GND) is the one furthest from the board edge. Logic voltage is 3.3V. For more instructions refer to our UART Howto.
NanoPi NEO Air
- Air device page on FriendlyARM wiki page
- NEO device page on FriendlyARM wiki page
- Armbian forum thread for both devices
- NEO Air Schematic for PCB rev 1.0
- NEO Schematic for PCB rev 1.0
- NEO Schematic for PCB rev 1.1
- NEO Schematic for PCB rev 1.2
- board mechanical drawings (dxf)
See the manufacturer's device pages above since links change from time to time.