Installation of the SDK and of the INtime Distributed RTOS is performed using the same CD medium. There is also an alternate installation of the INtime Distributed RTOS component using a USB drive.

Platform Requirements

The development kit should be installed on a Windows PC system, version Windows 7 or later versions of Windows including Windows 7, 8 and 10, 32- and 64-bit platforms, and Windows Server equivalents. A multi-core CPU is recommended for an INtime for Windows installation. A multi-core CPU is required to run INtime for Windows on Windows 8, or on any 64-bit version of Windows. Windows must be booted using the WIndows bootloader. A dual-boot system where Windows is loaded using a third-party bootloader will not run INtime successfully.

Support for Windows XP and Vista has been deprecated from INtime version 6.4 onwards.

If using WIndows 10 version 1703 or later, Secure Boot must be disabled. The requirements of Secure Boot are not Compatible with the requirements for INtime for Windows.

The INtime Distributed RTOS target system must be installed on a PC platform capable of booting from CD drive or USB media, with IDE or SATA interface and a drive attached to that controller. A keyboard is required for installation; both PS/2 and USB types are supported. The CPU must include an APIC interrupt controller and the BIOS must advertise the fact. INtime Distributed RTOS does not run using the legacy 8259 PIC.

A supported network card is required for connection to the Windows development system. Supported cards are listed at this location:

http://www.tenasys.com/index.php/support-home/knowledge-base?page=4

SDK Installation

The INtime SDK supports both INtime for Windows and INtime Distributed RTOS configurations.

In the INtime for Windows configuration, the INtime user’s application runs on the same platform as the development tools while with the INtime Distributed RTOS configuration, the developments tools are run on a separate platform.

The INtime for Windows configuration is designed to support an end product that has an INtime application working in conjunction with an Windows application on the same platform. For this reason installation of INtime for Windows configuration includes the installation of an INtime Node (INtime RTOS and application) on the same platform as the INtime SDK as shown in figure below. The resultant output of that environment is to have both the user’s Windows and the INtime application running on the same platform.

Partitioning of the Windows and INtime environments is described in the Configuration section.

INtime for Windows development environment configuration with the Windows and INtime components running on the same platform.

The INtime Distributed RTOS configuration is designed to support an end product that has an INtime application working on a platform by itself. For this reason the default installation of INtime Distributed RTOS configuration does not include the installation of an INtime Node (INtime RTOS and application) on the same platform as the INtime SDK. The resultant development environment looks as shown in the figure below, with the SDK running on a Windows platform and the INtime user application running on a separate platform, the target platform. The resultant output of that environment is to have an INtime application running stand-alone on a target platform that is running an INtime Node.

INtime Distributed RTOS development setup running on separate platforms connected by Ethernet.

Note that the INtime for Windows and INtime Distributed RTOS development environments are identical except for the INtime Distributed RTOS having the Windows and the INtime components running on separate platforms connected via Ethernet. Because of those similarities it is possible to develop stand-alone INtime application with an INtime for Windows configuration setup and then move the application to target platform.

SDK Installation Procedure

The procedure below describes installation of the INtime development tools and kernel on your development machine. Make sure that your development machine meets the requirements listed in the Platform Requirements section above.

Insert the INtime CD-ROM. If AutoRun is enabled a welcome dialog appears. If AutoRun has been disabled you can start the installation procedure by double-clicking the file named launch.exe in the root directory of the INtime CD-ROM. The installation procedure is similar to that of most standard Windows applications. You will be asked to accept the INtime software license agreement and to supply one or more registration keys to complete the installation procedure.

A default destination folder of %PROGRAMFILES%\INtime (typically C:\Program Files\INtime) is suggested by the installation program for the INtime development tools and sample files. Make note of this directory so you can locate it again if you wish to inspect header files and other INtime system files. Sample projects will be installed in the user directory of the user who installed INtime. Configuration files will be installed in the %INTIMECFG% directory.

Two basic install options are provided:

• Development Tools Only
  This option will only install the SDK and no INtime for Windows runtime software. Use this option for setting up a development system for use with an INtime Distributed RTOS target only. The INtime Distributed RTOS components are installed.
• Development Tools & Local nodes.
  This option installs the SDK and the components required to configure and run local INtime for Windows nodes. Use this option for developing applications for INtime for Windows. The INtime Distributed RTOS components are also installed with this option.

Locating your license keys

Depending on the product you purchased, you may be prompted for a combined development license code (CMBL). This license codes can be found on the license card that came with your software.

If you are installing a network licensed product you will be prompted to enter the IP address or fully-qualified domain name of the license server. Contact your company’s IT personnel for the license server information you will need to complete this licensing step.

After installation has completed you will be asked to reboot the system. If you have been provided a hardware key, insert it before rebooting. Once the system has rebooted you have the option of configuring the INtime runtime environment and services.

INtime Distributed RTOS target installation

The steps below describe the installation process to install INtime Distributed RTOS onto the target system.

The installation process assumes that the target system supports a CD drive and that the target system can be made to boot from the CD. Optional USB drive installation is also supported; it will require the target system to support booting from USB media.

