Hi Eric,
Okay, so this means that iocsh has no dependencies on EPICS?
We could use iocsh as just a basic SHELL with the RTEMS OS?
I guess we will still need to do some kind of cdCommands to support
the
cexp SHELL that we use here.
Thanks,
Ernest
On Mon, 2007-11-05 at 10:38 -0600, Eric Norum wrote:
On Nov 5, 2007, at 10:18 AM, Ernest L. Williams Jr. wrote:
On Mon, 2007-11-05 at 10:10 -0600, Eric Norum wrote:
We use envPaths here, since we use iocsh rather than cexp to start
our RTEMS IOCs.
Or am I misunderstanding what you want?
There are certain operating system specific commands one might
perform
before EPICS is loaded up. For example, we may want to cd around
the
file system in an easy way before EPICS loads up.
And envPaths/iocsh allow this.
Here are the first few lines from one of our RTEMS IOC startup
scripts. The values of TOP, ASDSTD, and ARCH are all set by the
envPaths file.
#####################################################################
###
#####
# Set up environment variables
# EDM wants to transfer waveform values as 4-byte values which means
that
# EPICS_CA_MAX_ARRAY_BYTES must be greater than 2^18*4.
< envPaths
epicsEnvSet EPICS_CA_MAX_ARRAY_BYTES 1050000
epicsEnvSet TZ "CST6CDT,M 3.2.0,M 11.1.0"
epicsEnvSet MAX1619_ADDR 24
< ../nfsCommands
epicsEnvSet IOC_INFO /iocinfo
epicsEnvSet P B:tune:
cd "${TOP}"
.....
then later on in the script there's a more complex cd:
cd "${ASDSTD}/bin/${ARCH}"