NanoPi R4S headless RK3399 SBC features up to 4GB RAM, dual Gigabit Ethernet, USB 3.0 ports

We’ve seen several tiny ultra-cheap boards for headless applications over the last few years with products Orange Pi Zero Plus or NanoPi R2S which are usually based on 32-bit Cortex-A7 or low power 64-bit Cortex-A53 processors, coupled with up to 512MB to 2GB, and may have some limitations when it comes to Gigabit Ethernet and USB 3.0 speeds.

If you’d like something similar but more powerful, FriendlyELEC is working on NanoPi R4S headless SBC powered by a Rockchip RK3399 hexa-core Cortex-A72/A53 processor with up to 4GB RAM, dual Gigabit Ethernet, and two USB 3.0 ports.

NanoPi R4S preliminary specifications:

  • SoC – Rockchip RK3399 hexa-core processor with dual-Core Cortex-A72 up to 2.0GHz,  quad-core Cortex-A53 up to 1.5GHz, Mali-T864 GPU with OpenGL ES1.1/2.0/3.0/3.1, OpenCL, DX11, and AFBC support, 4K VP9 and 4K 10-bit H265/H264 60fps video decoder
  • System Memory – 1GB DDR3 or 4GB LPDDR4
  • Storage – MicroSD card slot
  • Networking – 2x GbE, including one native Gigabit Ethernet, and one PCIe Gigabit Ethernet
  • USB – 2x USB 3.0 Type-A ports, USB 2.0 via 4-pin header
  • Expansion – 2×5-pin header with 1x SPI, 1x I2C
  • Debugging – 3-pin debug UART header
  • Misc- 1x power LED, and 3x user LEDs (SYS, LAN, WAN), user button, 2-pin RTC battery connector, 5V fan connector
  • Power Supply
    • 5V/3A via USB-C connector or pin header
    • RK808-D PMIC and independent DC/DC enabling DVFS, software power-down, RTC wake-up, system sleep mode
  • Dimensions – 66 x 66 mm (8-layer PCB)
  • Temperature Range – -20°C to 70°C

Note the specifications are preliminary as the information is not available on the main page of the Wiki, and I just found the board on a “hidden” page where you’ll also find the schematics and CAD files for both the 1GB and 4GB RAM.  There will be a heatsink cover most of the top side of the board not already used by connectors and headers. I’m not sure why the company did not place the Rockchip RK3399 processor on the bottom of the PCB as they did with NanoPi M4 since it allows for a larger heatsink and better heat dissipation.

There’s no information about software, but based on past RK3399 products, FriendlyELEC should offer both Ubuntu and OpenWrt images, and typical use case would be routers, networked storage, IoT gateways, etc…

There’s no price information for NanoPi R4S headless SBC, but considering the $50 price tag for the aforementioned NanoPi M4 SBC and features, around $30-$35 for the 1GB RAM version, and $60-$65 for the 4GB RAM model might be in the right ballpark.

Share this:

Support CNX Software! Donate via PayPal or cryptocurrencies, become a Patron on Patreon, or buy review samples

