DEV Community

Cover image for Rockchip's confusing SoC lineup: Which one actually fits your project?
Leonard Liao
Leonard Liao

Posted on

Rockchip's confusing SoC lineup: Which one actually fits your project?

I've been digging through Rockchip's processor family lately, and honestly? It's a mess. Not in a bad way - more like a "too many options, and they all look similar on paper" kind of way.

If you're building something with a Rockchip chip, you've probably stared at the specs for RK3588, RK3588S, RK3568, and RK3566, trying to figure out which one is the right choice. I've been there. And after spending way too many hours comparing datasheets, I think I've finally got a handle on it.

Let me walk you through what I found.

The flagship family: RK3588 vs RK3588S

The RK3588 is Rockchip's big dog. 8 cores, 6 TOPS NPU, 8K video, PCIe 3.0 x4 - it's the chip that powers most high-end SBCs like the Orange Pi 5 and KiwiPi 5B. It's fast, it's capable, and it costs accordingly.

Then there's the RK3588S. Same CPU, same GPU, same NPU. But they cut corners to make it cheaper. Less PCIe lanes, fewer video outputs, and lower maximum memory. The RK3588 vs RK3588S comparison shows the full picture, but the short version is: if you need maximum performance and expansion, get the RK3588. If you're building something power-sensitive or compact, the RK3588S might be the smarter move.

I've seen both chips in action. For most people, the differences won't matter that much. But if you're pushing the hardware hard - like running multiple AI models or driving several displays - the RK3588's extra PCIe lanes and higher memory bandwidth make a real difference.

The mid-range siblings: RK3568 vs RK3566

The RK3568 and RK3566 are Rockchip's mid-range workhorses. Both are quad-core Cortex-A55 chips with Mali-G52 graphics and about 1 TOPS of NPU performance. The RK3568 has a higher clock speed, more I/O options (including PCIe and SATA), and stronger 4K multimedia support.

The practical comparison between the RK3568 and RK3568 breaks down the differences, but here's my take: if you're building a tablet, e-reader, or any battery-powered device, the RK3566 is probably the better choice. It's cheaper and uses less power. If you need 4K video, multiple displays, or industrial I/O, the RK3568 is worth the extra cost.

What this means for your project

Here's the thing about Rockchip's lineup - there's no single "best" chip. It all depends on what you're building:

Rockchip Soc Lineup

The unexpected trade-offs

I learned a few things the hard way while testing these chips:

First, the software ecosystem varies between models. The RK3588 has the best community support because it's been around longer and is in more boards. The RK3566 and RK3568 are well-supported, but you'll find fewer tutorials and community images.

Second, thermal performance is tricky. The RK3588 runs hot. Really hot. Without active cooling, it'll throttle quickly under sustained load. The RK3588S is slightly better, but still needs a heatsink. The RK3566 and RK3568 are much more forgiving - they can run fanless in most cases.

Third, cost differences are bigger than you'd expect. The RK3588 boards are often double the price of RK3568 boards, and the RK3566 is even cheaper. If you don't actually need the extra power, it's easy to overspend.

My advice

Stop chasing specs. Start with what you actually need.

If you're building a simple project - a media player, a control panel, a basic edge device - the RK3566 or RK3568 will do just fine. You don't need a flagship chip for a kiosk display or a home automation hub.

If you're doing serious AI work, running multiple cameras, or driving 8K displays, the RK3588 is worth the investment. But make sure you have the cooling solution to match.

And if you're somewhere in between - needing decent performance but not full flagship - the RK3588S is a solid compromise. Most of the performance, less of the cost and power draw.

Rockchip's lineup is confusing, but it doesn't have to be. Figure out your requirements first, then pick the chip that fits. That's the only way to avoid paying for performance you'll never use - or ending up with a chip that can't handle what you need.

Top comments (0)