Done ! Thanks for your reminder !
_______________________________________
From: Till Straumann [[email protected]]
Sent: Monday, February 06, 2012 2:21 PM
To: Zhu, Lixin
Cc: [email protected]
Subject: Re: EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!!
On 02/06/2012 11:52 AM, Zhu, Lixin wrote:
> Thanks for your quick reponse,
>
> In fact, I only configured the 2 env varibale,
You should read the page I linked - here's it again:
http://www.aps.anl.gov/epics/base/RTEMS/tutorial/node18.html#SECTION00514200000000000000
you need to configure a few more variables.
T.
>
> 1) mot-script-boot
>
> 2) epics-script
>
> MVME3100> gevShow
> mot-script-boot
> tftpGet -c192.168.10.9 -s192.168.10.10 -fdemo/test.boot
> netShut
> go
>
> epics-script=192.168.10.10:tftpboot/demo:st.cmd
> Total Number of GE Variables =2, Bytes Utilized =132, Bytes Free =3460
> MVME3100>
>
>
> Before the RTEMS taking control, the networking is fine. If not, the Motload can't download the test.boot into the memory, and the code runs smoothly.
>
>
> I don't know how to check the networking is working or not, as the test.boot ( IOC demo) running and taking control of the whole system , and entering the IOC shell.
>
>
> I think maybe the
> 1) the target board and nfs server channel broken
>
> 2) nfs server or tftp server side, need some specifial conifurations. It seems the RPCIOD ( nfs ) can't send data to the server side.
>
>
>
> ________________________________________
> From: Till Straumann [[email protected]]
> Sent: Monday, February 06, 2012 12:30 PM
> To: Zhu, Lixin
> Cc: [email protected]
> Subject: Re: EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!!
>
> What is your RTEMS network configuration (the 'SEND failure' and 'Can't
> send...'
> messages indicate that networking is not configured correctly or at all)?
> Did you follow the instructions:
>
> http://www.aps.anl.gov/epics/base/RTEMS/tutorial/node18.html#SECTION00514200000000000000
>
>
> HTH
> -- Till
>
> On 02/05/2012 04:16 PM, Zhu, Lixin wrote:
>> Hi all,
>>
>> I am a new comer for the EPICS (10 days ), and I am now porting the RTEMS + EPICS to mvme3100 board. I meet the following case ,
>>
>>
>>
>> 1) For the NFS mode, after i downloading a ICO simple example example.boot, it shows the following infor.
>>
>>
>> ***** Initializing network *****
>> ***** Initializing NFS *****
>> RTEMS-RPCIOD $Release$, Till Straumann, Stanford/SLAC/SSRL 2002, See LICENSE file for licensing info.
>> RTEMS-NFS $Release$, Till Straumann, Stanford/SLAC/SSRL 2002, See LICENSE file for licensing info.
>> Trying to mount 192.168.10.10:/tftpboot/demo/iocboot/ioctest on /tftpboot/demo/iocboot/ioctest
>> RPCIO: SEND failure
>> Unable to contact NFS server - invalid port? (RPC: Unable to send)
>> nfsMount - mount: Unknown protocol
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> ***** Starting EPICS application *****
>> Can't open /tftpboot/demo/iocboot/ioctest/st.cmd: No such file or directory
>> 192.168.10.9> pwd
>> /tftpboot/demo/iocboot/ioctest
>>
>> I can't mount the nfs server , the st.cmd can't be called by the example.boot .
>>
>> The server is Debian lenny. I used another Unbuntu linux to mount the nfs server exported directory successfully .
>>
>> Any fast method to work aroud the issue ?
>>
>>
>>
>> 2) Since the nfs does't work, i try to turn to the TFTP mode . however, the error as the following ,
>>
>>
>> vmeTsi148 - IRQ manager using VME CSR to flush FIFO
>>
>> 6 I2C devices registered
>>
>> Registering /dev/console as minor 0 (==/dev/ttyS0)
>>
>> Startup.
>>
>> ***** Initializing network *****
>> ***** Initializing TFTP *****
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> ***** Starting EPICS application *****
>> Can't open /TFTP/BOOTP_HOST/epics/169.254.92.2/st.cmd: No such file or directory
>>
>> 169.254.92.2>
>>
>>
>> I don't know wether the st.cmd file would be downloaded from the server automatically or not. It is really no file, only empty directory.
>>
>> Anyone who knows about this issue ?
>>
>>
>>
>> One of the complete log:
>>
>> Copyright Motorola Inc. 1999-2005, All Rights Reserved
>> MOTLoad RTOS Version 2.0, PAL Version 1.1 RM03
>> Wed Oct 19 17:29:08 MST 2005
>>
>> MPU-Type =MPC8540
>> MPU-Int Clock Speed =666MHz
>> MPU-CCB Clock Speed =333MHz
>> MPU-DDR Clock Speed =166MHz
>> MPU-PCI Clock Speed =66MHz, PCI, 64-bit
>> MPU-Int Cache(L2) Enabled, 256KB, L2CTL =A8000300
>>
>> Reset/Boot Vector =Flash0
>>
>> Local Memory Found =10000000 (&268435456)
>> User Download Buffer =014D3000:016D2FFF
>>
>> MVME3100> tftpGet -c192.168.10.9 -s192.168.10.10 -fdemo/test.boot
>> Network Loading from: /dev/enet0
>> Loading File: demo/test.boot
>> Load Address: 014D3000
>> Download Buffer Size = 00200000
>>
>> Client IP Address = 192.168.10.9
>> Server IP Address = 192.168.10.10
>> Gateway IP Address = 192.168.10.253
>> Subnet IP Address Mask = 255.255.255.0
>>
>> Network File Load in Progress...
>>
>> Bytes Received =&1676364, Bytes Loaded =&1676364
>> Bytes/Second =&1676364, Elapsed Time =1 Second(s)
>> MVME3100> netShut
>> /dev/enet0 Disabled
>> /dev/enet1 Disabled
>> /dev-----------------------------------------
>> Welcome to rtems-4.9.3(PowerPC/Generic (no FPU)/mvme3100)
>> BSP: mvme3100, CVS Release ($Name: rtems-4-9-3 $)
>> CPU 0x8020 - rev 0x20
>> Additionnal boot options are H
>> Initial system stack at 1AB658
>> Software IRQ stack starts at 1AB750 with size 16384
>> Going to start PCI buses scanning and initialization
>> PCI A Status: 09 : 66MHz PCI 64-bit
>> PCI B Status: B8 : 33MHz PCI 64-bit
>> PMC1: ready PMC2: ready 3.3V
>> PCI C Status: 09 : 66MHz PCI 64-bit
>> PMC1: empty
>> PMC2: empty
>> PMCSpan: empty
>> Build Date: Thu Apr 14 19:18:32 UTC 2011
>> Board Type: MVME3100-1152 (S/N E031BAD)
>> External (=PCI Bus) Clock Freq : 66666666 Hz
>> Core Complex Bus (CCB) Clock Freq: 333333330 Hz
>> CPU Clock Freq: 133333332 Hz
>> Ethernet 0 00:01:AF:31:91:9D
>> Ethernet 1 00:01:AF:31:91:9E
>> Ethernet 2 00:01:AF:31:91:9F
>> Number of PCI buses found is : 2
>> BUS:SLOT:FUN VENDOR-DEV_ID: COMMAND STATUS BASE_ADDR0 BASE_ADDR1 IRQ_PIN -> IRQ_LINE
>> 0:0x00:0 0x1057-0x0008: 0x0006 0x20B0 0x80000000 0x00000000 0 -> 0 (=0x00)
>> 0:0x11:0 0x10E3-0x0148: 0x0146 0x02B0 0x80100004 0x00000000 1 -> 0 (=0x00)
>> 0:0x12:0 0x10B5-0x6520: 0x0147 0x02B0 0x00000000 0x00000000 0 -> 0 (=0x00)
>> 0:0x14:0 0x8086-0x3200: 0x0145 0x02B0 0x00011001 0x00012001 1 -> 2 (=0x02)
>> 1:0x02:0 0x10B5-0x9030: 0x0142 0x0290 0x80200000 0x00000000 1 -> 6 (=0x06)
>> Memory: 268435456 bytes
>> Cleared PCI errors: pci_stat was 0x20B0
>> Configuration.work_space_size = 1F4000
>> OpenPIC Version 1.2 (1 CPUs and 56 IRQ sources) at 0xE1040000
>> OpenPIC Vendor 0 (Unknown), Device 0 (Unknown), Stepping 0
>> OpenPIC timer frequency is 41666666 Hz
>> MSR is 0x00001000, TCR 0x04000000
>> -----------------------------------------
>> Exit from bspstart
>> Tundra Tsi148 PCI-VME bridge detected at 0x80100000, IRQ 0
>> Tsi148 Outbound Ports:
>> Port VME-Addr Size PCI-Adrs Mode:
>> 0: 0x20000000 0x0E000000 0xC0000000 A32, SUP, D32, SCT
>> 1: 0x00000000 0x00FF0000 0xCF000000 A24, SUP, D32, SCT
>> 2: 0x00000000 0x00010000 0xCFFF0000 A16, SUP, D32, SCT
>> 7: 0x00000000 0x01000000 0xCE000000 CSR, SUP, D32, SCT
>> Tsi148 Inbound Ports:
>> Port VME-Addr Size PCI-Adrs Mode:
>> 0: 0xC0000000 0x10000000 0x00000000 A32, PGM, DAT, SUP, USR, MBLT, BLT
>> vmeTsi148 IRQ manager: looking for registers on VME...
>> Trying to find CSR on VME...
>> vmeTsi148 - IRQ manager using VME CSR to flush FIFO
>> 6 I2C devices registered
>> Registering /dev/console as minor 0 (==/dev/ttyS0)
>> Startup.
>>
>> ***** Initializing network *****
>> ***** Initializing NFS *****
>> RTEMS-RPCIOD $Release$, Till Straumann, Stanford/SLAC/SSRL 2002, See LICENSE file for licensing info.
>> RTEMS-NFS $Release$, Till Straumann, Stanford/SLAC/SSRL 2002, See LICENSE file for licensing info.
>> Trying to mount 192.168.10.10:/tftpboot/demo/iocboot/ioctest on /tftpboot/demo/iocboot/ioctest
>> RPCIO: SEND failure
>> Unable to contact NFS server - invalid port? (RPC: Unable to send)
>> nfsMount - mount: Unknown protocol
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> rtems_bsdnet_get_ntp() Can't send: Host is unreachable
>> ***** Starting EPICS application *****
>> Can't open /tftpboot/demo/iocboot/ioctest/st.cmd: No such file or directory
>> 192.168.10.9> pwd
>> /tftpboot/demo/iocboot/ioctest
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thank you all.
>>
>>
>>
>> Kevin Zhu,
>>
>> FRIB, East Lansing, US
>>
>> [email protected]
>>
>> l
>>
>>
>>
>>
>>
>>
>>
- References:
- EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!! Zhu, Lixin
- Re: EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!! Till Straumann
- RE: EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!! Zhu, Lixin
- Re: EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!! Till Straumann
- Navigate by Date:
- Prev:
RE: CARS modbus output record initialization Mark Rivers
- Next:
Virtual circuit disconnect - caRepeater bug? Oleg Makarov
- 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: EPICS IOC NFS mount and TFTP issue for the mvme3100 board, please help, urgent !!! Till Straumann
- Next:
Charged Particle detectors? Pierrick Hanlet
- 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
|