How to Identify a Rockchip SoC (from Linux, U-Boot, USB or the Chip Marking)

Whether you are reverse-engineering a device or confirming a supplier's claim, here are the fastest ways to identify the SoC.

1. From a running Linux system

cat /proc/device-tree/compatible | tr '\0' '\n'
# radxa,rock-5b
# rockchip,rk3588

cat /proc/device-tree/model
# Radxa ROCK 5B

The last compatible entry is the SoC. /proc/cpuinfo helps confirm the core mix: CPU part 0xd0b is Cortex-A76, 0xd05 is Cortex-A55, 0xd08 is Cortex-A72, 0xd03 is Cortex-A53.

2. From Android

adb shell getprop ro.board.platform      # e.g. rk3588
adb shell getprop ro.product.board

3. From the serial boot log

The DDR init and U-Boot banners usually name the SoC and the DDR configuration in the first second of output (debug UART, usually 1,500,000 baud).

4. From USB in MaskROM mode

In MaskROM the device enumerates as vendor 2207. The product ID identifies the family, e.g. 350b for RK3588/RK3588S, 350a for RK3568/RK3566 and 330c for RK3399.

5. From the package marking

The SoC top marking shows the part number (e.g. RK3588, RK3588S, RK3568J). A trailing J or K usually indicates an industrial or extended-temperature grade. For RK3588 vs RK3588S, remember the S variant has a different package and fewer high-speed interfaces. See the RK3588S page.