/***************************************************/ /* Release Notes for RTX51 TINY Version 2 */ /* PK51 PROFESSIONAL DEVELOPERS KIT */ /***************************************************/ This file contains

release notes and last minute changes relating to the RTX51 TINY Real Time Operating System Version 2. Information in this file, the accompanying manual, and software is Copyright (c) 2002 Keil Software and Keil Elektronik. All rights reserved. Contents ======== 1. 1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 2. 3. 4. What's New in RTX51 TINY Version 2 Code Banking Support Explicit Task Switch (Function: os_switch_task) RUN Status Flag for Tasks CPU IDLE Mode for Power-Reduction Add User Code to the 8051 CPU Hardware Timer Routine Handling for Interval Events (Function: os_reset_interval) Reduced Code/Data Size and Improved Performance Problems solved in RTX51 TINY Version 2.02 Example Programs

1.

What's New in RTX51 TINY Version 2

RTX51 TINY Version 2 has been completly restructured to gain flexiblity, accelarate performance, and reduce code/data space requirements. Also several new features are added to this popular Real-Time Kernal. The following section describes the new features in RTX51 TINY Version 2: 1.1. Code Banking Support You can now use RTX51 TINY together with code banking application. Code banking support is enabled in the file CONF_TNY.A51 with the CODE_BANKING configuration variable. As with all other code banking applications you need to configure the file L51_BANK.A51. Note: The banking configuration file L51_BANK.A51 V2.12 or higher is required. 1.2. Explicit Task Switch (Function: os_switch_task) The function os_switch_task lets a task give up the CPU and let another task execute. If the task calling os_switch_task is the only task that is ready for execution, it will resume running immediately. Function prototype: void os_switch_task (void); Program Example:

void long_job (void) _task_ 1 float f1, f2; f1 = 0; while (1) { f2 = log (f1); f1 += 0.0001; os_switch_task (); } }

// execute other tasks

1.3. READY Status Flag In addition to the signal flag, each task has also a READY status flag. A new function allows you to set the READY status flag. If the READY status flag of a tasks is set, the task will always stay in the Ready state. The os_wait function will immidiatly continue to the execute when the READY status flag is set. When a task becomes active, the status of the READY status flag is cleared and the previous status is signaled as retrun value of the os_wait and os_switch_task function. The os_wait function requires no specific argument (like K_SIG for the signal flag) to wait for the READY status flag. Compared to the os_send_signal function, the os_set_ready function executes faster. os_set_ready does not check for valid taskid arguments. Function Prototypes void os_set_ready (unsigned char taskid); void isr_set_ready (unsigned char taskid); Set the READY status flag of the task specified by taskid. The value of the READY status flag is indicated by the return value RDY_EVENT of the os_wait and os_switch_task function. When a task becomes ready, the READY statu s flag of these task is automatically cleared.

1.4. CPU IDLE Mode for Power-Reduction Many 8051 variants can be switched into an IDLE mode where the CPU is gated off the clock signal. In IDLE mode, the CPU stops instruction execution. However peripherals including the interrupt system still continue their operation. RTX51 Tiny invokes the IDLE mode when no task is in the status READY. Typcially the IDLE mode is terminated by an CPU interrupt, i.e. the RTX51 Tiny System Clock Interrupt. On most 8051 variants the IDLE mode is started by setting bit 0 (IDL) in the PCON register. However, the configuration file CONF_TNY.A51 provides the macro CPU_IDLE for the configuration of the IDLE mode activation code.

1.5. Add User Code to the 8051 CPU Hardware Timer Routine In RTX51 Tiny Version 2 it is possible to add user code for the RTX51 System Timer Interrupt routine. In this way you may use the fixed clock rate of the RTX51 System Timer Interrupt to execute own routines. The user code can be configured with macro HW_TIMER_CODE in the configuration file CONF_TNY.A51.

1.6. Handling for Interval Events (Function os_reset_interval) RTX51 Tiny maintains a software timer for each task. This software timer is used as interval timer when os_wait is called with a K_IVL event argument. The interval time specified is substracted from the software timer on the entry of the os_wait function. When two event arguments are used (signal and interval might be combined with K_SIG | K_IVL) with os_wait and the signal event occurs, the software timer migh t not be elapsed and this may result in incorrect interval times on further os_wai t calls with the K_IVL event argument. The function os_reset_interval overcomes t his problem and resets the interval time. Example: void maintask (void) _task_ 0 { os_create_task (1); while (1) { event = os_wait2 (K_SIG | K_IVL, 100); switch (event) { case TMO_EVENT: a = event; break; case SIG_EVENT: b = event; os_reset_inverval (100); // correct interval time on a signal ev ent break; } } }

2.

Reduced Code/Data Size and Improved Performance

RTX51 Tiny Version 2 is fully scalable and shows significant code size reductions when: a) Round Robin Task Switching is disabled with the setting TIMESHARING EQU 0 in the configuation file CONF_TNY.A51. b) not all RTX51 Tiny system functions are used. c) Stack Checking is disabled with the setting FREE_STACK EQU 0 in the

configuration file CONF_TNY.A51. Compared to RTX51 Tiny Version 1 the code size requirements are reduced. However also the overall system performance is improved. When you disable Round Robin Task Switching even the data requirements are reduced. 3. Problems solved in RTX51 TINY Version 2.02

The following known problems of RTX51 Tiny are corrected in Version 2.02: a) RTX51 Tiny V1.06: isr_send_signal function may destroy the READY status when an interrupt occurs during os_wait, whereby the current task is waiting for the signal from this interrupt. b) RTX51 Tiny V1.06: K_IVL and K_SIG event cannot be combined in os_wait since it is not possible to correct the interval timer. In RTX51 Tiny V2.0 the function os_reset_interval allows you to correct the interval timer. c) RTX51 Tiny V1.06: TIMESHARING (round-robin time) cannot be set to 1. In in this case it can happen (when the interrupt appears before the robin-time is set) that the timeout is delayed 256 system clock ticks. d) RTX51 Tiny V1.06: When user interrupts are longer than a RTX51 Tiny System Clock Timer Tick, the RTX51 Tiny System Clock Timer is called recursively. This overwrites the values SAVEPSW and SAVEACC with wrong values and causes typically a system crash. In RTX51 Tiny V2.0 it is recommended that you set LONG_USR_INTR EQU 1 in the configuration file CONF_TNY.A51 if your application contains an interrupt function that may take longer for execution than the RTX51 Tiny System Clock Timer Interval time. It might be also required to set this flag when your code executes most of the time interrupt code with high interrupt priority. e) RTX51 Tiny V2.00 BETA: os_wait did not reset the SIGNAL event, when the signal was already set before the os_wait call. f) RTX51 Tiny V2.00 BETA: os_wait with K_IVL argument did not work. g) RTX51 Tiny V2.01: os_wait returned wrong event codes when K_SIG and K_TMO was used in different combinations within the same task. h) RTX51 Tiny V2.01: K_IVL may caused 256 additional timer tick delays if the interval time is lower than the timer underflow value of that task.

4.

Example Programs

The following example programs are provided with RTX51 Tiny Version2. Examples\Ex1 Examples\Ex2 Demonstrates Round-Robin Multitasking. Shows how to use time delays and signals with the os_wait function.

Examples\Traffic A time-controlled Traffic Light Controller.

Examples\Banking Uses code banking a shows several new features of RTX Tiny Version 2.