yahboom
HomeLearn
Solution
Blog
Online Store
About Us
EN/中文
RDK S100(P) Board📖
0. RDK S100(P) Developer Kit
  • 1. RDK S100(P) Official Tutorial
1. Introduction to RDK S100(P) Development Board
  • 1.1 Introduction to the RDK S100(P) Development Board
  • 1.2 Install Operating System
  • 1.3 Interface Descriptions
  • 1.4 Accessory installation
  • 1.5 Camera Expansion Board
  • 1.6 MCU Port Expansion Board
  • 1.7 Precautions for using 15.6-inch screens
2. Basic Settings Course
  • 2.1 Network Configuration
  • 2.2 Remote Login
  • 2.3 System Update
  • 2.4 Boot Auto-Start Configuration
  • 2.5 RDK Exclusive Command Usage
  • 2.6 Linux Command Usage
  • 2.7 Example of GPIO read and write operations
  • 2.8 Using USB Camera
  • 2.9 Using MIPI Camera
  • 2.10 SSD mounting
  • 2.11 Binocular camera depth algorithm
3. TogetheROS.Bot Vision Applications
  • 1. About TogetheROS. Bot
  • 2. System Installation
  • 3. Object Detection(YOLO)
  • 4. Image Classification(mobilenetv2)
  • 5. Image Segmentation(mobilenet_unet)
  • 6. Perception Algorithm(BEV)
  • 7. Human Detection and Tracking (Ultralytics YOLO Pose)
4.Offline AI model course
Offline large model (Text Interaction)
  • 1. AI large model environment deployment
  • 2. Install large model dialogue platform
  • 3. Meta AI Llama 3.2 model
  • 4. Alibaba Cloud Qwen3 model
  • 5. Microsoft Phi-4 mini model
  • 6. DeepSeek - DeepSeek-R1 model
  • 7. Alibaba Cloud Qwen2.5vl Visual Multimodal Large Model
  • 8. Google Gemma3 Visual Multimodal Large Model
  • 9. Lava Visual Multimodal Large Model
  • 10. MiniCPM-V Visual Multimodal Large Model
  • 11. Multimodal visual understand application
  • 12. Multimodal text to image application
  • 13. Multimodal visual localization application
  • 14. Multimodal table scanning application
  • 15. Multimodal Autonomous Agent Applications
Offline large model (Voice Interaction)
  • 0. Voice Interaction Hardware Connection (Must Read)
  • 1. Offline speech-to-text (ASR)
  • 2. Offline Text-to-Speech (TTS)
  • 3.AI large model voice interaction
  • 4. Multimodal visual understanding voice interaction
  • 5. Multimodal Text-to-Image application
  • 6. Multimodal video analytics application
  • 7. Multimodal visual localization application
  • 8. Multimodal table scanning application
  • 9. Multimodal autonomous agent application
  • 10. AI Large Model Offline Voice Assistant
5.Online AI model course
Online large model (Text Interaction)
  • 1.OpenRouter large model API aggregation platform
  • 2.Multimodal visual understand application
  • 3.Multimodal visual localization application
  • 4.Multimodal table scanning application
  • 5.Multimodal autonomous agent application
Online large model (Voice Interaction)
  • 0.Voice interaction hardware connection (ReadMe)
  • 1.Online speech to text (ASR)
  • 2.Online text to speech (TTS)
  • 3.AI large model voice interaction
  • 4.Multimodal visual understand speech interaction
  • 5.Multimodal visual localization application
  • 6.Multimodal table scanning application
  • 7.Multimodal autonomous proxy application
  • 8.AI large model online voice assistant
6.YOLO26 tutorials
  • 01.YOLO26 environment
  • 02.CLI use
  • 03.Object detection
  • 04.Instance segmentation
  • 05.Pose estimation
  • 06.Image classification
  • 07.Oriented object detection
  • 08.Model conversion
  • 09.Dataset annotation
  • 10.Model training - conversion
  • 11.Model prediction
7.OpenClaw Advanced Development
  • 1.OpenClaw Deployment
  • 2.OpenClaw WhatsApp Plugin Application
  • 3.OpenClaw WebChat Interaction
  • 4.OpenClaw TUI Interaction
  • 5.OpenClaw Tools Introduction
  • 6.OpenClawGate Gateway User Manual
  • 7.OpenClaw Features Overview
  • 8.OpenClawClawHub Introduction (Skill Installation)
  • 9.OpenClaw Application - File Management
  • 10.OpenClaw Application - Camera
  • 11.OpenClaw Application - Browser Control
  • 12.OpenClaw Application - Script Execution
  • 13.OpenClaw Application - AI Programming (Peripheral & GPIO Control)
  • 14.OpenClaw Application - Dedicated AI Assistant
  • 15.OpenClaw Web Search Capability Configuration