35 Replies to “NanoPi R4S headless RK3399 SBC features up to 4GB RAM, dual Gigabit Ethernet, USB 3.0 ports”

  1. Interesting. A long time ago I needed small and powerful dual-port boxes to serve as on-wire packet capture devices or emergency firewalls. I don’t need that anymore but such a device could perfectly fit. Right now the closest I have is my clearfog, which I manage to power from USB using a USB-to-12V adapter.

    I suspect the reason for placing the RK3399 on the “wrong side” is that the ethernet ports are very high and leave a big hole behind, that can easily fit a heat sink. I still prefer to have the heat sink at the bottom for compute devices (like my Neo4 and M4). But when you need to place the board into a tiny plastic box, there’s possibly less room for a big heat sink at the bottom than at the top. However with the chip at the bottom, it’s possible to use a metal enclosure to serve as a huge heat sink.

    1. Very interesting. I’ve long been looking for the “perfect red team drop box”, and this is so close!

      Unanswered questions so far: from the RK3399 datasheet, it appears that the chip supports up to 4 USB2.0 ports. 2 are used in the USB3.0 connectors, one is available on a header. Is the fourth wired up to the USB-C port, to act as a USB device? If it is, that would be amazing!

      WiFi can be added with a nano-dongle (or bigger if size is not a constraint). It will be interesting to see just how much power it really demands, with no external accessories, doing tasks such as packet forwarding, etc.

      Would be really funny to use this as an embedded password cracking box, with the OpenCL capability.

      1. According to the schematic from the wiki, sadly the USB-C is power only and the remaining USB2.0 (host only) is not connected at all.
        Only the USB3.0 of the RK3399 are capable of OTG.

        Unfortunately, there is no wifi or EMMC.

        1. Sadly, that’s something really annoying with the vast majority of headless SBCs like this, there’s no access to a console once the box is closed. If you lose the IP address, you need to have a screwdriver. The only exception I know to this is the clearfog, which provides a USB console (and some of the SBCs which expose OTG can use usb_gadget to expose a dummy console, which is not as powerful but better than nothing). We really need to see progress in this area, I don’t count the number of times I had to write a known working IP address on a sticker placed on the device 🙁

          1. Actually it’s probably among Marvell’s design rules to always provide an external access to the console, as even the shevaplug/guruplug had a small connector with the TTL signals, and the mirabox featured a mini-USB port already. You have it on ESPRESSObin, MACCHIATObin, clearfog, etc. This seems essential to me. And I never fear hacking on my mcbin thanks to this.

      1. I think the question was likely: “Why use a Gigabit PCIe controller, and not a 2.5 GbE PCIe controller?”

          1. Isn’t the reason rather obvious? For the type of application (router/firewall) a 2.5GbE port would always be bottlenecked by the other 1GbE port. Increasing BOM costs for no reason.

            And adding more than one additional PCIe connected NIC would require either a PCIe switch or special NIC controllers like those for example. Both would end up with higher BOM costs and consumption.

          2. I too looked for dual-port NIC controllers and still couldn’t find any supporting 2.5G.

  2. I run my home router on the R2S. Ubuntu and the other distributions have issues with the interface drivers (keeps freezing on reboot for me) so I’ve just been using their friendlyelec port but its a fabulous little thing for home routers. I wrote a short HowItWentForMe on reddit.

  3. Yet another RK3399 board? Any update on when will Rockchip release its next SOC, the RK3588? Then we might actually see some interesting new SBCs, other than raspberry pi.

    1. In short, nothing in common with this one ? The challenge this one addresses is to have two gigabit ports on the small board. Remove that constraint and you have plenty of other choices.

    1. I thought the same but also I thought pfsense doesnt work well, or at all, on non Intel SoCs and NICs.
      I would LOVE IT if I was wrong about this.

  4. Previous board R2S has a serious overheating problem. And it’s the only board on rk3328 with such problem. You get 60C on idle, it’s almost unusable without metal case and cooler.
    RK3399 is hotter than 3328 so R4S will start to throttle few seconds after boot.
    Stay away.

      1. Agreed, all of my 5 Neo4 and the M4 have been running fine and cool since I assembled them. Not even a single crash or hang despite torturing them from time to time with distributed builds. Their uptime dates from my last UPS death 4 months ago 🙂

    1. As I mentioned, I suspect they target plastic enclosures and want to make them thinner. However, some plastics have reasonably good thermal conductivity, and I still think that having a large flat metal plate glued to the bottom of the enclosure will spread heat better than an inner heat sink with little to no air flow.

  5. Finally, PCIe instead USB for the second Ethernet interface! True, having the SoC on the other side of the board would have been better, but that’s not a deal breaker for me. Hopefully it will be available before end of the year.

  6. I’d probably buy this as a OpenWRT router if it’s able to shape a gigabit connection. I have an R2S currently which only manages about ~700mbps with SQM enabled. For now, virtualised x86 router on Hyper-V…

Leave a Reply

Your email address will not be published.

Advertisement
Advertisement