1
st
Edition 4-4
System Software Setup
Software requirements for application development and/or PowerPact6 operational checks are as follows:
• Application Development Software (Tornado 2, LynxOS) – provides application development
tools
• Board Support Package (BSP) - installed as a supplement to the Application Development
Software, the BSP provides specific support for the PowerPact6 family
• Terminal Emulator (HyperTerminal, Kermit, Tip, Cu etc.) or stand-alone terminal
• An FTP, TFTP or RSH server - provides target system access to host resident files
$
Note: Some of these software development packages may be incorporated into the application software
distribution or the host operating system, e.g. Tornado 2 includes terminal emulator and FTP server
software.
Once installed, terminal emulator and (T)FTP/RSH software must be configured.
Terminal emulation software should be set to communicate with the appropriate serial port as follows:
Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
Since the COM port is Tx/Rx only, turn off any handshaking options on the terminal/terminal emulation
software.
(T)FTP/RSH settings should allow sufficient target system access to host system directories/files.
Installation and configuration of the host software should be completed before operation of the target
system. For detailed installation and configuration instructions refer to the relevant software package
documentation.
Network Settings
The network may use Domain Name Service (DNS), Dynamic Host Configuration Protocol (DHCP),
Windows Internet Name Service (WINS), Boot Protocol (BOOTP), Reverse Address Resolution
Protocol (RARP), Sub-networks and Gateways. The development system can be configured to use any or
all of these protocols.
£RECOMMENDATION
In a DHCP-enabled network, allocate fixed IP addresses to host and target systems, at least
initially.
Network information and problem diagnosis may be carried out from the host system using standard OS
commands ipconfig, ifconfig, ping, etc.
For relevant system IP addresses and protocol details, consult your system administrator or refer to
suitable development environment documentation.