I-51-01E-006

ITRON Newsletter No.6
ITRON Technical Committee, TRON Association

Katsuta Building 5F, 3-39, Mita 1-chome, Minato-ku, Tokyo 108, JAPANTEL: (03) 3454-3191
FAX: (03) 3454-3224
ret rst is also supported, for a total of 52 system

The ITRON Registration System forcalls.

Products and Applications

Maximum number of system resources
Tasks:
511
Task priorities: 32 levels
Flags:
127
Semaphores:
127
Mailboxes:
127
Memory pools:
127
Cyclic handlers: 127
Alarm handlers: 127

The products listed in another page were newly registered in the period from November 1, 1993 throughJanuary 1, 1994. Details of the product registration
system, and an updated list of registered products,
can be obtained by contacting the TRON Association. Previously registered products are also listed
in ITRON Newsletter Nos.1 to 3, 5.
ITRON-related Publications

Listed in another page are the publications preparedand issued by the ITRON Technical Committee asof December 1, 1993. The ITRON-ITRON Standard Handbook is a one-volume compilation of theITRON (Ver 2.0) and ITRON2 speci cations. Eachof the publications can be obtained directly from thesources indicated.
The latest version of ITRON3.0 is now Ver
3.01.00. Changes made since the ITRON3.0 Standard Handbook was released (Ver 3.00.00) are notedin Newsletter No.5.

C language is used for system de nition, so when
the system is activated an external switch or othermeans is used to read and convert the system de nitions.
A C language system call interface library is provided.
System call parameter checking can be omitted, inorder to improve real-time performance.
For system development a C compiler and assembler are required in addition to MORTOS/n68.

Development procedure

1. Creation of a source le (C and/or assembly language)

New Products

The two products recently registered in the ITRONRegistration System for Products and Applications
are introduced here.

2. Creation of a system de nition le (C language)
3. Compiling

MORTOS/n68

4. Linkage with the MORTOS kernel library

MORTOS/n68 is a ITRON-speci cation OS for use
in embedded systems, supporting the MC68000 processor.

5. Debugging
6. ROM encapsulation

System call support

MORTOS/n98

System calls through level 4 are supported except
for frsm tsk and get blk. The level 5 system call

MORTOS/n98 is a ITRON-speci cation OS for the8086 processor family. It runs on the PC-9800 Seriesof personal computers (NEC) or can be used in embedded systems.

y This newsletter is reprinted from TRONWARE vol.25 andTRON PROJECT BIMONTHLY No.30.

1I-51-01E-006
Newly Registered Products (Nov. 1, 1993 { Jan. 1, 1993)

Speci cation
ITRON2.0

Product Name
MORTOS/n68
MORTOS/n98

Supported Processor
MC68000
8086 family

Company
MORSON JAPANMORSON JAPANITRON-related Publications

NameTypePricePublisher
ISBN No.
ITRON-ITRON Standard Handbook Speci cation (Japanese)
4,800Yen Personal Media Co. 4-89362-079-7
ITRON3.0 Standard Handbook
Speci cation (Japanese)
4,000Yen Personal Media Co. 4-89362-106-8
ITRON/FILE Standard Handbook
Speci cation (Japanese)
3,000Yen Personal Media Co. 4-89362-092-4
ITRON Standard Guidebook '92-'93
Textbook (Japanese)
3,500Yen Personal Media Co. 4-89362-197-6
ITRON Speci cation Ver 2.01.00.00
Speci cation (English) 12,000Yen TRON Association{
ITRON2 Speci cation Ver 2.02.00.10
Speci cation (English) 15,000Yen TRON Association{NOTES:- Prices do not include consumption tax.
- TRON Association members may purchase Association publications at a special discount price.
- English-language speci cations are also distributed free of charge via the Internet. The method for downloading isexplained in Newsletter No.2.

4. Linkage with the MORTOS kernel library

System call support
A total of 25 system calls are supported, fortask management (5), task-dependent synchronization (7), synchronization and communication(9), interrupt management (1), and time management/timer handler functions (3). Support forother system calls is planned. These system calls
are used from a C language interface.

5. Debugging
6. ROM encapsulation (not required when used ona personal computer)
MORTOS versions for other CPUs are also being
planned. System developers interested in such an OS
are asked to contact MORSON JAPAN.

Maximum number of system resources
Tasks:
511
Task priorities: 32 levels
Flags:
127
Semaphores:
127
Mailboxes:
127
Cyclic handlers: 127

Recent Works on ITRON

The monthly magazine Interface in its December 1993
issue carries a special feature article on ITRON, entitled, \A real-time OS introduction and ITRON implementation." It starts by describing what a realtime OS is, then explains how to make and use aITRON-speci cation OS. A simple OS, for which asource code list is provided, is used in the explanation.
This feature should be of interest to anyone desiring
an introduction to the world of real-time operating
systems and ITRON.
The feature does, however, contain a number of errors or statements that might be misunderstood, socare is required when reading it.

C language is used for system de nition, so when
the system is activated an external switch or othermeans is used to read and convert the system de nitions.
A system call C language interface library is provided.
System call parameter checking can be omitted, inorder to improve real-time performance.
For system development a C compiler is necessaryin addition to MORTOS/n98.

1. Section 3 states that with Hitachi's ITRONspeci cation kernel only one task of a given priority level can be created. Although a few of
Hitachi's ITRON implementations adopt sucha speci cation for the sake of improving performance and saving memory, most of their
ITRON-speci cation OSs, like those of otherrms, do not have this restriction.

Development procedure

1. Creation of a source le (C language)
2. Creation of a system de nition le (C language)
3. Compiling2

I-51-01E-006
2. Section 3 also states that the only real-time OSdebugger that can be used along with an ICE isthat of Yokogawa-Hewlett-Packard Ltd. In fact,
however, a number of other rms have releasedsuch debuggers for a ITRON-speci cation kernel.
3. Section 4 incorrectly states that when pget blk
and pget blf are executed from the taskindependent part, the acquired memory blockmust be returned before the task-independentpart is terminated. However, it is also possible fora memory block acquired in the task-independent
part to be returned in the task part, which is themore usual practice.

3