g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
<== Date ==> <== Thread ==>

Subject: RE: Problem: Example IOC in RTEMS-MVME2304
From: "Hill, Jeffrey O" <johill@lanl.gov>
To: Qazi Zia-ul-Haque <smzhaq@gmail.com>, tech-talk <tech-talk@aps.anl.gov>
Date: Fri, 20 Apr 2012 16:57:58 +0000
Hi Zia,

> "(null)" is not a valid command pathname.

I am using vendor specific option 129 in my bootp server 
to set the path for the NFS startup script. So one 
possibility is that your Linux bootp server is providing
the vendor specific option 129 (which is presumably empty).

You can completely disable the use of bootp when 
configuring your target as follows in the target config file,
<epics base>/configure/os/CONFIG.Common.RTEMS-MVME2304

ARCH_DEP_CFLAGS += -DMY_DO_BOOTP=NULL

Alternatively, you could set the NFS path to the startup script
using the bootp server's configuration file. Here is an example 
Carnegie Mellon /etc/bootptab.

.default:\
  :hn:\
  :dn="myLab.gov":\
  :sm=255.255.255.0:\
  :gw=nn.mm.oo.gg:\
  :ts= nn.mm.oo.ts0, nn.mm.oo.ts1:\
  :ds= nn.mm.oo.dns0, nn.mm.oo.dns1:\
  :lg= nn.mm.oo.ss:\
  :sa= nn.mm.oo.ss:\
  :bf=boot.exe:

dingy:\
  :ht=ethernet:\
  :ha=0xaa0001f00dba:\
  :ip= nn.mm.oo.tt:\
  :hd=boot/iocName:\
  :T129="/epicsIOC/iocName/iocBoot/iociocName\
  :tc=.default:

> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov]
> On Behalf Of Qazi Zia-ul-Haque
> Sent: Thursday, April 19, 2012 5:47 AM
> To: tech-talk
> Subject: Problem: Example IOC in RTEMS-MVME2304
> 
> Hi
> 
> Continuing trying to run EPICS ioc in RTEMS-MVME2304, I am facing the
> following error message.
> 
> 
> ***** Initializing NFS *****
> "(null)" is not a valid command pathname.
> "" is not a valid command pathname.
> 
> I am using a tftp/nfs server to provide the boot file and argument
> file. However there is another BOOTP/DHCP server is running on the
> network which is to boot LINUX for installation. What I f eel is that
> the reason of error is the conflict between the two bootings (the
> bootp server and tftp/nfs server) perhaps and the CPU is trying to
> boot from the DHCP/BOOTP server after loading the boot file from
> TFTP/NFS server. However I am not sure if my feeling is correct.
> 
> Below is the complete output after isuing the nbo command from
> PPC1-BUG to initiate network booting in the MVME2304.
> 
> Please provide me your kind advice and guidance to proceed.
> 
> With Best Regards
> 
> Zia
> ______________________________________________
> 
> PPC1-Bug>nbo
> Network Booting from: DEC21140, Controller 0, Device 0
> Device Name: /pci@80000000/pci1011,9@e,0:0,0
> Loading: second.boot
> 
> Client IP Address      = 10.1.22.45
> Server IP Address      = 10.1.22.69
> Gateway IP Address     = 10.1.22.1
> Subnet IP Address Mask = 255.255.255.0
> Boot File Name         = second.boot
> Argument File Name     = 10.1.22.69:/tftpboot/st.cmd
> 
> Network Boot File load in progress... To abort hit <BREAK>
> 
> Bytes Received =&826464, Bytes Loaded =&826464
> Bytes/Second   =&137744, Elapsed Time =6 Second(s)
> 
> Residual-Data Located at: $07F88000
> 
> Model: 000000000000000000000000000(e2)
> Serial: MOT07C27F7
> Processor/Bus frequencies (Hz): 333391008/66672376
> Time Base Divisor: 4000
> Memory Size: 8000000
> 
> PCI: Probing PCI hardware
> 
> RTEMS 4.x/PPC load:
> Uncompressing the kernel...
> done
> Now booting...
> -----------------------------------------
> Welcome to rtems-4.10.2(PowerPC/Generic (classic FPU)/mvme2304) on MVME
> 2300
> -----------------------------------------
> idreg 0 = 0x48011057
> OpenPIC found at C1000000.
> pci : Configuring interrupt routing for 'MVME 2300'
> pci : No bridge from bus 0 towards root found
> pci : Unable to match device 0:0x0B:1 with an int routing table entry
> pci : No bridge from bus 0 towards root found
> pci : No bridge from bus 0 towards root found
> Cleared PCI errors: pci_stat was 0x2280
> OpenPIC Version ? (2 CPUs and 16 IRQ sources) at 0xC1000000
> OpenPIC Vendor 0 (Unknown), Device 0 (Unknown), Stepping 2
> OpenPIC timer frequency is 8333656 Hz
> Universe II PCI-VME bridge detected at 0xC1040000, IRQ 11
> Universe Master Ports:
> Port  VME-Addr   Size       PCI-Adrs   Mode:
> 0:    0x20000000 0x0E000000 0x10000000 A32, D64 [MBLT], Dat, Sup
> 1:    0x00000000 0x00FF0000 0x1F000000 A24, D64 [MBLT], Dat, Sup
> 2:    0x00000000 0x00010000 0x1FFF0000 A16, D64, Dat, Sup
> Universe Slave Ports:
> Port  VME-Addr   Size       PCI-Adrs   Mode:
> 0:    0xC0000000 0x07F80000 0x80000000 A32, Pgm, Dat, Sup, Usr, PWEN, PREN
> Registering /dev/console as minor 0 (==/dev/ttyS0)
> 
> ***** Initializing network *****
> Startup.
> dec21140 : found device 'dc1', bus 0x00, dev 0x0E, func 0x00
> dec2114x : unit 1 base address C1041000.
> dec2114x : driver attached
> dec2114x : driver tasks created
> bodoetcp2c1_1i4nxi t::  0u0s:i0n1g: AnFe:t0wBo:r9k3 :i6nFt e r fnaacmee
> ''ddcc1
> ,''
>   io 11000, mem C1041000, int 10
> dec2114x: Installing IRQ 10
> bootpc hw address is 0:1:af:b:93:6f
> My ip address is 10 .1 .22 .71
> Domain Name Server is 10 .1 .100 .20
> Domain Name Server is 10 .1 .100 .21
> Domain name is sesame.local
> Time Server is 10 .1 .100 .20
> Boot file is /pxelinux.0
> Subnet mask is 255 .255 .255 .0
> Server ip address is 10 .1 .100 .8
> Gateway ip address is 10 .1 .22 .1
> Log server ip address is 10 .1 .100 .8
> ***** Initializing NFS *****
> "(null)" is not a valid command pathname.
> "" is not a valid command pathname.
> 
> fatal error, exiting


References:
Problem: Example IOC in RTEMS-MVME2304 Qazi Zia-ul-Haque

Navigate by Date:
Prev: RE: mrfioc2 compile error Davidsaver, Michael
Next: Re: RE: mrfioc2 compile error 송영기
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
Navigate by Thread:
Prev: Problem: Example IOC in RTEMS-MVME2304 Qazi Zia-ul-Haque
Next: Problem in porting EPICS on microblaze softcore processor ssahoo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·