Development Environment Document Information Category TN-OS*

The Datasheet Archive - 100 Million Datasheets from 7500 Manufacturers.

Development Environment Document Information Category TN-OS*

Datasheet Thumbnail

Top Searches for this datasheet

Nippon Bldg., 2-6-2, Ohte-machi, Chiyoda-ku, Tokyo 100-0004, Japan RenesasTechnology Corp. Product Category
Development Environment
Document Information Category
TN-OS*-076A/EA
Rev.
Title
Notes Variable-Size Memory Pool Shared Stack Functions HI2000/3
Usage Limitation
Applicable Product
HS0200ITZE1SRE, HS0200ITZE1SRE-E, HS0200ITZE1SRB, HS0200ITZE1SRB-E, HS0200ITZE1SRS, HS0200ITZE1SRS-E V1.00 V1.10
Reference Document
HI2000/3 Hitachi Industrial Realtime Operating System Series User's Manual ADE-702-208A Revision
Thank using product. Please observe notes listed below variable-size pool shared stack functions. These problems will fixed following revision (V1.1.02). Variable-Size Memory Pool Function Release Wait Queue [Problem] When there multiple wait queues variable-size memory pool, second later wait queues released. this case, tasks WAIT state will released next time rel_blk system call issued. [Conditions] This problem arise when both following conditions satisfied. There multiple tasks waiting acquire memory block. WAIT state first task acquire memory block been released timeout tget_blk system call rel_wai ter_tsk (excluding rel_blk system call). Example:
Memory pool area (size: bytes)
First wait task
Second wait task
Used area: bytes Empty area: bytes
Size acquire: bytes
Size acquire: bytes
rel_wai ter_tsk been issued timeout period tget_blk elapsed
above figure, task task waiting acquire bytes bytes, respectively, 200-byte memory pool. When timeout task occurs after specified timeout period tget_blk elapsed WAIT state task been released system call rel_wai ter_tsk issued task task still remains WAIT state acquires memory block even though become first wait task. [Solution] Keep sufficient variable-size memory pool area that task will enter WAIT state.
2004. Renesas Technology Corp., rights reserved.
Page
RENESAS TECHNICAL UPDATE TN-OS*-076A/EA
Size Memory Pool Area [Problem] available size variable-size memory pool reduced. [Conditions] This problem arise when both following conditions satisfied. There task waiting acquire memory block. WAIT state first wait task released while memory block being returned. Example:
Memory pool area (size: bytes) Wait task (with timeout)
Used area: bytes Empty area: bytes
Size acquire: bytes
Returning memory block rel_blk
Interrupt occurs. This causes timeout wait task.
above figure, there wait task with timeout memory pool. When timer interrupt occurs causes timeout timeout period remained wait task zero while memory block being returned rel_blk, bytes memory pool area will used thus empty area will bytes. wait task already timeout acquired memory block. However, memory pool assumes that memory block acquired. [Solution] Keep sufficient variable-size memory pool area that task will enter WAIT state.
Shared Stack Function [Problem] Tasks waiting shared stack executed. [Condition] addresses lower bits task stack area (section name: h2sstack) work area (section name: hi8_2s_ram) same. [Solution] Allocate different addresses lower bits task stack area work area.
Page

Development Environment Document Information Category TN-OS*

Top Searches for this datasheet

Other recent searches