The RI600PX was developed based on the RI600V4, which conforms to the latest version of µITRON4.0 Specification and with additional memory protection function of the µITRON 4.0 protection extension. Almost all service calls in it except Rendezvous are supported.

In addition, its affinity for the IDE CS+ and the configurator which automatically generates startup files will help you greatly reduce development time and get to market faster.

Note: RI600PX is not generally promoted to U.S. and European customers. Customers in U.S. and Europe who are interested in RI600PX are requested to contact our regional marketing departments for details.

  • Only the memory object protect function of µITRON 4.0 Specification for Protect Function Extension is supported, and the kernel object protect function is not supported.
  • TRON, ITRON, and μITRON do not refer to any specific product or products.
  • The activities of TRON Association have been handed over to TRON Forum.


Support has been added to the RXv3 architecture, a new CPU core of the RX family.

Learn More (Tool News) >>

Release Information


Latest Ver.: V1.03.00

Released: Nov 27, 2018

Details of upgrade (See Tool News)

Operating Environment

Agreement Details

 User's Manual( Coding | All )

CS+ interface plug-ins (Real-time OS Common plug-in)

Latest Ver.: V3.03.00

Released: Jul 1, 2016

CS+ interface plug-ins (Plug-in for RI600PX)

Latest Ver.: V3.00.01

Released: Nov 27, 2018

Integrated Tools

Compiler :CC-RX
Integrated development environment :CS+



  • Compliant with µITRON4.0 Specification
    The RI600PX was developed based on the RI600V4, which conforms to the latest version of µITRON4.0 Specification and with additional memory protection function of the µITRON 4.0 protection extension. Therefore, the knowledge acquired from µITRON specification-related various publications or seminars, etc. can be made use of directly.In addition, the application programs developed using other µITRON-compliant real-time OS's can be ported to the RI600PX relatively easily.
  • Increased processing speed
    The memory protection function enables high-speed processing with minimum effect on the system since it is realized by controlling part MPU (Memory Protection Unit) of RX600 Series and RX200 Series.
  • ROM-based implementation
    Since the system is a real-time/multi-tasking OS assumed to be used embedded in the execution environment, it was designed to be compact and ready for ROM-based implementations. Also, because the system can be configured linking only the service calls used in the system by the user (rather than all the service calls provided by the RI600PX), a real-time/multi-tasking OS can be configured which is compact and optimized for the user's needs.
  • Interface with CS+, the Renesas Electronics Integrated Development Environment
    The RI600PX OS interfaces with CS+ to support the following functions:
    • Auto-settings for options required in OS build
    • Displays state of OS control object for tasks, semaphore, etc. (Resource Information)

  • Sample Projects (CS+ edition) Provided for FIT
    Sample projects (CS+ edition) for the use of Firmware Integration Technology (FIT) with the RI600PX real-time operating systems (Real-time OS) for the RX family are supplied.
    Download the sample project for FIT from Downloads Tab.


Memory Protection

  • High-reliability system
    To reduce a possibility of being unable to detect program glitches when debugging the program and causing a trouble in the market after the system has been shipped from the factory, this OS assures the system of high reliability.If memory data destruction occurs especially in a memory area in which the OS, etc. are stored, the system may produce a dangerous condition by, for example, operating erratically. However, since this OS is free of memory data corruptions, the system can continue operating normally, and is therefore assured of high system reliability
  • Debug assistance
    In systems without memory protection, a corruption of memory content by an illegal pointer behavior, etc. generally is not noticed until it actually comes to the surface as a trouble symptom. The cause of a bug can only be identified by analyzing emulator's trace data, which requires a large amount of time. The RI600PX can detect a bug when an illegal memory access is committed, enabling the debugging efficiency to be greatly increased.


