DOCSLIB.ORG

Intime Software 4.0 User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Intime Software 4.0 User's Guide USER’ S MANUAL INtime® 4.0 Software TenAsys Corporation 1400 NW Compton Drive, Suite 301 Beaverton, OR 97006 USA +1 503 748-4720 FAX: +1 503 748-4730 31001-6 [email protected] September 2009 www.tenasys.com September 2009 Copyright © 2009 by TenAsys Corporation. All rights reserved. INtime, iRMX, and TenAsys are registered trademarks of TenAsys Corporation. † All other trademarks, registered trademarks, service marks, and trade names are the property of their respective owners. Before you begin This guide describes INtime® software, both as an extension for Microsoft Windows or as a stand-alone RTOS (Real Time Operating System) running on an Intel architecture PC, that provides the tools you need to create and run real-time (RT) applications— robust, high-performance applications with predictable responses to external events. This guide assumes that you know how to develop programs for Windows and understand RT system concepts. Note In this guide, the term “Windows” means any supported version of Windows. For a complete listing of supported Windows versions, see page 3. About this guide Guide contents This guide introduces you to INtime software: how it makes RT applications possible and how to use the INtime development tools. Use this guide to get acquainted with INtime software, then refer to INtime Help for detailed information about INtime components. For more information about accessing help, see Where to get more information later in this chapter. Note For a quick start, read the following: • Chapter 1, Overview to introduce you to all the basic INtime software concepts and to learn where to find detailed information about INtime software. • Chapter 10, INtime application development, to learn about developing RT applications using INtime software. iii INtime 4.0 Software Part I: Introducing INtime software This part introduces INtime software and explains how INtime software and Windows work together to create RT applications. Chapter Description 1 Overview Describes how INtime software works together with Windows to create and run RT applications, and lists INtime software’s features. It also tells you where to find detailed information about INtime software topics. 2 Understanding INtime Explains how INtime’s RT kernel works with Windows to provide software architecture RT functionality. It also lists and describes INtime components. 3 About INtime software’s Describes the RT kernel and its objects, the basic building blocks RT kernel that application programs manipulate. 4 About RT programming Describes processes unique to RT programming. 5 Designing RT applications Provides general guidelines for RT system design. Part II: Using INtime software This part explains how to start INtime software and how to use the INtime software development tools. Chapter Description 6 Installation Explains how to install and uninstall INtime software. 7 Configuration Describes how to configure INtime software. 8 Connecting to an INtime Explains how to set up an NTX connection to an INtime host or a host runtime system for remote debugging. 9 Operation Describes how to start and run INtime software. Part III: Appendices The appendices provide additional information about INtime software. Appendix Description A INtime software Lists and describes system calls that threads in the RT portion of system calls INtime applications use to communicate with each other and with Windows threads. You can find detailed information, including syntax and parameter values, in INtime Help. B The iwin32 subsystem Describes the iwin32 subsystem, which provides a Win32 API for the INtime kernel. It is a parallel API to the INtime API that makes porting of existing Win32 applications easier. C INtime directory structure Describes the INtime directory structure. D INtime software Lists and describes INtime software program files. components iv Before you begin Appendix Description E Visual Studio debugging for Describes how to upgrade existing INtime projects to use the older INtime projects Visual Studio product and its debugger. F Adding INtime software Lists and describes how to add INtime components to a Windows to an XP Embedded XP Embedded development environment so you can produce XP configuration Embedded images that include these INtime components. G Troubleshooting Lists problems you may encounter while running INtime software, and explains how to avoid or resolve those problems. Glossary The glossary defines terms used to describe INtime software. Notational conventions This manual uses the following conventions: • All numbers are decimal unless otherwise stated. • Bit 0 is the low-order bit. If a bit is set to 1, the associated description is true unless otherwise stated. • Data structures and syntax strings appear in this font. Note Indicates important information about the product. Indicates alternate techniques or procedures that you can use to save time Tip or better understand the product. Indicates potentially hazardous situations which, if not avoided, may result CAUTION in minor or moderate injury, or damage to data or hardware. It may also alert you about unsafe practices. Where to get more information About INtime software You can find out more about INtime software from these sources: • World Wide Web: TenAsys maintains an active site on the World Wide Web. The site contains current information about the company and locations of sales offices, new and existing products, contacts for sales, service, and technical support information. You can also send e-mail to TenAsys using the web site: www.tenasys.com You can contact TenAsys by email: [email protected] You can contact TenAsys technical support by email: v INtime 4.0 Software [email protected] Note When sending e-mail for technical support, please include information about both the hardware and software, including Windows and INtime versions, plus a detailed description of the problem, including how to reproduce it. Requests for sales, service, and technical support information receive prompt response. • INtime Help: Describes INtime software concepts and explains how to use INtime tools. INtime Help includes all system calls, including their syntax which you can cut and paste directly into your code. To access Intime Help, do one of these: • Within Microsoft Visual Studio: INtime content is integrated with the Visual Studio help collections. INtime content may be filtered with the keyword “INtime”. • Within source code: Highlight a system call in your source code, then press F1. Help for that system call displays. • Readme file: Lists features and issues that arose too late to include in other documentation. • Other: If you purchased your TenAsys product from a third-party vendor, you can contact that vendor for service and support. About Windows For more information about Windows operation and program development, see these documents: • Documentation that came with Windows. • Documentation that came with Microsoft Visual Studio. vi Contents Part I Introducing INtime software Chapter 1 Overview How does INtime software work? ........................................................................................ 3 Running an INtime application in conjunction with Windows ................................. 4 Communication between Windows and RT threads ............................................ 4 Considerations for INtime applications running on a single processor PC ......... 5 Considerations for INtime applications running on a multiprocessor PC ........... 6 Developing an INtime application ....................................................................................... 7 Design considerations.................................................................................................... 7 Code development......................................................................................................... 7 Features ................................................................................................................................. 8 Development environment............................................................................................ 8 Wizards ................................................................................................................... 8 Libraries .................................................................................................................. 9 Debuggers................................................................................................................ 9 Sample applications............................................................................................... 10 Runtime environment ................................................................................................... 12 RT enhancements to Windows .............................................................................. 12 Memory protection................................................................................................. 12 “Blue screen” protection........................................................................................ 13 Chapter 2 Understanding INtime software architecture Terminology .......................................................................................................................... 15 How INtime software and Windows work together to run RT applications ...................... 16 Transport mechanisms .................................................................................................. 17 About the OSEM....................................................................................................
Load more

