T-Kernel Specification (1.B0.02)

More documents

Recommendations

Info

68 CHAPTER 4. T-KERNEL/OS FUNCTIONS tk ena wai Enable Task Wait [C Language Interface] ER ercd = tk_ena_wai ( ID tskid ) ; [Parameters] ID tskid Task ID [Return Parameters] ER ercd Error code [Error Codes] E OK E ID E NOEXS Normal completion Invalid ID number (tskid is invalid or cannot be used) Object does not exist (the task designated in tskid does not exist) [Description] Releases all wait disable conditions set by tk dis wai for the task designated in tskid. The invoking task can be designated by setting tskid = TSK SELF = 0. Note, however, that when a system call is issued from a task-independent portion and tskid = TSK SELF = 0 is designated, error code E ID is returned. Copyright c○ 2002, 2003 by T-Engine Forum T-Kernel 1.B0.02
4.3. TASK EXCEPTION HANDLING FUNCTIONS 69 4.3 Task Exception Handling Functions Task exception handling functions handle exception events occurring in a task, in the context of that task, interrupting normal task processing. A task exception handler is executed as a part of the task where the task exception occurred, in the context of that task and at the protection level designated when the task was created. The task states in a task exception handler, except for those states concerning task exceptions, are the same as the states when running an ordinary task portion; and the same system calls are available. A task exception handler can be started only when the target task is running a task portion. If the task is running any other portion when a task exception is raised, the task exception handler is started only after the task returns to the task portion. If a quasi-task portion (extended SVC) is executing when a task exception is raised, a break function corresponding to that extended SVC is called. The break function interrupts the extended SVC processing, and the task returns to the task portion. Requested task exceptions are cleared when the task exception handler is called (when the task exception handler starts running). Task exceptions are designated by task exception codes from 0 to 31, of which 0 is the highest priority and 31 the lowest. Task exception code 0 is handled differently from the others, as explained below. Task exception codes 1 to 31 : • These task exception handlers are not nested. A task exception (other than task exception code 0) raised while a task exception handler is running will be made pending. • On return from a task exception handler, the task resumes from the point where processing was interrupted by the exception. • It is also possible to use longjmp() or the like to jump to any point in the task without returning from the task exception handler. Task exception code 0: • This exception can be nested even while a task exception handler is executing for an exception of task exception code 1 to 31. Execution of task exception code 0 handlers is not nested. • A task exception handler runs after setting the user stack pointer to the initial setting when the task was started. In a system without a separate user stack and system stack, however, the stack pointer is not reset to its initial setting. • A task exception code 0 handler does not return to task processing. terminated. The task must be 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 77 and 78: 4.2. TASK-DEPENDENT SYNCHRONIZATION
Page 91: 4.2. TASK-DEPENDENT SYNCHRONIZATION
Page 95 and 96: 4.3. TASK EXCEPTION HANDLING FUNCTI
Page 101 and 102: 4.4. SYNCHRONIZATION AND COMMUNICAT
Page 131 and 132: 4.5. EXTENDED SYNCHRONIZATION AND C
Page 143 and 144:
4.5. EXTENDED SYNCHRONIZATION AND C
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
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?