Virtuoso User Manual - ClassicCMP

More documents

Recommendations

Info

Virtuoso : an overview on a node. The key to this transparency of topology is the use of a system definition file (see below). In this context we emphasize that with Virtuoso the node identifier is nothing more than an attribute of the object. The transparent distributed operation would not work if the semantics of the microkernel services and their implementation were not fully distributed. This imposes a certain programming methodology. E.g. global variables or pointers are only allowed if the programmer very well knows that only local references to it are used and the objects referencing to it will not be mapped over more than one target processor. When common memory is used, the objects must be protected using a resource lock . InputQueue ConsoleInputDriver Node#1 OutputQueue ConsoleOutputDriver DisplayTask MailBox1 SamplingTask2 + Sema1 Node#2 Node#4 SamplingTask1 + Sema2 + Sema3 MonitorTask Node#3 Microkernel Object Processor Node FIGURE 1 A possible mapping of objects onto a network P1 - 12 Virtuoso User Manual Copyright 1996 Eonic Systems
Virtuoso : an overview 3.3. A multi-level approach for speed and flexibility As any designer knows, a single tool or method cannot cover all of the different aspects of an application. In particular DSPs are increasingly used for signal processing and embedded control at the same time. This poses quite a challenge to the programming tool as it must handle timing constraints expressed in microseconds. Traditionally this meant programming in assembler at the interrupt level. One of the drawbacks of this approach is a lack of modularity and hence the sheer impossibility to build complex multitasking applications. Real-time multitasking kernels on the other hand provide for modularity but impose an unacceptable overhead for handling fast interrupts at the task level. On parallel DSPs the situation is even more demanding than on single processor DSPs. The reason is that interprocessor communication is generating interrupts that have to be processed at the system level. Hence a minimum interrupt latency as well as interrupt disabling time is a must. As an example consider the TMS320C40 DSP.This processor requires to handle already up to 14 interrupts sources without any of them being related to external hardware. The Virtuoso programming system solves this Gordian Knot by providing an open multilevel system built around a very fast nanokernel managing a number of processes . The user can program his critical code at the level he needs to achieve the desired performance while keeping the benefits of the other levels. Internally, the kernel manages the processor context as a resource, only swapping and restoring the minimum of registers that is needed. The different levels are described below. ISR stands for Interrupt Service Routine. LEVEL 1 : ISR0 level This level normally only accepts interrupts from the hardware. Interrupts need only be disabled during ISR0 (e.g. less than 1 microsecond on a C40). The developer can handle the interrupt completely at this level if required or pass it on to one of the higher levels. The latter is the recommended method as it disables global interrupts for a much shorter time. This approach allows to handle interrupts (in burstmode) at over 1 Million interrupts per sec on a C40. The programmer himself is responsible for saving and restoring the context on the stack of the interrupted task. PART 3 Copyright 1996 Eonic Systems Virtuoso User Manual P1 - 13
Page 1 and 2: Virtuoso The Virtual Single Proces
Page 3 and 4: Table of Contents Introduction INT
Page 5 and 6: Simulation in the control loop ....
Page 7 and 8: KS_ResetSema ......................
Page 9 and 10: Semaphores ........................
Page 11 and 12: KS_EnableISR ......................
Page 13 and 14: Preserved Registers ...............
Page 15 and 16: Addressing Modes ..................
Page 17 and 18: Introduction Introduction Virtuoso
Page 19 and 20: Release notes Release notes V.3.01
Page 21 and 22: Implementation-Specific Features Im
Page 23 and 24: The history of Virtuoso The history
Page 25 and 26: Manual Format Manual Format PART 1
Page 27 and 28: License agreement License agreement
Page 29 and 30: License agreement notice shall not
Page 31 and 32: License agreement submits to jurisd
Page 33 and 34: License agreement RETURN A SIGNED C
Page 37 and 38: Installation 1. Installation 1.1. I
Page 39 and 40: Installation 5. Run the final demon
Page 41 and 42: Installation 1.7. The final referen
Page 43 and 44: A short introduction any other appl
Page 45: Virtuoso : an overview 3.2.2. Class
Page 49 and 50: Virtuoso : an overview task switch
Page 51 and 52: Virtuoso : an overview An ISR enter
Page 53 and 54: Functional support from Virtuoso of
Page 55 and 56: Functional support from Virtuoso Th
Page 57 and 58: Functional support from Virtuoso ex
Page 59 and 60: Functional support from Virtuoso al
Page 61 and 62: Functional support from Virtuoso (c
Page 63 and 64: Functional support from Virtuoso Me
Page 65 and 66: Functional support from Virtuoso da
Page 67 and 68: Functional support from Virtuoso me
Page 69 and 70: Functional support from Virtuoso In
Page 71 and 72: Functional support from Virtuoso 4.
Page 73 and 74: Functional support from Virtuoso ru
Page 75 and 76: Functional support from Virtuoso sy
Page 77 and 78: Simple Examples /* resource node */
Page 79 and 80: Simple Examples The sender task is
Page 81 and 82: Applications from the start on, add
Page 85 and 86: Virtuoso microkernel types & data s
Page 93 and 94: Virtuoso microkernel services 8. Vi
Page 95 and 96: Virtuoso microkernel services ■ c
Page 97 and 98:
Virtuoso microkernel services ■ i
Page 99 and 100:
Virtuoso microkernel services ■ a
Page 101 and 102:
Virtuoso microkernel services ■ s
Page 103 and 104:
Nanokernel types and datastructures
Page 105 and 106:
Nanokernel services 10. Nanokernel
Page 107 and 108:
Alphabetical List of Virtuoso micro
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
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:
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:
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:
Hostserver and netloader 12. Hostse
Page 205 and 206:
Hostserver and netloader 12.2.2. Li
Page 207 and 208:
Hostserver and netloader 12.3. Host
Page 209 and 210:
Hostserver and netloader Driver Use
Page 211 and 212:
Runtime libraries int fputc ( int c
Page 213 and 214:
Runtime libraries int vsprintf ( ch
Page 215 and 216:
Runtime libraries the graphics libr
Page 217 and 218:
Runtime libraries void setfillstyle
Page 219 and 220:
Runtime libraries void circle ( int
Page 221 and 222:
Runtime libraries 13.2.6. Text plot
Page 223 and 224:
System Configuration 14. System Con
Page 225 and 226:
System Configuration NETLINK ROOT
Page 227 and 228:
System Configuration should be defi
Page 229 and 230:
System Configuration < : unidirecti
Page 231 and 232:
System Configuration Processor Numb
Page 233 and 234:
System Configuration The number mus
Page 235 and 236:
System Configuration /* * the size
Page 237 and 238:
Debugging environment under Virtuos
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Practical hints for correct use 16.
Page 255 and 256:
Practical hints for correct use If
Page 257 and 258:
Practical hints for correct use len
Page 259 and 260:
Microkernel C++ interface 17. Micro
Page 261 and 262:
Microkernel C++ interface first cha
Page 263 and 264:
Microkernel C++ interface the name
Page 265 and 266:
Microkernel C++ interface class KMa
Page 267 and 268:
Microkernel C++ interface class KQu
Page 269 and 270:
Microkernel C++ interface class KRe
Page 271 and 272:
Microkernel C++ interface versions
Page 273 and 274:
Microkernel C++ interface vkobjcts.
Page 275 and 276:
Microkernel C++ interface test1.cpp
Page 277 and 278:
Microkernel C++ interface ... test1
Page 279 and 280:
Microkernel C++ interface test1.cpp
Page 281 and 282:
Virtuoso The Virtual Single Proces
Page 283 and 284:
Virtuoso on the Analog Devices 2102
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Alphabetical List of nanokernel ent
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Predefined drivers ing 14 can delay
Page 333 and 334:
Predefined drivers Signal/Wait (2)
Page 335 and 336:
Predefined drivers LINKFILE:list of
Page 337 and 338:
Virtuoso on the ADSP 2106x SHARC 21
Page 339 and 340:
Page 341 and 342:
Virtuoso on the ADSP 2106x SHARC .e
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Virtuoso on the ADSP 2106x SHARC of
Page 351 and 352:
Page 353 and 354:
Virtuoso on the ADSP 2106x SHARC ..
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Predefined drivers 23. Predefined d
Page 373 and 374:
Predefined drivers 23.1.2. The host
Page 375 and 376:
Predefined drivers ■ speed: SSPEE
Page 377 and 378:
Task Level Timings signal to waitm
Page 379 and 380:
Application development hints. obje
Page 381 and 382:
Virtuoso on the Intel 80x86 26. Vir
Page 383 and 384:
Virtuoso on the Motorola 56K DSP 27
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Virtuoso on the Motorola 56K DSP Th
Page 391 and 392:
Virtuoso on the Motorola 56K DSP $0
Page 393 and 394:
Virtuoso on the Motorola 56K DSP Re
Page 395 and 396:
Virtuoso on the Motorola 56K DSP Fo
Page 397 and 398:
Page 399 and 400:
Virtuoso on the Motorola 56K DSP mo
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Virtuoso on the Motorola 56K DSP in
Page 409 and 410:
Page 411 and 412:
Virtuoso on the Motorola 68030 syst
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Virtuoso on the Motorola 96K DSP Ad
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Virtuoso on the Motorola 96K DSP ru
Page 433 and 434:
Page 435 and 436:
Virtuoso on the Motorola 96K DSP ;
Page 437 and 438:
Page 439 and 440:
Virtuoso on the Motorola 96K DSP mo
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Virtuoso on the Motorola 96K DSP wh
Page 453 and 454:
Virtuoso on the Motorola 68HC11. 30
Page 455 and 456:
Virtuoso on the Motorola 68HC16 mic
Page 457 and 458:
Virtuoso on the Mips R3000 systems.
Page 459 and 460:
Virtuoso on the INMOS T2xx, T4xx, T
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Virtuoso on the INMOS T9000 transpu
Page 477 and 478:
Virtuoso on the Texas Instruments T
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Programming the nanokernel actually
Page 501 and 502:
Programming the nanokernel The func
Page 503 and 504:
Programming the nanokernel The L_CH
Page 505 and 506:
Programming the nanokernel call. If
Page 507 and 508:
Programming the nanokernel nal stat
Page 509 and 510:
Programming the nanokernel tasks to
Page 511 and 512:
Programming the nanokernel 1. The f
Page 513 and 514:
Page 515 and 516:
Page 517 and 518:
Page 519 and 520:
Page 521 and 522:
Page 523 and 524:
Page 525 and 526:
Page 527 and 528:
Page 529 and 530:
Page 531 and 532:
Page 533 and 534:
Page 535 and 536:
Page 537 and 538:
Page 539 and 540:
Predefined drivers ment the PC inte
Page 541 and 542:
Glossary Abort (task) API Class Deb
Page 543 and 544:
Process Queue Resource Semaphore /S
Page 545 and 546:
Index Numerics 21020 relevant docum
Page 547 and 548:
KS_Enqueue P2 - 42 KS_EnqueueW P2 -
Page 549 and 550:
estorecrtmode P2 - 133 routing tabl
show all

Virtuoso User Manual - ClassicCMP

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

Delete template?

Save as template?