Preparing a USB drive for installation

This optional step prepares a USB drive for installation of the INtime software on a target system. This method may be used if the CDROM medium is not available or if the software was delivered electronically. The USB drive will be formatted and the installation software installed on it.

• Insert the USB drive into the system where the SDK is installed. Use Windows Explorer to determine which drive letter has been assigned to the device.
• Navigate to the "%INTIME%rtos" folder and start the create_installstick.bat command file.

At the prompt, enter the driver letter of your USB drive:
Enter USB Drive letter:
eg, d:
--

• Enter the drive letter and press Enter. The drive will be formatted and the files copied to it. At the end you will see the prompt:

Press any key to continue ...

• Press Enter and remove the drive from the system
• Prepare the target system to boot from a USB device, insert the device and boot the system.

Booting from the product CDROM

You can use this method to install from the product CD which also contains the SDK installer.

Prepare the target system to boot from the CDROM. Insert the CDROM media and boot the system.

Installation of the INtime Distributed RTOS target system

On boot an automatic installation script will be invoked. It will ask a number of configuration questions and at each step you will be prompted to continue. If you choose not to continue, in general the previous step will be repeated.

1. Keyboard selection
   Select a keyboard type from the menu by entering its number and pressing Enter.
2. Disk selection
   A list of disk devices is displayed with their drive names. Select the drive you wish to install INtime software on.
3. Partitioning the disk
   
   Note: The following installation instructions assume you have an empty hard disk on which you will be installing the INtime RTOS. If your disk is already partitioned, you will have to either delete your existing partition in step 4 before you create a new partition or you will have to create a second partition and activate that partition for booting.
   A bootable partition must be created on the disk.
   1. From the initial menu, select option 2 to modify the partition table and then option 2 to create a partition.
   2. Type 1 to create partition 1. Choose option 2 to create a FAT32 partition.
   3. Enter the partition limits. Enter cylinder 0 for the start of the partition, then reading the information above the menu, select an ending cylinder number to create a partition of at least 100 Mbytes.
   4. Press Enter to return to the original menu
   5. Select option 3 to activate (make bootable) your partition and select your partition number (number 1 in the above example)
   6. Press Enter once more to return to the initial menu then Enter again to exit the utility, following the prompts to save your new partition table.
4. Format the partition
   Type 'y' to start the format utility then type 'yes' to start the format operation.
5. Install the files
   Type 'y' to unpack the INtime software files into your partition.
6. Set the default time zone
   Follow the prompts to select your time zone if the default does not apply.
7. Set time and date
   This step allows you to adjust the PC real-time clock (battery clock) depending on whether you wish the time to be kept in UTC or your local time zone. Most PCs keep their clock in local time, but you may choose to adjust this so that the battery clock keeps time in UTC (Universal Coordinated Time, or GMT).
8. Network configuration
   You will be given a list of interfaces detected by the installer. Choose the interface you wish to be the default system interface, which will be used to connect to your development system.
   1. DHCP – enter ‘y’ if you wish your network address to be assigned by your local DHCP server
   2. IP Address (if DHCP not selected). Enter an IPv4 address appropriate for your local network
   3. Netmask. Enter an appropriate netmask for your local network. Pressing ENTER will accept the suggested value, or you can enter a new value.
   4. Gateway. May be left blank, otherwise the address of the forwarding gateway for your local subnet.
   5. Type hostname; note the hostname should be a unique name that is recognizable among the devices on your network. Host name may contain only the ASCII letters 'a' through 'z' (in a case insensitive manner), the digits '0' through '9', and the characters ('-',’_’)
   6. Type Domain Name; may be left blank, or choose your local internet domain name, for example mydomain.com. Domain Name has the same character restrictions as hostname and use the '.' character to separate subdomain names.
   7. Type the domain name and DNS server. May be left blank, or give the name of your local domain and the IP address of a DNS server.
9. Tethering information
   Here you will enter the IP address or fully-qualified domain name for your development system. This is used to connect your target to the development system during development for the purposes of granting a license to the target. This connection is called "tethering" and is described in the next section below.
10. Set Administrator password
    This password is used to gain access to the web-based configuration utility on the target. You can enter a blank password if desired. If you enter a non-blank password you will be prompted to reenter it for confirmation purposes.
11. Reboot the system
    Remove the installation media and allow the system to reboot

Tethering the target to your development system

The INtime SDK comes with a license to run the development tools and local INtime for Windows nodes, and one additional license to run an INtime Distributed RTOS target system for development purposes. The license for the INtime Distributed RTOS system is granted by the development system by a process called "tethering". A periodic check is made that the target is connected to a licensed development system, and if that check fails the target system will shut itself down.

To activate the tethering, start the tethering server on the development system. Open a command window and type "tetherserver". Start the target system you just installed and during the boot process you will see the message "System TETHERED" which indicates a valid connection has been made. If tethering fails the system will shut down after 10 minutes.

Once you have configured your tethering you can install the tether server as a Windows service like this:

tetherserver -install

If you wish your target system to run without being tethered you will need to obtain a runtime license and activate the system.