vxworks programmer's guide.pdf - DAQ Plone Site

More documents

Recommendations

Info

VxWorks 5.4 Programmer’s Guide HP-UX Windows The following is an example of a compiler command line for VxSim development. The file to be compiled in this example has a base name of applic. % cchppa -g -ansi -nostdinc -DRW_MULTI_THREAD -D_REENTRANT -O2 \ -fvolitile -fno-builtin -I. -I/wind/target/h -DCUP_SIMHPPA \ -c applic.c The following is an example of a compiler command line for VxSim development. The file to be compiled in this example has a base name of applic. Option Definitions % ccsimpc -DCPU=SIMNT -mpentium -ansi -nostdinc -g -nostdlib \ -fno-builtin -fno-defer-pop -Wall -DRW_MULTI_THREAD \ -D_REENTRANT -I. -I C:/Tornado/target/h -c applic.c The options shown in the example have the following meanings: 2 ccsimso Required; use ccsimso for the Solaris simulator, cchppa for the HP-UX simulator, and ccsimpc for the Windows simulator. -DCPU=SIMNT Required; defines the CPU type. See the table on page Defining the CPU Type, p.535. -mpentium Optional for Windows only; specifies Pentium optimizations. -ansi Recommended; supports all ANSI standard C programs. -nostdinc Required; searches only the directories specified with the -I flag (see below) and the current directory for header files. Does not search host-system include files. -O2 Optional; implements optimization. Not recommended for the PC simulator. 2. For more information on these and other compiler options, see the GNU ToolKit User’s Guide. WRS supports compiler options used in building WRS software; see the Guide for a list. Other options are not supported, although they are available with the tools as shipped. 536
H VxSim -g Optional; produces debugging information. -nostdlib Required for Windows; does not use the standard system startup files or libraries when linking. -fvolatile Required for Solaris and HP-UX; considers all memory references through pointers to be volatile. -fno-builtin Required; uses library calls even for common library subroutines. -fno-defer-pop Required for Windows, optional for UNIX. Causes arguments to each function call to be popped as soon as the function returns. -Wall Optional; enables most warnings. -DRW_MULTI_THREAD Required; specifies Rogue Wave multi-threading. -D_REENTRANT Required; causes reentrant code to be generated. -I $WIND_BASE/target/h Required; includes VxWorks header files. (Additional -I flags may be included to specify other header files.) -c Required; specifies that the module is to be compiled only, and not linked for execution under the host. applic.language_id Required; the files to compile. For C compilation, specify a suffix of .c. For C++ compilation, specify a suffix of .cpp. The output is an unlinked object module with the suffix .o; for the example, the output is applic.o. The object module format for each simulator is as follows: SIMSPARCSOLARIS SIMHPPA SIMNT ELF SOM a.out Following C++ compilation, the compiled object module (applic.o)ismunched. Munching is the process of scanning an object module for non-local static objects, and generating data structures that VxWorks run-time support can use H 537
Page 1 and 2:
VxWorks Programmer’s Guide ® 5.4
Page 3:
1 Overview ........................
Page 6 and 7:
VxWorks 5.4 Programmer’s Guide 2
Page 8 and 9:
VxWorks 5.4 Programmer’s Guide 2.
Page 10:
VxWorks 5.4 Programmer’s Guide 3.
Page 13 and 14:
Contents 4.4.2 Initializing the raw
Page 15 and 16:
Contents 6.2.4 Shared-Memory Alloca
Page 17 and 18:
Contents The -I Compiler Flag .....
Page 19 and 20:
Contents 9.2.6 Summary of Target an
Page 21 and 22:
Contents Double-word Integers: long
Page 23 and 24:
Contents F.2 Building Applications
Page 25 and 26:
Contents H.4 Architecture Considera
Page 27 and 28:
1 Overview 1.1 Introduction This ma
Page 29 and 30:
1 Overview You can use the cross-de
Page 31 and 32:
1 Overview ■ ■ ■ ■ ■ Perf
Page 33 and 34:
1 Overview services. Using these in
Page 35 and 36:
1 Overview RT-11 Compatible File Sy
Page 37 and 38:
1 Overview Target-Resident Tools 1
Page 39 and 40:
1 Overview writer and a single read
Page 41 and 42:
1 Overview Board Support Packages (
Page 43 and 44:
1 Overview 1.6 Documentation Conven
Page 45 and 46:
2 Basic OS 2.1 Introduction Modern
Page 47 and 48:
2 Basic OS - signal handlers - debu
Page 49 and 50:
2 Basic OS Preemptive Priority Sche
Page 51 and 52:
2 Basic OS Preemption Locks The win
Page 53 and 54:
2 Basic OS Table 2-4 Task Name and
Page 55 and 56:
2 Basic OS Table 2-8 Task-Deletion
Page 57 and 58:
2 Basic OS 2.3.5 Tasking Extensions
Page 59 and 60:
2 Basic OS Table 2-12 POSIX Schedul
Page 61 and 62:
2 Basic OS Example 2-2 Getting POSI
Page 63 and 64:
2 Basic OS A Separate errno Value f
Page 65 and 66:
2 Basic OS 2.3.9 Shared Code and Re
Page 67 and 68:
2 Basic OS Figure 2-5 Stack Variabl
Page 69 and 70:
2 Basic OS Figure 2-7 Multiple Task
Page 71 and 72:
2 Basic OS tPortmapd If you have in
Page 73 and 74:
2 Basic OS sometimes be necessary w
Page 75 and 76:
2 Basic OS the other semaphore-cont
Page 77 and 78:
2 Basic OS * blocked on semaphore w
Page 79 and 80:
2 Basic OS ■ ■ ■ ■ It can b
Page 81 and 82:
2 Basic OS guarding the resource le
Page 83 and 84:
2 Basic OS semaphore with an initia
Page 85 and 86:
2 Basic OS Table 2-15 POSIX Semapho
Page 87 and 88:
2 Basic OS printf ("unnameSem: sem_
Page 89 and 90:
2 Basic OS To remove a semaphore, a
Page 91 and 92:
2 Basic OS 2.4.4 Message Queues Mod
Page 93 and 94:
2 Basic OS Urgent Messages The msgQ
Page 95 and 96:
2 Basic OS queue is full, mq_send(
Page 97 and 98:
2 Basic OS void sendTask (void) { m
Page 99 and 100:
2 Basic OS mySigAction.sa_sigaction
Page 101 and 102:
2 Basic OS /* Read in the messages
Page 103 and 104:
2 Basic OS printf ("mq_receive with
Page 105 and 106:
2 Basic OS intertask messages. In V
Page 107 and 108:
2 Basic OS individually addressed p
Page 109 and 110:
2 Basic OS Table 2-20 Basic Signal
Page 111 and 112:
2 Basic OS 2.5 Interrupt Service Co
Page 113 and 114:
2 Basic OS 2.5.3 Special Limitation
Page 115 and 116:
2 Basic OS the boot ROMs re-display
Page 117 and 118:
2 Basic OS Table 2-24 Watchdog Time
Page 119 and 120:
2 Basic OS 2.8 POSIX Memory-Locking
Page 121 and 122:
3 I/O System 3.1 Introduction The V
Page 123 and 124:
3 I/O System The first refers to a
Page 125 and 126:
3 I/O System Table 3-1 Basic I/O Ro
Page 127 and 128:
3 I/O System Table 3-2 File Access
Page 129 and 130:
3 I/O System The write( ) routine e
Page 131 and 132:
3 I/O System Example 3-1 Applicatio
Page 133 and 134:
3 I/O System 3.4.1 Using Stdio Note
Page 135 and 136:
3 I/O System While sscanf( ) is imp
Page 137 and 138:
3 I/O System (which can be seen on
Page 139 and 140:
3 I/O System that reason, their ret
Page 141 and 142:
3 I/O System /* clean up */ if (aio
Page 143 and 144:
3 I/O System aiocb_write.aio_sigeve
Page 145 and 146:
3 I/O System Tty Options The tty de
Page 147 and 148:
3 I/O System possible to restart Vx
Page 149 and 150:
3 I/O System Writing to Pipes from
Page 151 and 152:
3 I/O System Mounting a Remote NFS
Page 153 and 154:
3 I/O System Files on a network dev
Page 155 and 156:
3 I/O System with rt11Fs using rt11
Page 157 and 158:
3 I/O System the same BSP, then dif
Page 159 and 160:
3 I/O System typedef struct /* SCSI
Page 161 and 162:
3 I/O System /* configure Wincheste
Page 163 and 164:
3 I/O System /* initialize a tapeFs
Page 165 and 166:
3 I/O System 3.7.7 Sockets In VxWor
Page 167 and 168:
3 I/O System VxWorks file systems,
Page 169 and 170:
3 I/O System Drivers can optionally
Page 171 and 172:
3 I/O System Figure 3-2 Example - D
Page 173 and 174:
3 I/O System information. In partic
Page 175 and 176:
3 I/O System Figure 3-5 Example: Ca
Page 177 and 178:
3 I/O System Figure 3-6 Example: Ca
Page 179 and 180:
3 I/O System can also occur elsewhe
Page 181 and 182:
3 I/O System if (pMyDrvDev->myDrvDa
Page 183 and 184:
3 I/O System else { cacheFlush (DAT
Page 185 and 186:
3 I/O System the end of the written
Page 187 and 188:
3 I/O System operations in the init
Page 189 and 190:
3 I/O System Table 3-15 Fields in t
Page 191 and 192:
3 I/O System pDev numBytes buffer f
Page 193 and 194:
3 I/O System funcCode the requested
Page 195 and 196:
3 I/O System dosFsModeChange( )) is
Page 197 and 198:
3 I/O System routine is the opposit
Page 199 and 200:
3 I/O System end-of-file. However,
Page 201 and 202:
4 Local File Systems 4.1 Introducti
Page 203 and 204:
4 Local File Systems Figure 4-1 MS-
Page 205 and 206:
4 Local File Systems Figure 4-2 FAT
Page 207 and 208:
4 Local File Systems Volume Label A
Page 209 and 210:
4 Local File Systems The routine do
Page 211 and 212:
4 Local File Systems limit its use,
Page 213 and 214:
4 Local File Systems value (at leas
Page 215 and 216:
4 Local File Systems You can also e
Page 217 and 218:
4 Local File Systems The most commo
Page 219 and 220:
4 Local File Systems 4.2.14 Reading
Page 221 and 222:
4 Local File Systems /* set read-on
Page 223 and 224:
4 Local File Systems data would be
Page 225 and 226:
4 Local File Systems To explicitly
Page 227 and 228:
4 Local File Systems It is also pos
Page 229 and 230:
4 Local File Systems Table 4-5 I/O
Page 231 and 232:
4 Local File Systems ! WARNING: The
Page 233 and 234:
4 Local File Systems 4.3.4 Mounting
Page 235 and 236:
4 Local File Systems Ready-change c
Page 237 and 238:
4 Local File Systems 4.4.2 Initiali
Page 239 and 240:
4 Local File Systems 4.4.6 Changing
Page 241 and 242:
4 Local File Systems However, if th
Page 243 and 244:
4 Local File Systems The tapeFsInit
Page 245 and 246:
4 Local File Systems Mounting Volum
Page 247 and 248:
4 Local File Systems Table 4-9 MTIO
Page 249 and 250:
4 Local File Systems Each I/O reque
Page 251 and 252:
4 Local File Systems ! WARNING: Whe
Page 253 and 254:
5 C++ Development Basic Support and
Page 255 and 256:
5 C++ Development routines in WindS
Page 257 and 258:
5 C++ Development ! WARNING: In the
Page 259 and 260:
5 C++ Development Calling Static Co
Page 261 and 262:
5 C++ Development -frepo This appro
Page 263 and 264:
5 C++ Development consult any stand
Page 265 and 266:
5 C++ Development Run-Time Type Inf
Page 267 and 268:
5 C++ Development modification hist
Page 269 and 270:
5 C++ Development */ object_t* clas
Page 271 and 272:
5 C++ Development catch (exception)
Page 273 and 274:
5 C++ Development /****************
Page 275 and 276:
5 C++ Development /* object_registr
Page 277 and 278:
5 C++ Development ! CAUTION: In ord
Page 279 and 280:
5 C++ Development /* Create a watch
Page 281 and 282:
6 Shared-Memory Objects Optional Co
Page 283 and 284:
6 Shared-Memory Objects 6.2.1 Name
Page 285 and 286:
6 Shared-Memory Objects 6.2.2 Share
Page 287 and 288:
6 Shared-Memory Objects Figure 6-1
Page 289 and 290:
6 Shared-Memory Objects /**********
Page 291 and 292:
Page 293 and 294:
6 Shared-Memory Objects } { if (msg
Page 295 and 296:
6 Shared-Memory Objects memory syst
Page 297 and 298:
6 Shared-Memory Objects Example 6-3
Page 299 and 300:
6 Shared-Memory Objects /* get shar
Page 301 and 302:
6 Shared-Memory Objects if ((smMemP
Page 303 and 304:
6 Shared-Memory Objects 6.3 Interna
Page 305 and 306:
6 Shared-Memory Objects 6.3.5 Cache
Page 307 and 308:
Page 309 and 310:
6 Shared-Memory Objects Table 6-5 W
Page 311 and 312:
6 Shared-Memory Objects Table 6-6 C
Page 313 and 314:
6 Shared-Memory Objects ■ ■ ■
Page 315 and 316:
7 Virtual Memory Interface Basic Su
Page 317 and 318:
7 Virtual Memory Interface To make
Page 319 and 320:
7 Virtual Memory Interface 7.5 Usin
Page 321 and 322:
7 Virtual Memory Interface Change t
Page 323 and 324:
7 Virtual Memory Interface Figure 7
Page 325 and 326:
7 Virtual Memory Interface /* Selec
Page 327 and 328:
7 Virtual Memory Interface typedef
Page 329 and 330:
7 Virtual Memory Interface processo
Page 331 and 332:
7 Virtual Memory Interface * This r
Page 333 and 334:
7 Virtual Memory Interface 0x1fb800
Page 335 and 336:
8 Configuration and Build 8.1 Intro
Page 337 and 338:
8 Configuration and Build The Syste
Page 339 and 340:
8 Configuration and Build devices.
Page 341 and 342:
8 Configuration and Build NOTE: The
Page 343 and 344:
8 Configuration and Build The Initi
Page 345 and 346:
8 Configuration and Build Installat
Page 347 and 348:
8 Configuration and Build As noted
Page 349 and 350:
8 Configuration and Build Table 8-1
Page 351 and 352:
8 Configuration and Build 8.4 Build
Page 353 and 354:
8 Configuration and Build tty heade
Page 355 and 356:
8 Configuration and Build ! CAUTION
Page 357 and 358:
8 Configuration and Build To define
Page 359 and 360:
8 Configuration and Build -DCPU=arc
Page 361 and 362:
8 Configuration and Build ! WARNING
Page 363 and 364:
8 Configuration and Build linker ld
Page 365 and 366:
8 Configuration and Build The Globa
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
8 Configuration and Build - INCLUDE
Page 373 and 374:
8 Configuration and Build Aside fro
Page 375 and 376:
8 Configuration and Build ROM image
Page 377 and 378:
8 Configuration and Build 8.7 Build
Page 379 and 380:
8 Configuration and Build Figure 8-
Page 381 and 382:
8 Configuration and Build sake of c
Page 383 and 384:
8 Configuration and Build by the su
Page 385 and 386:
8 Configuration and Build compilati
Page 387 and 388:
8 Configuration and Build CC_DEFINE
Page 389 and 390:
8 Configuration and Build 8.8.2 Usi
Page 391 and 392:
8 Configuration and Build can simpl
Page 393 and 394:
8 Configuration and Build As before
Page 395 and 396:
9 Target Shell 9.1 Introduction In
Page 397 and 398:
9 Target Shell 9.2.2 Using the Targ
Page 399 and 400:
9 Target Shell Note that an offendi
Page 401 and 402:
9 Target Shell ■ ■ ■ ■ ■
Page 403 and 404:
9 Target Shell by reading the targe
Page 405 and 406:
9 Target Shell Table 9-3 Network Sh
Page 407:
Appendices 381
Page 410 and 411:
VxWorks 5.4 Programmer’s Guide De
Page 412 and 413:
VxWorks 5.4 Programmer’s Guide A.
Page 414 and 415:
VxWorks 5.4 Programmer’s Guide
Page 416 and 417:
VxWorks 5.4 Programmer’s Guide Th
Page 418 and 419:
VxWorks 5.4 Programmer’s Guide Mo
Page 420 and 421:
Page 422 and 423:
VxWorks 5.4 Programmer’s Guide If
Page 424 and 425:
VxWorks 5.4 Programmer’s Guide Fi
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
VxWorks 5.4 Programmer’s Guide db
Page 432 and 433:
VxWorks 5.4 Programmer’s Guide a.
Page 434 and 435:
VxWorks 5.4 Programmer’s Guide SP
Page 436 and 437:
VxWorks 5.4 Programmer’s Guide in
Page 438 and 439:
VxWorks 5.4 Programmer’s Guide th
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
VxWorks 5.4 Programmer’s Guide Bo
Page 448 and 449:
VxWorks 5.4 Programmer’s Guide In
Page 450 and 451:
Page 452 and 453:
VxWorks 5.4 Programmer’s Guide Me
Page 454 and 455:
Page 456 and 457:
Page 458 and 459:
VxWorks 5.4 Programmer’s Guide to
Page 460 and 461:
VxWorks 5.4 Programmer’s Guide ob
Page 462 and 463:
VxWorks 5.4 Programmer’s Guide Ta
Page 464 and 465:
Page 466 and 467:
VxWorks 5.4 Programmer’s Guide he
Page 468 and 469:
VxWorks 5.4 Programmer’s Guide Be
Page 470 and 471:
VxWorks 5.4 Programmer’s Guide In
Page 472 and 473:
VxWorks 5.4 Programmer’s Guide }
Page 474 and 475:
VxWorks 5.4 Programmer’s Guide So
Page 476 and 477:
Page 478 and 479:
VxWorks 5.4 Programmer’s Guide Bu
Page 480 and 481:
Page 482 and 483:
VxWorks 5.4 Programmer’s Guide bo
Page 484 and 485:
VxWorks 5.4 Programmer’s Guide de
Page 486 and 487:
VxWorks 5.4 Programmer’s Guide If
Page 488 and 489:
VxWorks 5.4 Programmer’s Guide TF
Page 490 and 491:
Page 492 and 493:
VxWorks 5.4 Programmer’s Guide ro
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
VxWorks 5.4 Programmer’s Guide nu
Page 500 and 501:
Page 502 and 503:
VxWorks 5.4 Programmer’s Guide lp
Page 504 and 505:
Page 506 and 507:
Page 508 and 509:
VxWorks 5.4 Programmer’s Guide NO
Page 510 and 511:
Page 512 and 513: VxWorks 5.4 Programmer’s Guide R3
Page 514 and 515: VxWorks 5.4 Programmer’s Guide Vi
Page 516 and 517: VxWorks 5.4 Programmer’s Guide Fi
Page 518 and 519: VxWorks 5.4 Programmer’s Guide yo
Page 520 and 521: VxWorks 5.4 Programmer’s Guide -c
Page 522 and 523: VxWorks 5.4 Programmer’s Guide Th
Page 524 and 525: VxWorks 5.4 Programmer’s Guide EL
Page 526 and 527: VxWorks 5.4 Programmer’s Guide Ta
Page 530 and 531: VxWorks 5.4 Programmer’s Guide Me
Page 532 and 533: VxWorks 5.4 Programmer’s Guide 50
Page 534 and 535: VxWorks 5.4 Programmer’s Guide G.
Page 536 and 537: VxWorks 5.4 Programmer’s Guide -n
Page 538 and 539: VxWorks 5.4 Programmer’s Guide G.
Page 540 and 541: VxWorks 5.4 Programmer’s Guide
Page 542 and 543: VxWorks 5.4 Programmer’s Guide in
Page 544 and 545: VxWorks 5.4 Programmer’s Guide CO
Page 546 and 547: VxWorks 5.4 Programmer’s Guide An
Page 548 and 549: VxWorks 5.4 Programmer’s Guide Fl
Page 552 and 553: VxWorks 5.4 Programmer’s Guide No
Page 554 and 555: VxWorks 5.4 Programmer’s Guide Me
Page 560 and 561: VxWorks 5.4 Programmer’s Guide To
Page 564 and 565: VxWorks 5.4 Programmer’s Guide to
Page 566 and 567: VxWorks 5.4 Programmer’s Guide Ar
Page 568 and 569: VxWorks 5.4 Programmer’s Guide To
Page 570 and 571: VxWorks 5.4 Programmer’s Guide In
Page 574 and 575: VxWorks 5.4 Programmer’s Guide !
Page 576 and 577: VxWorks 5.4 Programmer’s Guide 2.
Page 578 and 579: VxWorks 5.4 Programmer’s Guide Cl
Page 580 and 581: VxWorks 5.4 Programmer’s Guide UL
Page 582 and 583: VxWorks 5.4 Programmer’s Guide Ad
Page 584 and 585: VxWorks 5.4 Programmer’s Guide On
Page 586 and 587: VxWorks 5.4 Programmer’s Guide 1.
Page 590 and 591: VxWorks 5.4 Programmer’s Guide I.
Page 596 and 597: VxWorks 5.4 Programmer’s Guide Fo
Page 598 and 599: VxWorks 5.4 Programmer’s Guide su
Page 600 and 601: VxWorks 5.4 Programmer’s Guide Co
Page 602 and 603: VxWorks 5.4 Programmer’s Guide I.
Page 604 and 605: VxWorks 5.4 Programmer’s Guide (3
Page 608 and 609: VxWorks 5.4 Programmer’s Guide Ta
Page 612 and 613:
VxWorks 5.4 Programmer’s Guide ai
Page 614 and 615:
VxWorks 5.4 Programmer’s Guide st
Page 616 and 617:
VxWorks 5.4 Programmer’s Guide ba
Page 618 and 619:
VxWorks 5.4 Programmer’s Guide cr
Page 620 and 621:
VxWorks 5.4 Programmer’s Guide DO
Page 622 and 623:
VxWorks 5.4 Programmer’s Guide ex
Page 624 and 625:
VxWorks 5.4 Programmer’s Guide -f
Page 626 and 627:
VxWorks 5.4 Programmer’s Guide IN
Page 628 and 629:
VxWorks 5.4 Programmer’s Guide se
Page 630 and 631:
Page 632 and 633:
Page 634 and 635:
Page 636 and 637:
VxWorks 5.4 Programmer’s Guide GD
Page 638 and 639:
VxWorks 5.4 Programmer’s Guide an
Page 640 and 641:
VxWorks 5.4 Programmer’s Guide re
Page 642 and 643:
VxWorks 5.4 Programmer’s Guide co
Page 644 and 645:
Page 646 and 647:
VxWorks 5.4 Programmer’s Guide ta
Page 648 and 649:
VxWorks 5.4 Programmer’s Guide VM
Page 650 and 651:
VxWorks 5.4 Programmer’s Guide X
show all

vxworks programmer's guide.pdf - DAQ Plone Site

Create successful ePaper yourself

Delete template?

Save as template?