![]() |
![]() |
![]() |
15.2 Customizing Your pRISM+ Environment
In this section you will learn about some of the advanced features of pRISM+. You will learn how to:
- install multiple pRISM+ versions (page 15-5)
- define your environment for a multiple-user configuration (page 15-7)
- develop in a mixed-platform environment (page 15-8)
- redefine your color settings (page 15-13)
- configure your pRISM+ help print options (page 15-13)
15.2.1 Multiple pRISM+ Installations
pRISM+ for pSOSystem allows you to have multiple pRISM+ installations on your PC and Workstation.
Multiple Installations In the Windows Environment
In this section you will learn how to install and use multiple pRISM+ installations in a Windows environment.
Installing Your Second pRISM+ Installation
During the installation, install your second pRISM+ installation in a different directory, for example:
C: \68K\isi68k\
C: \powerpc\isippc\
C: \PPC1_2_3\isippc\
The default installation directory is:
C: \isi$CPU_FAMILY\
where
$CPU_FAMILY
represents68k
,ARM
,mips
,ppc
orx86
.During the installation, select Browse directory to create or choose a directory for your pRISM+ installation.
After the installation of the pRISM+ product install the Service Pack, if any exists.
Apply the complete installation of the Integration of SNiFF+ 3.2 in pRISM+ 2.0 following the installation instructions in the
README.txt
.
The installation of SNiFF+ 3.2 is capable to support the pRISM+ installations for all CPU_FAMILIES at once.Multiple Installations In the UNIX Environment
In this section you will learn how to install and use multiple pRISM+ installations in a UNIX environment.
Installing Your Second pRISM+ Installation
During the installation, install your second pRISM+ installation in a different directory for example:
/User_Home_directory/68K/isi68k/
/User_Home_directory/Powerpc/isippc/
/User_Home_directory/PPC1_2_3/isippc/
The default installation directory is:
/User_Home_directory/isi$CPU_FAMILY/
where
$CPU_FAMILY
represents68k
,ARM
,mips
,ppc
, orx86
.Running Your Second pRISM+ Installation
To run one of your pRISM+ installations, you need to reset your environment variables. The
prismrc
orprismrc.csh
files identify your pRISM+ installation and the environment variables.
cd /User_Home_directory/isi$CPU_FAMILY
where
$CPU_FAMILY
represents68k
,ARM
,mips
,ppc
, orx86
. You need to be in the directory of the pRISM+ installation you want to access. (See Figure 15-2.) This command will take you to the pRISM+ installation directory.
source prismrc
source prismrc.cshYou can now use this pRISM+ installation directory for pSOSystem development.
15.2.2 Multiple-users Configuration (UNIX Only)
Multiple users can run pRISM+ on the same workstation. The default mode of operation for pRISM+ is for a single user to run it on a single workstation. This section describes the necessary steps you need to perform in order to have multiple users running on the same workstation.
Orbix Configuration for Multiuser Support
- To enable multiple user support on a Solaris machine, run the following sample script,
$PRISM_DIR/bin/multi-user-support.sh
, after the installation is completed. Note that in order to run the script root privilege is required.- Issue this command to start the Orbix daemon after the
multi-user-support
script has been executed.
- Users on this workstation need to set an environment variable in their profile (for example,
.profile
or.login
) to point to the directory containing Orbix.cfg. For example:
IT_CONFIG_PATH=/etc
export IT_CONFIG_PATHA log file
/var/adm/orbix
will be created for logging Orbix daemon activities.Memory Considerations (Solaris)
When multiple users are running pRISM+ from the same workstation, you can run into problems if the system is not adapted for multiple users. pRISM+ uses shared memory and when multiple users are using the workstation, the shared memory kernel parameters need to be tuned. You need to remember to allocate an equal amount of shared memory by using the swap space on the system.
See the document SunOS 5.x Administering Security, Performance and Accounting, Appendix A, Tuning Kernel Parameters for additional details. You can also use the answer book to get this information.
If the Target Setup window hangs when you are trying to download to your target, this can be one of the problems. The following error may appear to inform you that you need to tune your system:
No room for another process
15.2.3 Mixed-Platform Development for Solaris and Windows
This section describes how to develop a pSOSystem application in a mixed-platform environment. Specifically, it describes how to compile an application on the Solaris platform and debug the application using a Windows 95 or 98 or Windows NT based source level debugger.
System Environments and Configurations
- A UNIX workstation running Solaris 2.5.1 or 2.6 and pRISM+ version 2.0 or later.
- A PC running Windows 95, pRISM+ version 2.0 that includes SingleStep version 7.4, and NFS client software from Net Instrument.
Before You Begin
F:\isi<TargetName>\pss<TargetName>.<version>
- Consult the UNIX
man
pages on theshare
command to find out how to export part of your UNIX file system so you can NFS-mount it from your PC.- For this example,
/export/usr1
contains pRISM+ on your Solaris machine for the PowerPC processor type and pRISM+ has been installed into the directoryexport/usr1/isi
$CPU_FAMILY
.- Install NFS client software on your Windows 95 or Windows NT machine. NFS-mount
/export/usr1
and map it to the local driveF:\
.Make sure you can browse to this directory before proceeding:
Building Your Application in the UNIX Environment
Build your application according to the Quick Start with a Tutorial chapter. Ensure that the resulting
ram.elf
output file is place into a directory named/export/usr1/myapp
. If you cannot copy yourram.elf
to/export/usr1/myapp
then you must ftp your file to your PC. Use a Windows ftp application to copyram.elf
from your UNIX workstation to your PC.It is recommended to copy the
/ISI<TargetName>/users/<user_ID>/PSOS<TargetName>_PWE/appsram.elf
to this directory:
Debugging Your Application in the Windows Environment
To debug this application from the Windows based SingleStep Debugger, do the following:
- Launch Orbixd and pRISM+ Manager. Refer to Chapter 3.
- From the pRISM+ Manager, select the pRISM+ Shell button.
- In the pRISM+ Shell, type the following:
- For PowerPC:
psmppc
- For 68K:
psm68k
The Debug window and the SingleStep main window are displayed. See Figure 15-3 on page 15-10 for an example of the Debug window.
- In the Debug window, enter the path and the name of the
ram.elf
file in the File field.- Click on the Connection tab.
The Connection window is displayed (Figure 15-4).
- Click Network Host in the Type section of the Connection window.
- In the Details box, select UDP and enter the name of your target board (if DNS is available) or its IP address in the Host field.
- Click on the Logging tab and select the Log to screen (always) option.
- Click OK.
The system proceeds to make the network connection and download the executable image. The Debug Status window displays status messages as this takes place. When the download is complete, the Image Downloading, Target Reset, and Execute until `main' fields should show
Completed
, and the Debug Session field should showStarted Successfully
(see Figure 15-5).
NOTE: The status of the download is displayed in the bottom of the Debug Status window.
Your
ram.elf
file is now ready for you to debug.15.2.4 Redefining Your Environment Variables
The pRISM+ software installation includes a script file that sets up the pRISM+ environment. In the Windows environment the installation script automatically sets your environment variable to the default settings.
In the UNIX environment you must run a script in order to set your environment settings. These environment variables are set by the
prismrc
orprismrc.csh
script (depending on your platform). To ensure that these settings are made every time you log in, addprismrc
orprismrc.csh
to your startup or profile file.
NOTE: The variable PSS_BSP
setting is changed when you are using the pRISM+ Manager. When you change thePSS_BSP
setting you must exit and restart pRISM+. The installation provides a default setting.
In the Windows Environment the environment file is called
env
$CPU_FAMILY
.ksh
:
env68k.ksh
for the 68K environmentenvarm.ksh
for the ARM environmentenvmip.ksh
for the MIPS environmentenvppc.ksh
for the PowerPC environmentenvx86.ksh
for the X86 environmentThis script file is created at installation and is run automatically each time you start pRISM+. You can edit the
env
$CPU_FAMILY.ksh
file if you would like to change the pRISM+ environment settings. Each time you make a change to the script, you must first exit the Orbix daemon and pRISM+ Manager, make the change, then restart the Orbix daemon and pRISM+ Manager.In the UNIX Environment, you can also edit these variables. You can modify your environment variables in the following files:
envv
$CPU_FAMILY.csh
, where$CPU_FAMILY
can be one of the following: 68K, ARM, MIPS, PPC, or X86.envv$CPU_FAMILY.sh
, where$CPU_FAMILY
can be one of the following: 68K, ARM, MIPS, PPC, or X86.prismrc
prismrc.csh
These environment files are text files that can be easily edited by using any text editor. For additional information on the environment variables, refer to Appendix B, pRISM+ Environment Variables.
15.2.5 Redefining Your Color Settings (Solaris and HP-UX)
The color settings for pRISM+ Manager, ESp, Object Browser, and pRISM+ on-line help can be set through your
.Xdefaults
file. A sample.Xdefaults
file is provided in the$PRISM_DIR/lib
directory. This sample.Xdefaults
file can be appended to the end of your current.Xdefaults
file.Now, run the following command to replace the current property settings with the changes in your
.Xdefaults
file:The color settings for SNiFF+ are contained in the
.UserPrefs.sniff
file, which is copied to your$HOME
directory the first time you run pRISM+. See the SNiFF+ documentation for information relating to the setting of the colors for SNiFF+.
NOTE: The colors cannot be set for pRISM+ Wizard or the SearchLight user interface at this time.
15.2.6 Setting a Printer for On-line Help (Solaris and HP-UX)
This section describes how to correctly define a printer so you can print the pRISM+ on-line help. These directions are for the UNIX environment only.
LPT1 and LPT2 are valid printer slots provided by pRISM+. By using pRISM+, you need to create a PostScript file and redirect the applicable file to a printer denoted by either LPT1 or LPT2.
To configure LPT1 or LPT2, do the following steps:
- Edit the
win.ini
file. You can obtain this file from your$HOME/windows/win.ini
directory, which resides in your home directory.- Change the print commands for LPT1 or LPT2 to redirect the output to a printer of your choice. For LPT1, you can choose between two commands.
However, you can change the LPT1 command to the following
"LPT1:=lp -dprintername -c -s "%s" "
where printername is your specified printer.
![]() |
![]() |
![]() |