The ITRON project is the first of several sub-architectures of the TRON project.

Originally undertaken in 1984, ITRON is a Japanese open standard for a real-time operating system (RTOS) initiated under the guidance of Ken Sakamura. This project aims to standardize the RTOS and related specifications for embedded systems, particularly small-scale embedded systems. The ITRON RTOS is targeted for consumer electronic devices, such as mobile phones and fax machines. Various vendors sell their own implementations of the RTOS.

Details

ITRON, and µITRON (sometimes also spelled uITRON or microITRON) are the name of RTOS specifications coming out of ITRON projects. 'µ' means that the particular specification is meant for the smaller 8-bit or 16-bit CPU targets. Specifications are available for free. Commercial implementations are available, and offered under many different licenses. On 10 November 2017, the Institute of Electrical and Electronics Engineers acquired ownership of the 16- and 32- bit uITRON from TRON Forum.[1]

A few sample sources exist, and there are many commercial source offerings, too.

Examples of open source RTOSes incorporating an API based on µITRON specification are eCos and RTEMS.

ITRON specification is meant for hard real-time embedded RTOS.

It is very popular in the embedded market, as there are many applications for it, i.e., devices with the OS embedded inside.

For example, there is an ACM Queue interview with Jim Ready, founder of MontaVista (realtime linux company), "Interview with Jim Reddy", April 2003, ACM Queue.[2] He says in the interview, "The single, most successful RTOS in Japan historically is µITRON. This is an indigenous open specification led by Dr. Ken Sakamura of the University of Tokyo. It is an industry standard there." Many Japanese digital cameras, for example, have use ITRON specification OS. Toyota automobile has used ITRON specification OS for engine control.

Supported CPUs are numerous. ARM, MIPS, x86, SH FR-V and many others including CPUs supported by open source RTOS eCos and RTEMS, both of which include the support for µITRON compatible APIs.

ITRON's popularity comes from many factors, but one factor is the notion of "loose standardization": the API specification is at the source level, and does not specify binary API compatibility. This makes it possible for implementers to make use of features of the particular CPU model to which the implementation is targeted. The developer even has the freedom of choosing to pass the parameters using a consolidated packet, or separate parameters to API (system call, library call, etc.). Such freedom is important to make the best use of not so powerful 8-bit or 16-bit CPUs. This makes keeping the binary compatibility among different implementations impossible. This led to the development of T-Kernel in the 2000s in order to promote binary compatibility for middleware distribution.

ITRON specification promotion was done by the various companies which sell the commercial implementations. There was also an NPO TRON Association[3] that promoted the specification by publishing it as well as other TRON specification OSes. But since the first quarter of 2010, it has become part of T-Engine Forum,[4] another non-profit organization that promotes other operating system such as the next generation RTOS, T-Kernel.

T-Kernel is the name of the specification and at the same time refers to the single implementation based on the authorized source code available from T-Engine Forum for free under T-License. So T-Kernel doesn't suffer from the binary API compatibility.

JTRON (Java TRON) is a sub-project of ITRON to allow it to use the Java platform.

See also

References

  1. ↑ "IEEE Standards Association (IEEE-SA) and TRON Forum Sign Agreement to Advance IoT Development and Interoperability". www.tron.org. Retrieved 2019-10-02.
  2. ↑ "Interview - ACM Queue". queue.acm.org.
  3. ↑ "TRON Forum". www.tron.org.
  4. ↑ "The name of T-Engine Forum was changed to TRON Forum". www.t-engine.org.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.