INtimeÂ® 3.1 Software - tenAsys

More documents

Recommendations

Info

INtime <strong>3.1</strong> <strong>Software</strong> The kernel's RT clock is a counter that the kernel uses to keep track of the number of kernel clock ticks that have occurred. When the kernel is initialized, the count is set to 0 (zero). The period of a kernel clock tick is configurable via the INtime Configuration utility and you can read the current configuration using CopyRtSystemInfo. Low-level calls System call knCreateRtAlarmEvent knWaitForRtAlarmEvent knResetRtAlarmEvent knDeleteRtAlarmEvent knGetKernelTime knSetKernelTime Description Creates an alarm event object which is triggered by an alarm. Waits at an alarm object for the given time interval, or until the alarm triggers. Resets a one-shot alarm after it has triggered. Deletes an alarm event object and releases the memory used to store its state for reuse. Returns the value of the counter the kernel uses to tally the number of low-level ticks that have occurred. Sets the value of the counter that the kernel uses to tally the number of low-level ticks that have occurred. Structures Structure CONTROLBUFFER CPUFRAME EVENTINFO EXCEPTION FILETIME GENADDR HEAPINFO HWEXCEPTIONMSG INTERRUPTINFO KNTIME NTXEVENTINFO NTXPROCATTRIBS OBJECTDIR PCIDEV Description Tracks the progress of each message during its life in the service. N/A Returns notifications about system state, sponsor processes, dependent processes, and shutdown notifications. N/A Provides the file system time stamp. Provides port addresses which fully differentiate ports within a particular service. N/A Specifies the format for data sent to the HW_FAULT_MBX data mailbox. N/A The kernel stores and reads the time value. Returns notifications about system state, sponsor processes, and dependent processes. Specifies memory usage fields the RT Application Loader. N/A Passes parameters to library calls and to return values from the PCI configuration space. 128
Appendix A: INtime software system calls Structure POOLINFO PORTINFO RECEIVEINFO SECURITY_ATTRIBUTES SERVICEATTRIBUTES SERVICEDESC SYSINFO THREADACCOUNTING THREADINFO_SNAPSHOT THREADSTATE_SNAPSHOT TRANSACTION urb usbClient usbConfigDescriptor usbCtrlRequest usbDeviceDescriptor usbDeviceId usbEndPointDescriptor usbInterface usbInterfaceDescriptor Description N/A N/A Provides information about received messages to the thread or returns information about the operation just completed. Contains the security descriptor for an object and specifies whether the handle retrieved by specifying this structure is inheritable. The header for every structure passed to GetRtServiceAttributes and SetRtServiceAttributes. Contains all configuration information needed to run the service. Contains information about the current RT machine configuration. N/A N/A N/A Tracks many operations through the service. For example: a simple send, a send-RSVP or certain receive operations. The USB Request Block structure, which identifies USB transfer requests. Identifies the USB client to the USB subsystem. The USB-defined configuration descriptor, plus some implementation-specific fields that link to the configuration interfaces. Defines a device control request. The USB-defined device descriptor; there is one descriptor per device. Identifies USB devices and interfaces for hotplugging and enumeration purposes. The USB-defined endpoint descriptor. The USB subsystem copies all endpoint descriptors from the device. References the alternate settings for a given interface. This structure is referenced from the usbConfigDescriptor structure. The USB-defined interface descriptor. The USB subsystem copies all interface descriptors from the device. INscope calls 129
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 and 130: Appendix A: INtime software system
Page 143: 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 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?