INtimeÂ® 3.1 Software - tenAsys

More documents

Recommendations

Info

INtime 3.1 Software RT calls You use these calls when developing the real-time portion of an INtime application. High-level (validating) calls High-level calls provide higher protection and validation features. Memory is allocated automatically from the process’s pool. Each high level object consumes a slot from the system GDT (8000 objects maximum) High-level system calls validate a call’s parameters; a condition code returned by the call indicates whether you used invalid parameters. Condition codes for trying to read or write memory to which you have no access also exist. High-level exchange objects validate parameters and are protected against unexpected deletion. High-level calls exist for these exchange objects: • Object and data mailboxes • Counting semaphores • Regions (for mutual exclusion with priority inversion protection) Low-level (non-validating) calls Low-level calls provide higher performance, but lower protection and validation features. Low-level objects provide functionality beyond that of high-level objects. You must allocate memory for low-level objects and may allocate memory beyond lowlevel object needs. You can use this additional memory to store application-specific state information associated with the object. Low-level objects are not protected against unexpected deletion and do not validate parameters (if you need parameter validation, use high-level system calls). Low-level calls use the flat, 4 Gbyte addressing capabilities of the microprocessor. They do not use segmentation. Therefore, they do not consume a slot from the system GDT. Use low-level objects in these situations: • For isolated parts of the application, such as signaling ordinary threads from an interrupt handler. • When performance is critical, such as high-performance, unvalidated sending and receiving of data mailbox messages and semaphore units. Note System calls that manipulate low-level objects assume that all memory reference pointers received are valid. 114
Appendix A: INtime software system calls Low-level calls exist for these exchange objects: • Data mailboxes • Single-unit semaphores • Region semaphores (with priority inversion protection) • Software alarm events (virtual timers) that invoke alarm event threads that you write. RT services Real-time services include: • RT service calls: An INtime real-time application (RTA) which processes messages from a user and events from an interface. A service is defined by the set of messages and the actions provoked by those messages. Each interface is associated with a service descriptor. • RT service handlers: Subroutines invoked by the kernel to perform servicedependent functions of the system calls. RT system calls Distributed System Management (DSM) NTX calls System call ntxRegisterRtDependency ntxUnregisterDependency ntxRegisterSponsor ntxUnregisterSponsor ntxNotifyEvent Description Registers a dependency Unregisters a dependency Registers a sponsor Unregisters a sponsor Notifies of an event High-level calls System call RegisterRtDependency UnregisterRtDependency RegisterRtSponsor UnregisterRtSponsor RtNotifyEvent Description Registers a dependency Unregisters a dependency Registers a sponsor Unregisters a sponsor Notifies of an event 115
Page 1 and 2:
U S E R ’ S M A N U A L INtime ®
Page 3 and 4:
Before you begin This guide describ
Page 5 and 6:
Before you begin Glossary Notationa
Page 7 and 8:
Before you begin • Within source
Page 9 and 10:
Contents Part I Chapter 1 Chapter 2
Page 11 and 12:
Contents Part II Chapter 6 Chapter
Page 13 and 14:
Contents Part III Appendix A Append
Page 15 and 16:
Contents NTX DLLs..................
Page 17 and 18:
I Introducing INtime software This
Page 19 and 20:
1 Overview INtime software extends
Page 21 and 22:
Chapter 1: Overview Considerations
Page 23 and 24:
Chapter 1: Overview Developing an I
Page 25 and 26:
Chapter 1: Overview INtime software
Page 27 and 28:
Chapter 1: Overview • INtime Grap
Page 29 and 30:
Chapter 1: Overview • Remote conf
Page 31 and 32:
2 Understanding INtime software arc
Page 33 and 34:
Chapter 2: Understanding INtime sof
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
3 About INtime software’s RT kern
Page 47 and 48:
Chapter 3: About INtime software’
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
4 About RT programming This chapter
Page 57 and 58:
Chapter 4: About RT programming Pre
Page 59 and 60:
Chapter 4: About RT programming whe
Page 61 and 62:
Chapter 4: About RT programming Fig
Page 63 and 64:
Chapter 4: About RT programming Syn
Page 65 and 66:
Chapter 4: About RT programming The
Page 67 and 68:
Chapter 4: About RT programming Exc
Page 69 and 70:
Chapter 4: About RT programming Str
Page 71 and 72:
5 Designing RT applications This ch
Page 73 and 74:
Chapter 5: Designing RT application
Page 75 and 76:
Chapter 5: Designing RT application
Page 77 and 78:
II Using INtime software This part
Page 79 and 80: 6 Installation This chapter explain
Page 81 and 82: Chapter 6: Installation 5. Select o
Page 83 and 84: 7 Configuration INtime software pro
Page 85 and 86: Chapter 7: Configuration Tab Local
Page 87 and 88: Chapter 7: Configuration Configurin
Page 89 and 90: Chapter 7: Configuration Setting th
Page 91 and 92: 8 Preparing an RT node This chapter
Page 93 and 94: Chapter 8: Preparing an RT node Bui
Page 95 and 96: Chapter 8: Preparing an RT node 4.
Page 97 and 98: Chapter 8: Preparing an RT node Fir
Page 99 and 100: 9 Operation This chapter describes
Page 101 and 102: Chapter 9: Operation • INtime too
Page 103 and 104: 10 INtime application development T
Page 105 and 106: Chapter 10: INtime application deve
Page 125 and 126: III Appendices The appendices inclu
Page 127 and 128: A INtime software system calls This
Page 129: Appendix A: INtime software system
Page 133 and 134: Appendix A: INtime software system
Page 157 and 158: B The iwin32 subsystem This appendi
Page 159 and 160: Appendix B: The iwin32 subsystem A
Page 161 and 162: Appendix B: The iwin32 subsystem Mu
Page 163 and 164: Appendix B: The iwin32 subsystem Sh
Page 165 and 166: Appendix B: The iwin32 subsystem Us
Page 167 and 168: Appendix B: The iwin32 subsystem Pr
Page 169 and 170: C INtime directory structure This a
Page 171 and 172: D INtime software components This a
Page 173 and 174: Appendix D: INtime software compone
Page 181 and 182:
Appendix D: INtime software compone
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
E Visual Studio .NET debugging for
Page 191 and 192:
Appendix E: Visual Studio .NET debu
Page 193 and 194:
F Adding INtime software to an XP E
Page 195 and 196:
G Troubleshooting This appendix lis
Page 197 and 198:
Appendix G: Troubleshooting Table G
Page 199 and 200:
Appendix G: Troubleshooting Table G
Page 201 and 202:
Glossary application loader asynchr
Page 203 and 204:
Glossary memory area memory pool me
Page 205 and 206:
Index A B C D E F G H I J K L M N O
Page 207 and 208:
A B C D E F G H I J K L M N O P Q R
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
show all

INtimeÂ® 3.1 Software - tenAsys

Create successful ePaper yourself

Delete template?

Save as template?