8.ROS2 basic course
  • 1.Introduction to ROS2
  • 2.ROS2 install Humble
  • 3.ROS2 development environment
  • 4.ROS2 workspace
  • 5.ROS2 function package
  • 6.ROS2 node
  • 7.ROS2 topic communication
  • 8.ROS2 service communication
  • 9.ROS2 action communication
  • 10.ROS2 custom interface message
  • 11.ROS2 parameter service case
  • 12.ROS2 meta-function package
  • 13.ROS2 distributed communication
  • 14.ROS2 DDS
  • 15.ROS2 time related API
  • 16.ROS2 common command tools
  • 17.ROS2 rviz2 use
  • 18.ROS2 rqt toolbox
  • 19.ROS2 Launch startup file configuration
  • 20.ROS2 recording and playback tool
  • 21.ROS2 URDF model
  • 22.ROS2 Gazebo simulation platform
  • 23.ROS2 TF2 coordinate transformation
Download
  • Annex_File
  • Code
Download ZIP

Welcome to RDK S100(P) Board repository

2.5 RDK Exclusive Command Usage

 

RDK Exclusive Command Usage

RDK Exclusive Command Usage1. hrut_boardid2. hrut_ps3. hrut_somstatus4. rdkos_info5.hrut_socuid6.devmem

 

1. hrut_boardid

The hrut_boardid command is used to retrieve the ID of the current development board (different development boards have different IDs).

⚠️ The board ID affects hardware initialization during boot—please configure it with caution.

  • Grammar explanation

    xxxxxxxxxx
    root@ubuntu:~# hrut_boardid
    0x6A84
  • Output explanation:

    xxxxxxxxxx
    0x   6A          8             4
         ^^          ^             ^
         ||          |             |
      Chip ID   Board Power Design   Board Design Version

 

2. hrut_ps

The hrut_ps command prints process status information not supported by BusyBox's ps command, including process ID, parent process ID, priority, memory usage, virtual memory, and more.

  • Grammar explanation

    xxxxxxxxxx
    hrut_ps
  • Supported Information

    • pid: Process ID. Each process in the operating system has a unique identifier called the process ID (pid), which is used to uniquely identify and reference a process within the system.

    • ppid: Parent Process ID. This indicates the parent process that created the current process.

    • state: Process state.

      • I: Idle.
      • R: Running.
      • S: Sleeping.
      • D: Disk sleeping (uninterruptible sleep).
      • T: Stopped.
      • X: Dead.
      • Z: Zombie.
      • t: Tracing stop.
      • P: Parked.
    • prio: Priority. Represents the scheduling priority of the process, usually expressed as a numeric value. A higher number typically indicates higher priority, making the process more likely to receive CPU time slices.

    • nice: Nice value. Represents the scheduling priority as an integer. A lower nice value indicates higher priority, allowing the process to obtain CPU time more frequently.

    • rt_prio: Real-time priority. Indicates the priority of real-time processes; a lower value signifies higher real-time priority.

    • policy: Scheduling policy. Specifies the scheduling policy used for the process, typically a scheduling algorithm such as First-In-First-Out (FIFO), Round Robin (RR), etc.

    • vsize: Virtual memory size. Represents the size of the virtual memory address space accessible to the process.

    • rss: Resident Set Size (physical memory usage). Indicates the amount of physical RAM currently allocated and used by the process.

    • comm: Command name. Contains the name of the command or executable file associated with the process, used to identify the process type or purpose.

 

3. hrut_somstatus

