FriendlyARM NanoPC-T2 Board Gets More Storage, WiFi & Bluetooth, Stays Cool, and Costs Less

FriendlyARM NanoPC-T1 board powered by Samsung Exynos 4412 processor with 1GB RAM and 4GB eMMC flash was unveiled at the start of 2014 for $69. The company has now announced NanoPC-T2 with Samsung S5P4418 processor with 1GB RAM, and 8GB Flash, as well as WiFi and Bluetooth, as Gigabit Ethernet all of which were missing in the first version. NanoPC-T2 also has a power management chip, and a larger heatsink, meaning that it does not suffer from overheating like NanoPi2 according to FriendlyARM.

NanoPC-T2NanoPC-T2 specifications:

  • SoC – Samsung S5P4418 quad core Cortex A9 processor @ up to 1.4GHz with Mali-400MP GPU
  • System Memory – 1GB 32bit DDR3 RAM
  • Storage – 8GB eMMC flash, and 1x SD card slot (on the bottom of the board)
  • Connectivity – Gigabit Ethernet, 802.11 b/g/n WiFi and Bluetooth LE 4.0 (Ampak AP6212) with on-board chip antenna and 1x IPX antenna connector
  • Video Output / Display I/F- 1x HDMI 1.4a, LVDS, MIPI DSI, 0.5 mm pitch SMT FPC seat for type-A full-color LCD (RGB: 8-8-8)
  • Audio I/O – HDMI, 3.5mm audio jack, 1x on-board microphone
  • Camera – 1x DVP interface, 1x MIPI CSI interface
  • USB – 2x USB 2.0 type A host ports; 1x micro USB 2.0 OTG port; 2x USB 2.0 host port via 8-pin header
  • Expansions Headers – 30-pin header for GPIO, 8-pin header for power signals, reset and LED 1-2
  • Debugging – 4-pin header for serial console
  • Misc – Power switch, 1x power & 2x user LEDs, RTC battery header, boot selection button (SD card / eMMC)
  • Power Supply – 5V/2A via power barrel; AXP228 PMIC
  • Dimension – 100 x 60 mm (6-layer PCB)
Click to Enlarge
Click to Enlarge

The board can run Debian and Android from either anSD card or eMMC flash using the boot selection button. The Wiki page is currently empty, but should eventually have all the technical details needed to get started and more.

NanoPC-T2 board will launch on February 28, 2016 for $59 + shipping on FriendlyARM shop. Individuals based in South and North America will instead be able to purchase it from Andahammer.

Support CNX Software - Donate via PayPal or become a Patron on Patreon

13
Leave a Reply

avatar
13 Comment threads
0 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
9 Comment authors
tkaiserTheguyukPeter Scargillroel Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
hoangdinh86
Guest
hoangdinh86

Why not 2GB RAM. Next to Odroid C2

Armer
Guest
Armer

hoangdinh86 :
Why not 2GB RAM. Next to Odroid C2

Yes, the odroid-C2 looks much better and cheaper than this guy except for the on-board wifi&ble.

data
Guest
data

a bit pricey compared to competition now. any one actually know lithography process node of this samsung soc chipset (I mean with some official source specifiing it) or power consumption test ?

roel
Guest
roel

To me it looks a nice board 8GB emmc, wifi, bluetooth, usb expansio headers, full size sd-card and all ports on the same side. I only wonder what about the samsung processor. There is not much information. Does it have a vpu (with h265 support), does it have mainline support, how is it performace.
59$ is not so expensive. If You want to buy an odroid with emmc, You will be on a higher price, and you don’t have wifi and bluetooth.

Peter Scargill
Guest

Despite my best efforts at getting answers out of FriendlyArm, the NanoPi T3 (and I’d guess the T2 is the same) SD Android comes in at 4GB and nothing I can do including instructions from FriendlyArm will increase that. I have a 64GB SD card and almost all of it is wasted. There HAS to be a way to expand to use the whole 64GB as internal memory – but I’m not getting anywhere.

Theguyuk
Guest
Theguyuk
tkaiser
Guest
tkaiser

@cnxsoft
Most FriendlyARM boards aren’t Allwinner based but Samsung/Nexell, Pete’s PC T3 using an S5P6818 (Cortex-A53) and the T2 using S5P4418 (Cortex-A7). Both share almost the same kernel (unfortunately regarding T3/M3) so most instructions apply to both.

I would use an x86 Xenial installation, do a backup of the card and then try to resize the data partition using GParted there. To do a device backup without wasting to much space I would recommend something like this (replacing /dev/sdd with the SD card’s device node):

Peter Scargill
Guest

Ok I’m part way there. A variation on FriendlyArm’s “solution” which simply would not work – turn out it was nearly there.

Flash Android – and immediately pop the SD into a Linux machine -Raspberry Pi is fine – why they didn’t put out some Windows utilities I don’t know – they seem to assume everyone has a Linux machine whereas in the west the VAST majority of us use Windows – however….

With the SD in my Raspberry Pi – I checked /DEV/ to make sure there was an SDA – if it comes up as SDB change accordingly..

sudo parted /dev/sda unit % resizepart 4 100% resizepart 7 100% unit MB print

then

sudo resize2fs -f /dev/sda7

I tried variations including that recommended by Friendlyarm which didn’t have the extra % signs – theirs didn’t work – this does – so take the SD out of your machine and into the T3. HOLD the BOOT button, turn it on, let go of the boot button a couple of seconds later – voila – a minute later, Android pops up I have one with 32GB and another with 64GB – ideal for media centres!!!

The bit I’m still missing – if I power off and on and DON’T hold the boot button – it boots into EMMC – need to know how to have it always boot from the SD (8GB on Android is pretty useless)…. any ideas anyone?

Oh- KODI and other media stuff – work pretty well.

Member

Resizing the filesystem is a common Android problem, it is not specific to this board. Google around for various fixes.

The EMMC contains a signature that says it contains a valid boot image. Wipe out that signature (usually the first 10 bytes or so of the EMMC chip) and it will boot from the SD Card. This is controlled by the ROM on the chip. This is also a generic ARM feature that is not specific to this board.

Peter Scargill
Guest

Thanks for that Jon but an expert at this I am not. How would you wipe that out?