Rockchip Rockit Runtime Library Developer Guide

Based on the supplied Rockchip Chinese and English V2.28.0 documents (2025-04-27), retaining technical chapters 3-13. Chinese technical content supplies additions missing from English, with discrepancies identified. This is an ArmSoM platform reference: check the actual board, SoC, SDK/BSP, kernel and peripherals individually. It does not establish support for every ArmSoM board. No commands or hardware tests were executed.

3. Framework

In order to facilitate Rockit porting, a new runtime libraries has been developed in the kernel. Hereinafter referred to as RRT. The block diagram of RRT in the kernel is as follows:

.
├── isp.ko   ---- isp module, corresponding to the /dev/mpi/rkisp-vir0 node
├── valloc.ko  --- buffer manager, corresponding to the /dev/mpi/valloc node
├── venc.ko    --- Encoder module, corresponding to the /dev/mpi/venc
├── vmpi.ko    --- media framework, corresponding to the /dev/mpi/vmpi
├── vpss.ko    --- vpss module, corresponding to the /dev/mpi/vpss
├── vrga.ko    --- rga module, corresponding to the /dev/mpi/vrga
├── vrgn.ko    --- rgn module, corresponding to the /dev/mpi/vrgn
├── vsys.ko    --- system module, corresponding to the /dev/mpi/vsys
└── vvi.ko     --- vi module, corresponding to the /dev/mpi/vvi

Before using rockit interface, the above ko need to be loaded, and the loading way is as follows (note: all the above ko have been merged into one ko):

insmod rockit.ko

Use the following command to check whether the loading is successful

# lsmod
Module                  Size  Used by    Tainted: G
rknpu                  21535  1
rockit                 90530 14
mpp_vcodec            350020  4 rockit
rga3                   76968  3 rockit
sc4336                  8940  2
phy_rockchip_csi2_dphy     7657  0
phy_rockchip_csi2_dphy_hw     7644  0
video_rkisp           138585  3 rockit,[permanent]
video_rkcif           107889  4
rk_dvbm                 5813  2 mpp_vcodec,video_rkisp

After loading successfully, you can run related programs that depend on rockit.so.

3.1 Parameters Supported by KO

3.1.1 mcu_fw_path

The path of MCU wrapping firmware, it is empty by default, does not load MCU firmware.

insmod rockit.ko mcu_fw_path=/oem/usr/ko/hpmcu_wrap.bin

3.1.2 mcu_fw_addr

The address of the MCU wrapping firmware, it is 0xff6ff000(rv1106)/0x210f6000(rv1103b) by default.

insmod rockit.ko mcu_fw_addr=0xff6ff000

3.1.3 isp_max_h

It is the height of the ISP front-end input. If VICAP has configured the cropping function, it should be configured the width after cropping. If the secondary parameter is configured incorrectly, cat /dev/mpi/vlog will prompt for the correct value.

mpi_log_err("isp input height config err, config h= %d, real h = %d", isp_max_h, isp_h);

insmod rockit.ko isp_max_h=1920

3.1.4 isp_max_w

Reserved

3.1.5 en_mcu

Whether to enable the MCU driver. It is enabled(rv1106)/disabled(rv1103b) by default. The MCU driver will not be loaded after it is disabled.

insmod rockit.ko en_mcu=0

3.1.6 rk_dma_heap_base

The first address of the MMZ released by RK_MPI_SYS_RelasePhyMemory needs to be 4K aligned and larger than the starting address of MMZ. The calculation method of the MMZ starting address is: total physical memory - MMZ size.

insmod rockit.ko rk_dma_heap_base=0x40000

3.1.7 rk_dma_heap_size

The size of the MMZ released by RK_MPI_SYS_RelasePhyMemory needs to be less than or equal to the size of the MMZ.

insmod rockit.ko rk_dma_heap_size=0x40000

4. Cross-platform Porting

The RRT has been enhanced with the addition of OSAL (Operating System Abstraction Layer) and rewritten based on OSAL, enabling it to run not only in the Linux kernel mode but also in the Linux user mode and on RTOS (Real-Time Operating Systems). Currently, there are two instances of the RRT in RV1103B/RV1126B, one running in user mode and the other in kernel mode. To view /dev/mpi/xxx related nodes on LINUX user mode and RTOS, the command dumpsys needs to be prefixed to the original command.

dumpsys cat /dev/mpi/valloc
dumpsys cat /dev/mpi/vsys
dumpsys cat /dev/mpi/vlog
dumpsys cat /dev/mpi/vrgn

5. Cross - platform Communication