The hrut_somstatus command retrieves temperature sensor readings, CPU/BPU operating frequencies, and BPU load.

  • Grammar explanation

    xxxxxxxxxx
    sudo hrut_somstatus
  • Common Usage

    xxxxxxxxxx
    sunrise@ubuntu:~$ sudo hrut_somstatus
    =====================1=====================
    temperature-->
            pvt_cmn_pvtc1_t1 : 38.565 (C)
            pvt_cmn_pvtc1_t2 : 40.219 (C)
            pvt_mcu_pvtc1_t1 : 37.829 (C)
            pvt_mcu_pvtc1_t2 : 38.013 (C)
            pvt_bpu_pvtc1_t1 : 38.932 (C)
    voltage-->
            FAKE     : 100.0 (mV)
            VDDQ_DDR2 : 498.0 (mV)
            VDD_MCU  : 749.0 (mV)
            VDDIO_PVT_MCU : 1794.0 (mV)
            VDDIO_TOP4_1V8 : 1794.0 (mV)
            VDDQ_DDR0 : 504.0 (mV)
            VDD2H_DDR0 : 1042.0 (mV)
            VAA_DDR0 : 1794.0 (mV)
            VDD_DDR0 : 743.0 (mV)
            VDDQ_DDR1 : 504.0 (mV)
            VDD2H_DDR1 : 1042.0 (mV)
            VAA_DDR1 : 1794.0 (mV)
            VDD_DDR1 : 743.0 (mV)
            VDDIO_SD_SDIO_T : 1788.0 (mV)
            VDD_CPU  : 776.0 (mV)
            VAA_DDR2 : 1780.0 (mV)
            VDD2H_DDR2 : 1030.0 (mV)
            VDD_DDR2 : 737.0 (mV)
            VDDIO_TOP2_1V8 : 1780.0 (mV)
            VDD_BPU  : 737.0 (mV)
            VDDIO_TOP0_1V8 : 1780.0 (mV)
            PLL_TOP0_VDDHV : 1768.0 (mV)
            VDDIO_SD_33_MCU : 3304.0 (mV)
            VDDIO_ADC_MCU : 1800.0 (mV)
            VDDIO_MCU_1V8 : 1800.0 (mV)
            PLL_MCU_VDDHV : 1800.0 (mV)
            PLL_MCU_VDDPOST : 746.0 (mV)
            PLL_MCU_VDDREF : 751.0 (mV)
            VDD_TOP  : 757.0 (mV)
            VDD_AON  : 751.0 (mV)
            VDDIO_SD_AON_CA : 1662.0 (mV)
            VDDIO_PVT_1V8 : 1800.0 (mV)
    cpu frequency-->
                      min   cur     max
            policy0: 1125000        1500000 1500000
            policy4: 1125000        1500000 1500000
    bpu status information---->
                    ratio
            bpu0:   0
    • temperature:

      • pvt_cmn_pvtc1_t1/2: CPU temperature, in degrees Celsius (°C).
      • pvt_mcu_pvtc1_t1/2: MCU temperature, in degrees Celsius (°C).
      • pvt_bpu_pvtc1_t1: BPU temperature, in degrees Celsius (°C).
    • cpu frequency:

      • min: Minimum operating frequency of the CPU.
      • cur: Current operating frequency of the CPU.
      • max: Maximum operating frequency of the CPU.
      • This information shows the frequency range (minimum, current, and maximum) for each CPU cluster.
    • bpu status information:

      • ratio: BPU load ratio during operation.
      • This information indicates the BPU load.

 

4. rdkos_info

