NanoPi M1 Allwinner H3 Development Board with HDMI, CVBS, Ethernet and 3 USB Ports Sells for $11 (Sort of)

FriendlyARM has been very busy since the beginning of the year, as they’ve already released NanoPi 2 Fire, NanoPC-T2, and NanoPi-M2 boards, all based on Samsung S5P4418 processor so far in 2016. But they’ve not stopped, as the company has now launched NanoPi M1 board powered by Allwinner H3 processor with a similar form factor as NanoPi-M2, similar features as Orange Pi One, except they added two extra USB ports, an AV port with composite video and stereo audio, an on-board microphone, and an IR receiver.

NanoPi_M1

NanoPi-M2 board specifications (highlights show improvements or differences over Orange Pi One):

  • SoC – Allwinner H3 quad core Cortex A7 @ 1.2 GHz with an ARM Mali-400MP2 GPU up to 600 MHz
  • System Memory – 512 MB DDR3 (1GB as option)
  • Storage – micro SD card slot
  • Video & Audio Output – HDMI and 3.5mm jack for CVBS (composite + stereo audio)
  • Connectivity -10/100M Ethernet
  • USB – 3x USB 2.0 host ports, 1x micro USB OTG port
  • Camera – DVP Interface
  • Expansions – 40-pin Raspberry Pi compatible header with UART, SPI, I2C, PWM, GPIOs, etc…
  • Debugging – 4-pin header for serial console
  • Misc – Power and reset buttons; 2x LEDs; IR receiver; on-board microphone.
  • Power Supply – 5V/2A via micro USB port; 4.7V ~ 5.6V via VDD pin on “Raspberry Pi” header.
  • Dimensions – 64 x 50mm (Orange Pi One dimensions: 69mm × 48mm)

The board currently supports Ubuntu Mate, Ubuntu Core or Debian. Some documentation is already available on the wiki, but the link to the firmware are wrongly pointing to NanoPi2 images for now, which are not usable with NanoPi M1. It’s quite likely it will be supported by armbian too. The schematics (PDF) and mechanical (DXF) file are also up for download.

NanoPi-M1_Case
The company can also provide a case for $3.49, or you can print it yourself if you prefer.

NanoPi-M1 is only one dollar more than Orange Pi One, but adds more features and offers better documentation. Is there a catch? Of course there is, as while the board is listed for $11 on FriendlyARM, shipping adds at least $10, bringing the total to $21. It’s still a pretty decent price, but not quite the bargain you may have hoped for. [Update: The board is sold on DX.com for $22.46 shipped]

Share this:
FacebookTwitterHacker NewsSlashdotRedditLinkedInPinterestFlipboardMeWeLineEmailShare

Support CNX Software! Donate via cryptocurrencies, become a Patron on Patreon, or purchase goods on Amazon or Aliexpress

ROCK 5 ITX RK3588 mini-ITX motherboard

