Experimental Physics and Industrial Control System
|
Till Straumann wrote:
Hi.
Let me first say that I'm not sure
'tech-talk' is the right forum to
address with this question which is
rather specific about the mvme5500 RTEMS
BSP and related software
Excuse me, but this is NOT specific
about the RTEMS-mvme5500 BSP. This is
a general question regarding how to load the
RTEMS/BSP/CEXP. It could be for any RTEMS
BSP that uses CEXP. Is'nt that "INIT" used by cexp ?
I think it's a good question to ask in EPICS as most
RTEMS users already know the how-to.
but has nothing
to do with EPICS.
Actaully I would strongly encourage Haoli Shi to
send more questions regarding EPICS3.14.9
to this tech-talk because I did not get a chance to
test the EPICS3.14.9 yet.
Also I would like to know which version of RTEMS Haoli used.
I remember that there were so many bugs in pre RTEMS4.7.0,
which were traced down to the powerPC shared files in the operating
system, but they were not due to the RTEMS-mvme5500 BSP.
Regards,
Kate
åæç wrote:
hi, there is an error about downloading the st.cmd(OS is RTEMS). in theNVRAM
configuration, I fill the "Command Line Parameters" with
"INIT=/home/shl/psApp/iocBoot/iocmvme5500/power_supply.cmd",but something
wrong appears as follows:
Till Straumann, Stanford/SLAC/SSRL 2002
See LICENSE file for licensing info
Trying to synchronize NTP...OK
Loading as 'shl' from '192.168.20.162' using RSH
Loading as 'shl' from '192.168.20.162' using RSH
Trying symfile 'BUILTIN', system script '/tmp/rshcpya00001'
Type 'cexpsh.help()' for help (no quotes)
Trying user script '/home/shl/psApp/iocBoot/iocmvme5500/power_supply.cmd':
Change Dir to '/home/shl/psApp/iocBoot/iocmvme5500/'
Type 'cexpsh.help()' for help (no quotes)
'power_supply.cmd':
opening script file: No such file or directory
Type 'cexpsh.help()' for help (no quotes)
Cexp>
why can't it find my .cmd file? (the file indeed lies in the directory,my
TFTP path is /home/shl/tftpboot, and my NFS shared directory is
/home/shl/psApp/iocBoot/iocmvme5500/, but here I use the absolute path)
It seems you use RSH for downloading the
operating system. There is no RSH support
however for downloading other pieces such
as scripts or loadable objects etc.
You must use TFTP or (more convenient) NFS.
The path to the '.cmd' file must contain
information about
a) the remote file-system type (TFTP vs. NFS)
b) the server
c) the remote path
E.g., you could say
INIT=/TFTP/123.4.56.8/psApp/iocBoot/iocmvme5500/power_supply.cmd
or
INIT=nfsserver:/home/shl:psApp/iocBoot/iocmvme5500/power_supply.cmd
another question, in the NVRAM configuration, one can pass a parameter to
application by filling "Command Line Parameters" with "NAME=value". if I won't
pass a parameter, how can I cancel the parameter?
You just leave 'command line parameters'
empty or let 'INIT=<path>' be the only
<NAME>=<value> pair...
HTH
-- Till
thanks a lot!
best regards
Haoli Shi
|
- Replies:
- Re: .cmd file downloading problem Êêñot;
- Navigate by Date:
- Prev:
Proposed change in asyn interruptCallback APIs Mark Rivers
- Next:
Re: Proposed change in asyn interruptCallback APIs Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: .cmd file downloading problem Till Straumann
- Next:
Re: .cmd file downloading problem Êêñot;
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 10 Nov 2011 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|