The rdkos_info command is used to collect, in one go, software and hardware versions of the RDK system, a list of loaded drivers, installed RDK software packages, and the latest system logs, enabling users to quickly obtain the current system status information.

  • Grammar explanation

    xxxxxxxxxx
    sudo rdkos_info [options]
  • Options

    All options are optional. If run without any options, rdkos_info defaults to the concise output mode.

    • -b: Basic output mode; system logs will not be collected.
    • -s: Concise output mode (default); outputs the latest 30 lines of system logs.
    • -d: Detailed output mode; outputs the latest 300 lines of system logs.
    • -v: Display version information.
    • -h: Display help information.
  • Common Usage

    Default usage:

    xxxxxxxxxx
    sudo rdkos_info

    Partial output is shown below:

    ​x
    sunrise@ubuntu:/root$ sudo rdkos_info
    ================ RDK System Information Collection ================
    ​
    [Hardware Model]:
            D-Robotics RDK S100(P) V0P5 (Board Id = 0x6A84)
    ​
    [CPU And BPU Status]:
            =====================1=====================
            temperature-->
                    pvt_cmn_pvtc1_t1 : 38.932 (C)
                    pvt_cmn_pvtc1_t2 : 40.587 (C)
                    pvt_mcu_pvtc1_t1 : 38.013 (C)
                    pvt_mcu_pvtc1_t2 : 38.381 (C)
                    pvt_bpu_pvtc1_t1 : 39.300 (C)
            voltage-->
                    FAKE     : 100.0 (mV)
                    VDDQ_DDR2 : 504.0 (mV)
                    VDD_MCU  : 749.0 (mV)
                    VDDIO_PVT_MCU : 1794.0 (mV)
                    VDDIO_TOP4_1V8 : 1794.0 (mV)
                    VDDQ_DDR0 : 498.0 (mV)
                    VDD2H_DDR0 : 1042.0 (mV)
                    VAA_DDR0 : 1794.0 (mV)
                    VDD_DDR0 : 743.0 (mV)
                    VDDQ_DDR1 : 498.0 (mV)
                    VDD2H_DDR1 : 1052.0 (mV)
                    VAA_DDR1 : 1794.0 (mV)
                    VDD_DDR1 : 743.0 (mV)
                    VDDIO_SD_SDIO_T : 1788.0 (mV)
                    VDD_CPU  : 776.0 (mV)
                    VAA_DDR2 : 1780.0 (mV)
                    VDD2H_DDR2 : 1042.0 (mV)
                    VDD_DDR2 : 737.0 (mV)
                    VDDIO_TOP2_1V8 : 1780.0 (mV)
                    VDD_BPU  : 737.0 (mV)
                    VDDIO_TOP0_1V8 : 1780.0 (mV)
                    PLL_TOP0_VDDHV : 1768.0 (mV)
                    VDDIO_SD_33_MCU : 3304.0 (mV)
                    VDDIO_ADC_MCU : 1800.0 (mV)
                    VDDIO_MCU_1V8 : 1800.0 (mV)
                    PLL_MCU_VDDHV : 1800.0 (mV)
                    PLL_MCU_VDDPOST : 751.0 (mV)
                    PLL_MCU_VDDREF : 751.0 (mV)
                    VDD_TOP  : 757.0 (mV)
                    VDD_AON  : 751.0 (mV)
                    VDDIO_SD_AON_CA : 1662.0 (mV)
                    VDDIO_PVT_1V8 : 1800.0 (mV)
            cpu frequency-->
                              min   cur     max
                    policy0: 1125000        1500000 1500000
                    policy4: 1125000        1500000 1500000
            bpu status information---->
                            ratio
                    bpu0:   0
    ​
    [Total Memory]:         4.7Gi
    [Used Memory]:          1.6Gi
    [Free Memory]:          1.5Gi
    ​
    ​
    [RDK OS Version]:
            4.0.2-Beta
    ​
    [RDK Kernel Version]:
            Linux ubuntu 6.1.112-rt43-DR-4.0.2-2506091317-g08c4b8-g2e7d75 #80 SMP PREEMPT_RT Mon Jun  9 13:18:49 CST 2025 aarch64 aarch64 aarch64 GNU/Linux
    ​
    [RDK Miniboot Version]:
            4.0.2-20250605231718

 

5.hrut_socuid

The hrut_socuid command prints the UID (Unique Identifier) of the current SoC chip.

  • Grammar explanation

    xxxxxxxxxx
    hrut_socuid
  • Common Usage

    xxxxxxxxxx
    sunrise@ubuntu:~$ hrut_socuid
    060c0b0d3090694108255c4c00001079

 

6.devmem

devmem is a command in BusyBox. It can read from and write to hardware registers by using the mmap function to map device memory into user space via the mmap method of the /dev/mem driver, thereby enabling read/write operations on physical addresses.

  • Grammar explanation

    xxxxxxxxxx
    devmem ADDRESS [WIDTH [VALUE]]
    ​
    Read/write from physical address
    ​
          ADDRESS Address to act upon
          WIDTH   Width (8/16/...)
          VALUE   Data to be written
    • ADDRESS: The physical address on which to perform the operation. This is a required parameter specifying the address to read from or write to.
    • WIDTH: An optional parameter indicating the data width. It can be specified as 8, 16, or 32, defining the bit-width of the data to read or write. If omitted, it defaults to 32 bits.
    • VALUE: An optional parameter representing the data value to write. If WIDTH is provided, VALUE must match the specified width. If VALUE is omitted, the command performs a read operation.
  • Common Commands

    • Reading registers
    xxxxxxxxxx
    Read 32-bit: devmem 0xa600307c 32
    Read 16-bit: devmem 0xa600307c 16
    Read 8-bit:  devmem 0xa600307c 8
    • Writing registers
    Write 32-bit: devmem 0xa6003078 32 0x1000100
    Write 16-bit: devmem 0xa6003078 16 0x1234
    Write 8-bit:  devmem 0xa6003078 8 0x12
Boot Auto-Start Configuration
Linux Command Usage

COMPANY

  • About us
  • Team Style
  • Blog

LEARNING & EXPLORATION

  • Tutorials
  • Edge AI hardware
  • Educational robots
  • Embedded intelligent hardware

WHERE TO BUY

  • Yahboom Online Store
  • Amazon
  • Alibaba
  • AliExpress
  • Mercado

TECHNOLOGY SUPPORT

  • Email: support@yahboom.com

BE A DISTRIBUTOR

  • Email: sales@yahboom.com
QR Code

Copyright © 2017-2026 Yahboom. All Rights Reserved.

EN/中文