Multiple RRTs may run on a single SOC. To reduce the communication cost for module developers, RRT has achieved cross - platform interoperability. Specifically, the VALLOC module is used to manage the reference count of cross - platform BUFFERs, and the VSYS module is used to implement cross - platform binding and the transfer of BUFFERs. Therefore, there is a prerequisite for cross - platform communication: the RRTs on each platform can share BUFFERs through physical memory. The following table shows the RRTs supported by each SOC and the modules included in each RRT.

6. VALLOC

The memory allocator of the media framework, which is responsible for allocating and managing the memory required by the media framework. You can use the following command to check the current memory status:

cat /dev/mpi/valloc

Detailed Information:

7. VLOG

LOG manager of media framework.

7.1 Kernel LOG

cat /dev/mpi/vlog

7.2 How to Set the LOG Output Level of the Module

The command echo module=level > /tmp/rt_log_level is used to change the LOG output level of the module, and this command affects rockit so and ko at the same time. module = all cmpi mb sys vdec venc rgn vpss vgs tde avs wbc vo vi ai ao aenc adec level=0,1,2,3,4,5,6; 2 is ERR (red), 3 WRN (yellow), 4 INF (green).

echo module=level > /tmp/rt_log_level

7.3 Set the Output Path and Size of SO LOG

echo rt_log_path=/tmp/rockit.log > /tmp/rt_log_level

echo rt_log_size=1024000 > /tmp/rt_log_level

7.4 Clear LOG

echo 0 > /dev/mpi/vlog

8. VSYS

The manager for media relationship binding, you can check the current binding relationship and frame rate information through the following command:

cat /dev/mpi/vsys

9. VENC

Encoding parameters, can be obtained by the following command:

cat /proc/vcodec/enc/venc_info

venc thread status

venc chn running status

venc chn attr 1

venc chn attr 2

ring buf status

hw status

hw param

fine tunning param

venc roi attr

hw session infos

bitstream buffer addr

h264e chn attr

Syntax INFO1

Syntax INFO2

h265e chn attr

Syntax INFO1

Syntax INFO2

Trans Info

jpege chn attr

RC base param1

RC base param2

RC run comm param1

RC run comm param2

RC gop mode attr

RC run vbr common param

RC run cbr param

RC run avbr param

RC HierarchicalQp INFO

RC debreath_effect info

RC run CBR/VBR info1

mpp_packet pool

mpp_buffer pool

mpp_frame pool

10. Mapping relationship between venc_info and rockit API

venc_info is the encoder configuration parameters printed by the kernel. currently only RV1103B/RV1106B and RV1103/RV1106 are supported.This chapter primarily focuses on key configurations, emphasizing subjective effects and objective compression- related settings.

11. IVS

Intelligent video surveillance parameters can be accessed via the following command:

cat /proc/vcodec/ivs/ivs_info

ivs channel attr

ivs common cfg

ivs md cfg

ivs od cfg

12. VRGN

The RGN manager of the media framework. Use the following command to see the current RGN information:

cat /dev/mpi/vrgn

13. VRGA

The RGA driver manager in Rockit. You can use the following command to check the current status of the RGA NODE:

cat /dev/mpi/vrga

Source discrepancies and verification notes

• Both sources state V2.28.0 and 2025-04-27. Chinese adds memtype and nkid; both fields are included in every language. Page count alone does not establish freshness.
• VSYS table: Chinese says the size is the frame rate, n retains n frames and 0 drops frames. English says 0 retains and 1 drops. The body uses the Chinese baseline; this contradiction must be checked against the SDK.
• isp_max_h is defined as input height, but both sources say “width after cropping”. Check the SDK implementation and the original diagnostic rather than silently changing the dimension.
• The RV1126B kernel module list spells VALLC; cenalbe, SCALL and RK_MPI_SYS_RelasePhyMemory also retain source spellings. Chinese last_runing, runing and heigth correspond to English last_running, running and height; both spellings are shown at the relevant fields.
• Both API tables map qp_dlt_row_i to u32RowQpDelta and qp_dlt_row to u32RowIQpDelta. Their apparent I/P meaning may be inconsistent; the mappings have not been swapped.
• Chinese has separate mpp_packet pool and mpp_buffer pool tables; English calls both mpp_buffer pool. Chinese captions are used here; packet, buffer and frame tables are all retained.
• English adds “8 groups in total” for VRGN h x y; this is retained in every language. English calls wcnt a frame rate while Chinese specifies a frame count; Chinese is used. For min_size, Chinese specifies minimum free space for allocating one frame while English says latest; the Chinese meaning is used.
• English Warp is interpreted as wrapping according to Chinese; identifiers remain unchanged. The Chinese details on ROI macroblocks, mean-compensated SAD, very-low-bitrate static-scene operation, trailing removal and noise jitter/crawling are also retained.