The memory protection which supports RI600PX is described below.

  • Detection of illegal access by tasks.
    Tasks belong to either of domain. Furthermore, a part of address space is allocated as some memory object. A domain can be set access permissions (read, write and execute) for each memory object. The Access Exception Handler will be called if a task accesses the area that has not been permitted. In addition, handlers can access all address space.
  • Protection of stack for task.
    Task cannot access the stack for another task. The Access Exception Handler will be called if a task accesses a stack for another task.
  • Detection of illegal access by the kernel.
    Because of the kernel as well as a handler can access to all address space. Therefore, if an invalid pointer parameter is specified to a service call, the kernel commands itself an illegal access. To avoid such a consequence, the kernel inspects whether the task that invoked a service call can access to the space referred to by the pointer area. When it detects an illegal access, the service call returns an error.



The RI600PX kernel consists of the following modules. Each module is provided by functions (service calls) .

  • Scheduler
    Manages execution sequence of multiple tasks based on their priority levels.
  • Task management
    Manages task status such as RUNNING, READY, WAITING or SUSPENDED.
  • Task-dependent synchronization
    Changes task status from other task, and synchronizes tasks.
  • Interrupt management function
    Makes a return from the interrupt handler.
  • Time management
    Sets system timer used by RI600PX kernel and starts user-defined alarm handler and cyclic handler. When using the time management function, it is necessary to specify the timer template file corresponding to the target device in the system configuration file.
  • System configuration management
    Reports information such as version number of RI600PX kernel.
  • Synchronization/communication
    Carries out synchronization and communication between tasks. The following function modules are available:
    1. Event flag
      Tasks are synchronized by the status of flags managed by the kernel.
    2. Semaphore
      Tasks are synchronized by the semaphore counter value managed by the kernel.
    3. Mail box
      Tasks are synchronized by sending or receiving a message.
    4. Data queue

Tasks are synchronized by communicating 4-byte data.

  • Extended Synchronization/Communication
    Carries out synchronization and communication between tasks. The following function modules are available:
    1. Message buffer
      Makes use of variable-length data communication to synchronize tasks.
    2. Mutex
      Makes use of priority ceiling protocol for avoiding priority inversion to synchronize tasks.


  • Memory pool management
    Dynamically allocates/frees memory area used by tasks. Enables efficient use of memory.
  • Task exception handling function
    Controls execution of task exceptions by, for example, defining or activating a task exception.
  • Cyclic handler function 
    Controls the execution of a handler activated periodically.
  • Alarm handler function
    Controls the execution of a handler activated at the specified relative-time.
  • Memory protection function
    The following functions are available:
    1. Detection of illegal access by tasks
    2. Protection of stack for task.
    3. Detection of illegal access by the kernel



Target device RX700 Series, RX600 series and RX200 Series with MPU (Memory Protection Unit)
Maximum number of tasks 255
Number of priority levels 255
Service call number 190
(Time takes for a target task to be executed
after the wup_tas is issued.)
3.2 microseconds (RX630, 100MHz)
Kernel code size From 6.3K bytes to 33.5K bytes
Kernel RAM usage per task data : 20 bytes
stack : 44 bytes




Provided items Explanation Note
Kernel source program Source files for the kernel Provided only with mass- production licenses which include source code.
Kernel library Kernel library for system building -
Standard header files ITRON specification common definition files
Kernel specification definition files
Other definition files
Header files are provided in C language.
Command line configurator Outputs all types of definition files from the cfg file that describes the structure parameters in text. -
Sample program A simple program using ITRON. -
CS+ interface plug-ins
- Real-time OS Common plug-in
- Plug-in for RI600PX
Function for easy kernel embedding
Function for referencing the OS state during debug
Manual User's manual -



Development Tools Support

Title Description
My Renesas Create a My Renesas account to use our tool download services,
receive e-newsletter/update notifications, and take advantage of our other services.
e-learning Information for studying and learning about microcontrollers and microprocessors.
FAQ Frequently asked questions and useful hints for development.
Forum A forum and community site to share technical information,
questions and opinions with others who use Renesas MCU's.
Tool News Tool release information and other important information.
Operating Environment Information on system requirements and operating environment for the latest
version of tools.
Info on Discontinued Products A list of Renesas software and tools that have been discontinued and
are no longer being offered for new projects.