Experimental Physics and
Industrial Control System

Michael Davidsaver <[email protected]> · Fri, 28 Oct 2016 13:46:24 -0400

Another quick check of an NFS server is 'showmount -e 100.100.100.110'
to probe the running server.  Failed mount attempts should be logged (eg
/var/log/syslog or similar).

Also, the RTEMS NFS client doesn't speak NFSv4 yet.

On 10/28/2016 12:05 PM, Heinz Junkes wrote:
> Bhavna,
> 
> on host 100.100.100.110 there must be a nfs server running.
> 
> Please check that host for nfs.server processes:
> 
> $ ps -ef | grep nfsd
> rtems     5536  5516  0 18:01 pts/14   00:00:00 grep --color=auto nfsd
> root     19606     2  0 Aug30 ?        00:00:00 [nfsd4]
> root     19607     2  0 Aug30 ?        00:00:00 [nfsd4_callbacks]
> root     19611     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19612     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19613     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19614     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19615     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19616     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19617     2  0 Aug30 ?        00:00:00 [nfsd]
> root     19618     2  0 Aug30 ?        00:00:00 [nfsd]
> 
> and /etc/exports
> that there is an entry for /tftpboot/rt_test3 like this:
> $ more /etc/exports
> # /etc/exports: the access control list for filesystems which may be
> exported
> #to NFS clients.  See exports(5).
> #
> /tftpboot/rt_test3       100.100.100.0/24(rw,sync,no_subtree_check)
> 
> HTH,
> Heinz
> ------------------------------------------------------------------------------
> Fritz-Haber-Institut    | Phone:         (+49 30) 8413-4270
> Heinz Junkes             | Fax (G3+G4):   (+49 30) 8413-5900
> Faradayweg 4-6        | 
> D - 14195 Berlin        | E-Mail:     [email protected]
> <mailto:[email protected]>
> ------------------------------------------------------------------------------
> 
> On 28 October 2016 at 11:22:43, भावना नितिन मेढ़ ([email protected]
> <mailto:[email protected]>) wrote:
> 
>> Hi,
>>
>> I am using EPICS base 3.14.12.4 built on Centos6.5 with RTEMS version
>> 4.9.1
>> The command below works ok.
>> tftpget -c100.100.100.101 -s100.100.100.110 -g100.100.100.110
>> -d/dev/enet0-a04000000 -f/rt_test3/bin/RTEMS-mvme5500/test.boot
>>
>> I am getting following error while trying to load EPICS IOC for RTEMS on
>> MVME5500.
>> MVME5500> go -a04000000
>> -----------------------------------------
>> Welcome to rtems-4.9.2(PowerPC/Generic (classic FPU)/mvme5500) on
>> MVME5500-0163
>> -----------------------------------------
>> Now BSP_mem_size = 0x1FE00000
>> rtems_configuration_get_work_space_size() = 1F4000
>> Universe II PCI-VME bridge detected at 0x82000000, IRQ 12
>> Universe Master Ports:
>> Port VME-Addr Size PCI-Adrs Mode:
>> 0: 0x20000000 0x0E000000 0x90000000 A32, D64 [MBLT], Dat, Sup
>> 1: 0x00000000 0x00FF0000 0x9F000000 A24, D64 [MBLT], Dat, Sup
>> 2: 0x00000000 0x00010000 0x9FFF0000 A16, D64, Dat, Sup
>> Universe Slave Ports:
>> Port VME-Addr Size PCI-Adrs Mode:
>> 0: 0x90000000 0x1FE00000 0x00000000 A32, Pgm, Dat, Sup, Usr, PWEN, PREN
>> Overriding main IRQ line PCI info with 76
>> Registering /dev/console as minor 0 (==/dev/ttyS0)
>>
>> ***** Initializing network *****
>> Startup.
>>
>> Ethernet driver name wmG unit 1
>> Copyright (c) 2004,2005 S. Kate Feng <[email protected]> (RTEMS/mvme5500
>> port)
>> ***** Initializing NFS *****
>> RTEMS-RPCIOD $Release$, Till Straumann, Stanford/SLAC/SSRL 2002, See
>> LICENSE fi.
>> RTEMS-NFS $Release$, Till Straumann, Stanford/SLAC/SSRL 2002, See LICENSE
>> file .
>> Trying to mount 100.100.100.110:/tftpboot/rt_test3 on /tftpboot/rt_test3
>> RPCIO: server '100.100.100.110' not responding - still trying
>> RPCIO: server '100.100.100.110' not responding - still trying
>> RPCIO: server '100.100.100.110' not responding - still trying
>> Unable to contact NFS server - invalid port? (RPC: Timed out)
>> nfsMount - mount: Unknown protocol
>> rtems_bsdnet_get_ntp() Can't send: Host is down
>> rtems_bsdnet_get_ntp() Can't send: Host is down
>> ***** Starting EPICS application *****
>> Can't set initial directory(/tftpboot/rt_test3/iocBoot/ioctest/): No such
>> file y
>> Can't set initial directory():
>>
>> fatal error, exiting
>>
>> Printing a stack trace for your convenience :-)
>>
>> 0x00128D84--> 0x00118204--> 0x001181D0--> 0x00003254
>> RTEMS terminated; Boot manually or turn on AUTO_BOOT.
>>
>>
>> I have set following variables.
>>
>> MVME5500> gevshow
>> mot-/dev/enet1-cipa=192.168.1.99
>> mot-/dev/enet1-sipa=192.168.1.4
>> mot-/dev/enet1-gipa=192.168.1.1
>> mot-/dev/enet1-file=bootrom.bin
>> epics-script=/tftpboot/rt_test3/iocBoot/ioctest/st.cmd
>> mot-/dev/enet0-cipa=100.100.100.101
>> mot-/dev/enet0-sipa=100.100.100.110
>> mot-/dev/enet0-snma=255.255.255.0
>> mot-/dev/enet0-gipa=100.100.100.110
>> epics-nfsmount=100.100.100.110:/tftpboot/rt_test3:/tftpboot/rt_test3
>> Total Number of GE Variables =10, Bytes Utilized =395, Bytes Free =3197
>>
>> Please suggest.
>>
>> Regards,
>> Bhavna
>>

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System