36 Replies to “NanoPi M1 Allwinner H3 Development Board with HDMI, CVBS, Ethernet and 3 USB Ports Sells for $11 (Sort of)”

  1. Shipping is not so bad.

    Indeed for a single board it is $10 but I just check how much it will be for 10 boards to Europe and $31 total seems fair enough.

  2. I fail to see a power barrel but the wiki is quite clear that the board can be powered (more reliably 🙂 ) through GPIO pins 2/4 and 6 like Orange Pi PC/One. So the only interesting question is how the voltage regulator behaves. According to schematic it should work like on Orange Pi One switching between one lower voltage and 1.32V.

  3. According to script.bin used they do not adjust VDD_CPUX voltage just like with Banana Pi M2+ (sad since the SoC will suffer from overheating way more easily compared to the Oranges) but apart from that it’s a pretty close clone of Orange Pi One/PC. BTW: fully supported by Armbian since 5 minutes ago: https://github.com/igorpecovnik/lib/pull/241

  4. @Jon Smirl
    Currently there’s no Android image available. But you can take the Android image for Orange Pi PC (works out of the box except blue led and ARISC errors since they copied the hardware very closely) or any other you find for H3 (Zidoo X1 or Beelink X2 for example), take FriendlyArm’s or better Armbian’s sysconfig.fex settings (see above) and then follow this guide to overwrite a few sectors with 2 files: https://codearetoy.wordpress.com/2016/01/12/orangepi-pc-android-display-on-dvi-monitor/

  5. @zoobab
    Mainline Ethernet still not ready but montjoie pushed his latest changes just a few minutes ago to his new Github repo. As soon as Ethernet is in a reasonable state we will provide 4.5 OS images too. If you use the Armbian build system you can run mainline kernel on H3 since last Dec already (using USB-Ethernet of course)

  6. Shouldn’t that making a device with a great price/performance ratio for Kodi if you just want AVC and HEVC with 1080p @ 50/60 Hz?

    Kodi on Openelec works fine for me on a Raspi 1 B for me, which also only has 512 MB RAM.

    Kodi is available for Debian Jessie on armhf and from the Wiki it seems they have working graphic drivers — if mplayer works, why should Kodi not?

    Do I miss something?

  7. @Christian
    Look into the OpenELEC forum on orangepi.org — the NanoPi M1 is more or less an exact clone of Orange Pi PC with half the DRAM (and that’s the problem — 512 MB seems sometimes not enough).

    I’m ran FriendlyARM’s Debian image on both Orange Pi PC/One to look around but they did the same as SinoVoip for their BPi M2+ and took the kernel sources from Boris Lobosevic (loboris) but at least FriendlyARM broke something since maximum clockspeed is limited to 1008 MHz with their image (1200 should be safe)

  8. @tkaiser,
    it seems that FriendlyARM at least is publishing latest stuff (datasheet and kernel code). After quick check of their github source, I can confirm that they have at least newer video driver code.

  9. @jernej
    Hm… since I added a patch for Mali r4p0-00rel0 to Armbian yesterday I had a look into linux-3.4/modules/mali/Makefile first and this looks just like loboris’ kernel with a few fixes on top.

  10. @tkaiser
    Thanks for your reply, especially as you seem to be involved in development for those devices!

    It seems there is an Openelec build now with HW acceleration: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=648

    I assume the Orange Pi PC version runs also NanoPi M1.

    This article mentions a NanoPi M1 version with 1 GB, so I guess I should wait for that.

    An explanation what I want it for: Soon there will be DVB-T2 with HEVC 1080p 50 Hz in Germany. I want build my own receiver with tvheadend as backend just for live TV and PVR. The off the shelf solutions are either proprietary and spartanic or have a premium price. I don’t need the other parts of Kodi for movie databases, streaming via Internet, … If Kodi doesn’t work, I guess I will have to use mplayer, which they claim works on the Wiki pages. But Kodi has I nicer interface 😀

    In another comment you mention “4.5 OS images”. You mean images with Linux kernel 4.5?

  11. @Christian
    Jernej’s OpenELEC version for Orange Pi PC will even run without any modification since the only two real differences are: blue instead of red led with different pin mapping, different voltage regulator always at 1.32V (not that good since the SoC gets hotter than necessary). Since shipping costs are rather high if you only need one device Orange Pi PC is obviously the better choice since this is ~17€ (tax free incl. shipping) and the OPi PC stays cooler due to better voltage regulation. With the OPi PC playing 1080p HEVC the temperature just increases by 4°-5°C and consumption depending on the movie’s contents between 0.3-0.8W (maybe 1W with a lot of motion)

    @jernej: You can take the fex from Armbian repo, should work regardless whether you adopt the new BSP kernel or not (IR receiver might be different though).

    And yes, due to the active linux-sunxi community mainline Linux kernel support for H3 exists since months. Main showstopper is still Ethernet (and display and other unnecessary stuff 😉 ). The official ‘road map’ can be seen here http://linux-sunxi.org/Mainlining_Effort but distros like Armbian collect the patches that are floating around to create a working image even if they haven’t landed in the official kernel sources yet (but we still wait for Ethernet before we release an image)

  12. @tkaiser
    Thanks again for your reply — I really appreciate it!

    I just discovered http://www.armbian.com/ and saw that you are very active there also. Is the Orange Pi PC Openelec build based on that in the sense that it uses the same patches and drivers?

    Do I understand correctly that the Ethernet driver is not in mainline yet, but supported in armbian and Orange Pi PC Openelec fork or does it currently not work at all?

    Thanks for now and see you in the other forums!

  13. @tkaiser
    I know, but I think I must stop at some point and start using mainline kernel. It will took a lot of time, but I think it will be worth it.

  14. @Christian
    I’m the author of that OpenELEC fork. We are sharing much of the patches and we are trying to stay compatible, but that it is not always possible due to different goals.

    Ethernet driver is naturaly included in both, OpenELEC and Armbian, but only in those images with legacy (3.4) kernel. There is no OpenELEC version with mainline kernel yet. And yes, ethernet driver is not in mainline kernel yet,

  15. @jernej
    Yes, I saw your id in many posts at http://www.orangepi.org/orangepibbsen/forum.php?mod=forumdisplay&fid=55 and that you already made even a 7 beta. Thanks for your great work!

    Normally I would not care for an older kernel, as many newer features are not that important for a media box. I ask because of the drivers. My plan was to use tvheadend as TV server — I saw that somebody did it with another stick — with the Geniatech T230 and the LinuxTV page says it it supported since kernel 3.19. So I fear that it will not work with a 3.4 kernel. Or are (most) DVB drivers backported?

    But as plan B I continue to run tvheadend on my Raspi 😀

    IIRC you wrote there that you stop accepting patches for 3.4 and switch to mainline. As DVB-T2 here starts in June and I only need it then there is some time left 🙂

    I plan to contribute then with — hopefully few 😀 — bug reports and localization, if needed.

  16. @Christian
    Images include backported media drivers from 4.4 kernel IIRC, so your driver should work although that is not always the case.

    I plan to go on mainline kernel soon after ethernet driver becomes usable but till then, I will try to integrate opensource VPU drivers.

  17. Small update: NanoPi M1 does use the same voltage regulator as known from Orange Pi One (switching between 1.1V and 1.3V so the only currently available H3 board only using a single VDD_CPUX voltage is Banana Pi M2+) but currently it seems nearly all available OS images for Nano Pi M1 do it somewhat wrong so the H3 will be fed all the time with 1.3V (higher temperatures and if used without heatsink also lower performance since throttling jumps in faster).

    At the moment some manual fixes are necessary: http://forum.armbian.com/index.php/topic/1015-nanopi-m1/?view=getlastpost

  18. @gitrix
    For $5 less you get the pretty similar Orange Pi PC or for pretty much the same end price you get the Orange Pi PC Plus (including case, USB to barrel plug DC-IN cable and shipping). With additional 8GB pretty fast eMMC and WiFi. OPi PC (Plus) is also faster since it has a better voltage regulator allowing higher clockspeeds with less throttling occuring.

  19. FriendlyARM told me they decreased the shipping fee to $5 for NanoPi boards:

    Our shipping cost with CHINA POST for one NanoPi family board is $5.
    Eventually we improved this. Hope this is a good news for our customers.

  20. @Peter Scargill
    Actually not having the Play Store is right way to follow Google’s guideline, but they could provide a convenient way to let the users install it, just like Hardkernel is doing for their ODROID boards.

  21. @Peter Scargill
    Hmm… I really don’t understand why people mess around with vendor supplied OS images. Using Armbian (not another distro but an automated build system able to spit out OS images for +40 different SBC in the meantime) the whole installation procedure could be moved from your script to image creation by adding the necessary packages to configuration.sh, adding manual installation stuff to extras, tweaking check_first_login.sh so that the mosquitto password will be set at 1st login and so on…

    All that’s needed is a x86_64 build host (Ubuntu Xenial for best results), then tweaking the image creation process once and from then on it’s super easy to create an absolutely clean OS image already containing all the necessary stuff for any of the +40 SBC we currently support: https://github.com/igorpecovnik/lib/blob/master/documentation/geek-faq.md

Leave a Reply

Your email address will not be published. Required fields are marked *

Khadas VIM4 SBC
Khadas VIM4 SBC