T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

92 CHAPTER 4. T-KERNEL/OS FUNCTIONS tk wai flg Wait Event Flag [C Language Interface] ER ercd = tk_wai_flg ( ID flgid, UINT waiptn, UINT wfmode, UINT *p_flgptn, TMO tmout ) ; [Parameters] ID flgid Event flag ID UINT waiptn Wait bit pattern UINT wfmode Wait release condition TMO tmout Timeout designation [Return Parameters] ER ercd Error code UINT flgptn Event flag bit pattern [Error Codes] E OK E ID E NOEXS E PAR E OBJ E DLT E RLWAI E DISWAI E TMOUT E CTX Normal completion Invalid ID number (flgid is invalid or cannot be used) Object does not exist (the event flag designated in flgid does not exist) Parameter error (waiptn = 0, wfmode is invalid, or tmout ≤ (−2)) Invalid object state (multiple tasks are waiting for an event flag with TA WSGL attribute) The object being waited for was deleted (the designated event flag was deleted while waiting) Wait state released (tk rel wai received in wait state) Wait released by wait disabled state Polling failed or timeout Context error (issued from task-independent portion or in dispatch disabled state) [Description] Waits for the event flag designated in flgid to be set, fulfilling the wait release condition designated in wfmode. If the event flag designated in flgid already meets the wait release condition set in wfmode, the waiting task continues executing without going to WAIT state. wfmode is designated as follows. wfmode := (TWF_ANDW || TWF_ORW) | [TWF_CLR || TWF_BITCLR] Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
4.4. SYNCHRONIZATION AND COMMUNICATION FUNCTIONS 93 TWF ANDW 0x00 AND wait condition TWF ORW 0x01 OR wait condition TWF CLR 0x10 Clear all TWF BITCLR 0x20 Clear condition bit only If TWF ORW is designated, the issuing task waits for any of the bits designated in waiptn to be set for the event flag designated in flgid (OR wait). If TWF ANDW is designated, the issuing task will wait for all of the bits designated in waiptn to be set for the event flag designated in flgid (AND wait). If TWF CLR specification is not designated, the event flag values will remain unchanged even after the conditions have been satisfied and the task has been released from WAIT state. If TWF CLR is designated, all bits of the event flag will be cleared to 0 once wait conditions of the waiting task have been met. If TWF BITCLR is designated, then when the conditions are met and the task is released from WAIT state, only the bits matching the event flag wait release conditions are cleared to 0 (event flag values &= ~wait release conditions). The return parameter flgptn returns the value of the event flag after the WAIT state of a task has been released due to this system call. If TWF CLR or TWF BITCLR was designated, the value before event flag bits were cleared is returned. The value returned by flgptn fulfills the wait release conditions of this system call. The contents of flgptn are indeterminate if the wait is released due to timeout or the like. A maximum wait time (timeout) can be set in tmout. If the tmout time elapses before the wait release condition is met, the system call terminates, returning timeout error code E TMOUT. Only positive values can be set in tmout. The time base for tmout (time unit) is the same as that for system time (= 1 ms). When TMO POL = 0 is set in tmout, this means 0 was designated as the timeout value, and E TMOUT is returned without entering WAIT state even if the condition is not met. When TMO FEVR = (−1) is set in tmout, this means infinity was designated as the timeout value, and the task continues to wait for the condition to be met without timing out. In the case of a timeout, the event flag bits are not cleared even if TWF CLR or TWF BITCLR was designated. Setting waiptn to 0 results in Parameter error E PAR. A task cannot execute tk wai flg for an event flag having the TA WSGL attribute while another task is waiting for it. Error code E OBJ will be returned for the task issuing the subsequent tk wai flg, regardless of whether that task would have gone to WAIT state; i.e., regardless of whether the wait release conditions would be met. If an event flag has the TA WMUL attribute, multiple tasks can wait for it at the same time. Waiting tasks can be queued, and the WAIT states of multiple tasks can be released by issuing tk set flg just once. If multiple tasks are queued for an event flag with TA WMUL attribute, the behavior is as follows. • Tasks are queued in either FIFO or priority order. (Release of wait state does not always start from the head of the queue, however, depending on factors such as waiptn and wfmode settings.) • If TWF CLR or TWF BITCLR was designated by a task in the queue, the event flag is cleared when that task is released from WAIT state. • Tasks later in the queue than a task designating TWF CLR or TWF BITCLR will see the event flag after it has already been cleared. If multiple tasks having the same priority are released from waiting simultaneously as a result of tk set flg, the order of tasks in the ready queue (precedence) after release will continue to be the same as their original order in the event flag queue. Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
Page 1 and 2:
T-Kernel Specification T-Kernel 1.B
Page 3 and 4:
Contents 1 T-Kernel Overview 1 1.1
Page 5 and 6:
CONTENTS v tk set flg (Set Event Fl
Page 7 and 8:
CONTENTS vii 5.2.2 Address Space Ch
Page 9 and 10:
CONTENTS ix td cal que (Reference Q
Page 11 and 12:
List of Figures 1.1 Position of T-K
Page 13 and 14:
List of Tables 2.1 State Transition
Page 15 and 16:
System Call Notation In the parts o
Page 17 and 18:
Index of T-Kernel/OS System Calls T
Page 19 and 20:
INDEX OF T-KERNEL/OS SYSTEM CALLS x
Page 21 and 22:
Index of T-Kernel/SM Extended SVC L
Page 23 and 24:
Index of T-Kernel/DS System Calls T
Page 25 and 26:
Chapter 1 T-Kernel Overview 1.1 Pos
Page 27 and 28:
1.2. SCALABILITY 3 • Middleware m
Page 29 and 30:
Chapter 2 Concepts Underlying the T
Page 31 and 32:
2.2. TASK STATES AND SCHEDULING RUL
Page 33 and 34:
2.2. TASK STATES AND SCHEDULING RUL
Page 35 and 36:
2.3. INTERRUPT HANDLING 11 preceden
Page 37 and 38:
2.5. SYSTEM STATES 13 Transient sta
Page 39 and 40:
2.7. MEMORY 15 which the upper and
Page 41 and 42:
Chapter 3 Common T-Kernel Specifica
Page 43 and 44:
3.2. SYSTEM CALLS 19 /* * Common co
Page 45 and 46:
3.2. SYSTEM CALLS 21 Ordinarily a f
Page 47 and 48:
3.3. HIGH-LEVEL LANGUAGE SUPPORT RO
Page 49 and 50:
Chapter 4 T-Kernel/OS Functions Thi
Page 51 and 52:
4.1. TASK MANAGEMENT FUNCTIONS 27 t
Page 53 and 54:
4.1. TASK MANAGEMENT FUNCTIONS 29 #
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66: 4.1. TASK MANAGEMENT FUNCTIONS 41 t
Page 77 and 78: 4.2. TASK-DEPENDENT SYNCHRONIZATION
Page 93 and 94: 4.3. TASK EXCEPTION HANDLING FUNCTI
Page 101 and 102: 4.4. SYNCHRONIZATION AND COMMUNICAT
Page 115: 4.4. SYNCHRONIZATION AND COMMUNICAT
Page 131 and 132: 4.5. EXTENDED SYNCHRONIZATION AND C
Page 167 and 168:
4.5. EXTENDED SYNCHRONIZATION AND C
Page 169 and 170:
4.5. EXTENDED SYNCHRONIZATION AND C
Page 171 and 172:
4.6. MEMORY POOL MANAGEMENT FUNCTIO
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
4.7. TIME MANAGEMENT FUNCTIONS 163
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
4.8. INTERRUPT MANAGEMENT FUNCTIONS
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
4.9. SYSTEM MANAGEMENT FUNCTIONS 19
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
4.10. SUBSYSTEM MANAGEMENT FUNCTION
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Chapter 5 T-Kernel/SM Details of th
Page 245 and 246:
5.1. SYSTEM MEMORY MANAGEMENT FUNCT
Page 247 and 248:
5.2. ADDRESS SPACE MANAGEMENT FUNCT
Page 249 and 250:
5.2. ADDRESS SPACE MANAGEMENT FUNCT
Page 251 and 252:
5.3. DEVICE MANAGEMENT FUNCTIONS 22
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
5.5. IO PORT ACCESS SUPPORT FUNCTIO
Page 277 and 278:
5.7. SYSTEM CONFIGURATION INFORMATI
Page 279 and 280:
5.7. SYSTEM CONFIGURATION INFORMATI
Page 281:
5.8. SUBSYSTEM AND DEVICE DRIVER ST
Page 284 and 285:
260 CHAPTER 6. T-KERNEL/DS FUNCTION
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
284 CHAPTER 7. REFERENCE INT tevptn
Page 310 and 311:
286 CHAPTER 7. REFERENCE ER ercd =
Page 312 and 313:
288 CHAPTER 7. REFERENCE INT ct = t
Page 314:
290 CHAPTER 7. REFERENCE E OACV ERC
show all

T-Kernel Specification (1.B0.02)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?