Recommended publications
  • What Is an Operating System III 2.1 Compnents II an Operating System
    Page 1 of 6 What is an Operating System III 2.1 Compnents II An operating system (OS) is software that manages computer hardware and software resources and provides common services for computer programs. The operating system is an essential component of the system software in a computer system. Application programs usually require an operating system to function. Memory management Among other things, a multiprogramming operating system kernel must be responsible for managing all system memory which is currently in use by programs. This ensures that a program does not interfere with memory already in use by another program. Since programs time share, each program must have independent access to memory. Cooperative memory management, used by many early operating systems, assumes that all programs make voluntary use of the kernel's memory manager, and do not exceed their allocated memory. This system of memory management is almost never seen any more, since programs often contain bugs which can cause them to exceed their allocated memory. If a program fails, it may cause memory used by one or more other programs to be affected or overwritten. Malicious programs or viruses may purposefully alter another program's memory, or may affect the operation of the operating system itself. With cooperative memory management, it takes only one misbehaved program to crash the system. Memory protection enables the kernel to limit a process' access to the computer's memory. Various methods of memory protection exist, including memory segmentation and paging. All methods require some level of hardware support (such as the 80286 MMU), which doesn't exist in all computers.
    [Show full text]
  • Irmx® 286/Irmx® II Troubleshooting Guide
    iRMX® 286/iRMX® II Troubleshooting Guide Q1/1990 Order Number: 273472-001 inter iRMX® 286/iRMX® II Troubleshooting Guide Q1/1990 Order Number: 273472-001 Intel Corporation 2402 W. Beardsley Road Phoenix, Arizona Mailstop DV2-42 Intel Corporation (UK) Ltd. Pipers Way Swindon, Wiltshire SN3 1 RJ United Kingdom Intel Japan KK 5-6 Tokodai, Toyosato-machi Tsukuba-gun Ibaragi-Pref. 300-26 An Intel Technical Report from Technical Support Operations Copyright ©1990, Intel Corporation Copyright ©1990, Intel Corporation The information in this document is subject to change without notice. Intel Corporation makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Intel Corporation assumes no responsibility for any errors that ~ay :!ppe3r in this d~ur:::ent. Intel Corpomtion make:; nc ccmmitmcut tv update nor to keep C"l..iiTeilt thc information contained in this document. Intel Corporation assUmes no responsibility for the use of any circuitry other than circuitry embodied in an Intel product. No other circuit patent licenses are implied. Intel software products are copyrighted by and shall remain the property of Intel Corporation. Use, duplication or disclosure is subject to restrictions stated in Intel's software license, or as defined in FAR 52.227-7013. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of Intel Corporation. The following are trademarks of Intel Corporation
    [Show full text]
  • Oracle VM Virtualbox User Manual
    Oracle VM VirtualBox R User Manual Version 5.0.16 c 2004-2016 Oracle Corporation http://www.virtualbox.org Contents 1 First steps 11 1.1 Why is virtualization useful?............................. 12 1.2 Some terminology................................... 12 1.3 Features overview................................... 13 1.4 Supported host operating systems.......................... 15 1.5 Installing VirtualBox and extension packs...................... 16 1.6 Starting VirtualBox.................................. 17 1.7 Creating your first virtual machine......................... 18 1.8 Running your virtual machine............................ 21 1.8.1 Starting a new VM for the first time.................... 21 1.8.2 Capturing and releasing keyboard and mouse.............. 22 1.8.3 Typing special characters.......................... 23 1.8.4 Changing removable media......................... 24 1.8.5 Resizing the machine’s window...................... 24 1.8.6 Saving the state of the machine...................... 25 1.9 Using VM groups................................... 26 1.10 Snapshots....................................... 26 1.10.1 Taking, restoring and deleting snapshots................. 27 1.10.2 Snapshot contents.............................. 28 1.11 Virtual machine configuration............................ 29 1.12 Removing virtual machines.............................. 30 1.13 Cloning virtual machines............................... 30 1.14 Importing and exporting virtual machines..................... 31 1.15 Global Settings...................................
    [Show full text]
  • CS 151: Introduction to Computers
    Information Technology: Introduction to Computers Handout One Computer Hardware 1. Components a. System board, Main board, Motherboard b. Central Processing Unit (CPU) c. RAM (Random Access Memory) SDRAM. DDR-RAM, RAMBUS d. Expansion cards i. ISA - Industry Standard Architecture ii. PCI - Peripheral Component Interconnect iii. PCMCIA - Personal Computer Memory Card International Association iv. AGP – Accelerated Graphics Port e. Sound f. Network Interface Card (NIC) g. Modem h. Graphics Card (AGP – accelerated graphics port) i. Disk drives (A:\ floppy diskette; B:\ obsolete 5.25” floppy diskette; C:\Internal Hard Disk; D:\CD-ROM, CD-R/RW, DVD-ROM/R/RW (Compact Disk-Read Only Memory) 2. Peripherals a. Monitor b. Printer c. Keyboard d. Mouse e. Joystick f. Scanner g. Web cam Operating system – a collection of files and small programs that enables input and output. The operating system transforms the computer into a productive entity for human use. BIOS (Basic Input Output System) date, time, language, DOS – Disk Operating System Windows (Dual, parallel development for home and industry) Windows 3.1 Windows 3.11 (Windows for Workgroups) Windows 95 Windows N. T. (Network Technology) Windows 98 Windows N. T. 4.0 Windows Me Windows 2000 Windows XP Home Windows XP Professional The Evolution of Windows Early 80's IBM introduced the Personal PC using the Intel 8088 processor and Microsoft's Disk Operating System (DOS). This was a scaled down computer aimed at business which allowed a single user to execute a single program. Many changes have been introduced over the last 20 years to bring us to where we are now.
    [Show full text]
  • Vista Wait Cursor Gif
    Vista Wait Cursor Gif 1 / 4 Vista Wait Cursor Gif 2 / 4 3 / 4 С Vista Transformation Pack можете да промените изгледа на Windows XP и да го направите като Windows Vista. Пакета ... vista transformation pack .gif С Vista ... Updated Vista Rainbar's launcher for constant waiting cursor activity issue. On October 31, 2013, claimed that the 's counterpart, a, was more recognized than Windows Vista's wait cursor due to the cultural impact that .... So the blue circle animation that pops up next to the mouse pointer that shows ... and closing running programs in the tray, and the waiting animation ... a problem by performing a clean boot in Windows Vista or in Windows 7.. In your jQuery use: $("body").css("cursor", "progress");. and then back to normal again $("body").css("cursor", "default");.. N. ▻ Non- animated throbbers‎ (1 C, 3 F) ... Ajax loader metal 512.gif 512 × 512; 45 KB ... Cursor Windows Vista.gif 32 × 32; 9 KB ... Wait.gif 40 × 40; 4 KB.. Download GIF Viewer for free. Windows 7/8/10-compatible animated .gif player. A C# program used to visualize and extract frames from .GIF files. (you need .. In this topic you'll learn more about static and animated cursors. ... in different context (Normal Select, Help Select, Working in background, Busy. ... colors, smooth transparency (alpha channel) - Supported by Windows XP, Vista and superior only ... which can be saved using various file formats (BMP, PSD, GIF, JPEG, WMF.. Windows Vista's "busy" cursor? Reply ... This always makes me forget my troubles. http://upload.wikimedia.org/wikipedia/en/3/3d/WaitCursor-300p.gif.
    [Show full text]
  • BCIS 1305 Business Computer Applications
    BCIS 1305 Business Computer Applications BCIS 1305 Business Computer Applications San Jacinto College This course was developed from generally available open educational resources (OER) in use at multiple institutions, drawing mostly from a primary work curated by the Extended Learning Institute (ELI) at Northern Virginia Community College (NOVA), but also including additional open works from various sources as noted in attributions on each page of materials. Cover Image: “Keyboard” by John Ward from https://flic.kr/p/tFuRZ licensed under a Creative Commons Attribution License. BCIS 1305 Business Computer Applications by Extended Learning Institute (ELI) at NOVA is licensed under a Creative Commons Attribution 4.0 International License, except where otherwise noted. CONTENTS Module 1: Introduction to Computers ..........................................................................................1 • Reading: File systems ....................................................................................................................................... 1 • Reading: Basic Computer Skills ........................................................................................................................ 1 • Reading: Computer Concepts ........................................................................................................................... 1 • Tutorials: Computer Basics................................................................................................................................ 1 Module 2: Computer
    [Show full text]
  • How Can I Test My Memory
    How can I test my memory A defective memory module(s) can cause various issues on your computer. These are just a few of the possible issues you may encounter. It is important to remember the issues below can also be caused by more than just defective memory. 1. Computer doesn't boot and/or you get a beep code. Check your motherboard manual for the error code if you are unsure what it means. 2. Random computer crashes including BSOD (Blue Screen of Death), General Protection Fault error messages, Illegal Operations, Fatal Exceptions, etc. 3. Random Reboots. 4. OS or other application installation failure. How can we be sure that the memory is defective before starting the RMA exchange process? There are programs available that are designed to test the computer's memory. We recommend Memtest86+ to test your computer's memory. Please visit this link to download and install Memtest86+ for an ISO image or USB Drive: Link To make a bootable Floppy from with in Windows, First you would download the memtest utility to your HDD, then using www.winzip.com extract it to the same directory. Please then get a floppy and do a fresh full format on it, and if there are any bad sectors just throw it away and get a new one. Then click on the install.bat file in the directory where you downloaded and extracted the files and follow the on screen prompts. To make a Bootable CD from within windows you would download the ISO image that has a .zip extension.
    [Show full text]
  • CS5460/6460: Operating Systems Lecture 6: Interrupts and Exceptions
    CS5460/6460: Operating Systems Lecture 6: Interrupts and Exceptions Several slides in this lecture use slides developed by Don Porter Anton Burtsev January, 2014 Why do we need interrupts? Remember: hardware interface is designed to help OS Why do we need interrupts? ● Fix an abnormal condition ● Page not mapped in memory ● Notifications from external devices ● Network packet received ● Preemptive scheduling ● Timer interrupt ● Secure interface between OS and applications ● System calls Two types Synchronous ● Exceptions – react to an abnormal condition ● Map the swapped out page back to memory ● Invoke a system call ● Intel distinguishes 3 types: faults, traps, aborts Asynchronous ● Interrupts – preempt normal execution ● Notify that something has happened (new packet, disk I/O completed, timer tick, notification from another CPU) Handling interrupts and exceptions ● Same procedure ● Stop execution of the current program ● Start execution of a handler ● Processor accesses the handler through an entry in the Interrupt Descriptor Table (IDT) ● Each interrupt is defined by a number ● E.g., 14 is pagefault, 3 debug ● This number is an index into the interrupt table (IDT) CPU Memory Interrupt descriptor Interrupt descriptor Interrupt descriptor ● Interrupt gate disables interrupts ● Clears the IF flag in EFLAGS register ● Trap gate doesn't ● IF flag is unchanged x86 interrupt table Device IRQs 128 = Linux System Call … … … 0 31 47 255 Software Configurable Reserved for the CPU Interrupts ● Each type of interrupt is assigned an index from
    [Show full text]
  • HP Remote Graphics Software
    Sales brief HP Remote Graphics Software Release notes This document comprises the release notes for HP Remote Graphics Software (HP RGS). Topics covered in this document include the following: • New features • Known issues • Security issues What’s new in Release 7.4 HP RGS 7.4 Sender supports Windows – The Linux® RGS Receiver Package contains 2. RHEL 7.4 requires an update to GDM to and Linux®. HP RGS 7.4 Receiver supports two separate installers: avoid a problem where the login screen does not return after a logout. See Ret Hat Windows, Linux®, and macOS™. – Receiver for RHEL 6.x Bugzilla bug 1469755. New features: – Receiver for RHEL 7.x and SUSE 12 3. On Linux® Receiver, the SETUP MODE 1. Floating License Server: The FLEXnet – The Linux® RGS Sender and Receiver sequence + H that is used to hide or unhide license server for floating licenses must Package contains the two Receiver the toolbar does not always work as be version 11.14 or later to support RGS installers listed above plus installers for: expected. This behavior is planned to be 7.4. Local licenses are not affected. The fixed in an upcoming release. - Sender for RHEL 6.x FLEXnet license server is included with the - Sender for RHEL 7.x and SUSE 12 HP RGS package. See the Licensing Guide at - Sender for SLED 11 hp.com/go/RGS for more information. What’s new in Release 7.3.3 2. Operating System Notes: Windows – RHEL 7.4 and SLED 12 SP3 are now HP RGS Release 7.3.3 is a release for Windows – Windows 10 Fall Creators Update is now supported and Linux® Senders and Receivers and the supported macOSTM Receiver.
    [Show full text]
  • Bluescreen 1St Edition Free
    BLUESCREEN 1ST EDITION FREE Author: Dan Wells ISBN: 9780062347886 Download Link: CLICK HERE How to fix the blue screen of death error in Windows 10 Schweiz - Deutsch. Retrieved 9 September Depending on the OS version, there may be several formats this can be saved in, ranging from a 64kB "minidump" introduced in Windows to a "complete dump" which is effectively a copy of the entire contents of physical memory RAM. It can occur as a result of a faulty update Bluescreen 1st edition due to spontaneous hardware failures. Remove everything you are not using, especially older applications. South Africa - English. Windows 10 gets new refresh rate feature, Start Menu search tweaks. You will then be offered Bluescreen 1st edition options for checking system files. Wikimedia Commons. However, this page is only of limited use. Were you viewing a video or were you in the middle of a video conference? To do this, shut down your PC and press F8 while restarting it. Windows blue screen (BSOD): How to cure the error A blue screen of death BSOD on windows 10 is an error that almost every Windows 10 user has experienced sometimes or the other. In some cases it tells you the exact error that has occurred. Developers are exploring Android support for Lumia phones April 10, Crna Gora - Srpski. Spinning pinwheel Windows wait cursor. There are several ways to solve Bluescreen 1st edition. For a short time, you see a blue screen with some information pop up. From Wikipedia, the free encyclopedia. The hexadecimal error code and parameters can still be found in the Windows Event Log or in memory dumps.
    [Show full text]
  • Crimson User Manual
    LP0577 CRIMSON 2 USER MANUAL Copyright © 2003-2006 Red Lion Controls. All Rights Reserved Worldwide. The information contained herein is provided in good faith, but is subject to change without notice. It is supplied with no warranty whatsoever, and does not represent a commitment on the part of Red Lion Controls. Companies, names and data used as examples herein are fictitious unless otherwise stated. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without the express written permission of Red Lion Controls All trademarks are acknowledged as the property of their respective owners. Written by Mike Granby and Jesse Benefiel. TABLE OF CONTENTS TABLE OF CONTENTS GETTING STARTED ........................................................................................... 1 SYSTEM REQUIREMENTS ..................................................................................... 1 INSTALLING THE SOFTWARE................................................................................. 1 CHECKING FOR UPDATES..................................................................................... 1 INSTALLING THE USB DRIVERS ............................................................................ 2 CRIMSON BASICS............................................................................................. 3 MAIN SCREEN ICONS ......................................................................................... 3 COMMUNICATIONS............................................................................................................................3
    [Show full text]
  • CS152: Computer Systems Architecture Virtual Memory
    CS152: Computer Systems Architecture Virtual Memory Sang-Woo Jun Winter 2019 Large amount of material adapted from MIT 6.004, “Computation Structures”, Morgan Kaufmann “Computer Organization and Design: The Hardware/Software Interface: RISC-V Edition”, and CS 152 Slides by Isaac Scherson So far… Operating System goals: o Protection and privacy: Processes cannot access each other’s data o Abstraction: OS hides details of underlying hardware • e.g., processes open and access files instead of issuing raw commands to disk o Resource management: OS controls how processes share hardware resources (CPU, memory, disk, etc.) Key enabling technologies: o User mode + supervisor mode w/ privileged instructions o Exceptions to safely transition into supervisor mode o Virtual memory to provide private address spaces and abstract the machine’s storage resources (today!) Remember context switching All running processes still share the same memory space o Does not support isolation between processes o e.g., If process 1 uses too much stack space, it will overrun process 2’s stack space o e.g., If process 1 maliciously writes to random address regions, it can overwrite process 2’s stack space Stack Stack Stack Timer Jump to Process 1 Process 1 Process 1 Stack pointer interrupt Proc1’s register values process 2 Proc1’s register values Stack pointer Process 2 Process 2 Proc2’s register values Stack pointer Isolation solution: Virtual Memory Illusion of a large, private, uniform store Virtual address o Address generated by a process (given to LW, SW,
    [Show full text]