Page History

...

Next, download the NetBoot program into the IOC. Use the network address that you obtained during "Inventory".
It needs to be entered with the tftpGet command, after the "-c" (for client) on the command line. Note that the backslash () is put at the end of the line as a continuation marker. You can simply type the remainder of the command without the backslash.In order to use the tftp server your ethernet wall connection MUST be on the
lclsdev subnet (ie 134.79.219.xxx) or the lclsdmz subnet (ie 134.79.151.xxx) or the lclsca subnet (ie 172.27.yyy.xxx). Note that the "xxx" needs to be replaced with the correct value from your own address. If your ethernet wall connection is NOT on the lclsdev or lclsdmz subnet then you can load the flash in your cpu from another configured cpu (of the same model). This is done by copying the flash in the configured cpu

You can also load the flash in your cpu from another configured cpu (of the same model). This is done by copying the flash in the configured cpu over the VME backplane to the cpu you intend to flash. Instructions on how to perform this operation can be found by clicking here .

The "-s" parameter allows us to specify the server address:
For the lclsdev subnetdevelopment, it is 134.79.219.136, the address of the lcls-dev1 server.  Note: Users are not allowed to log onto lcls-dev1.
For the lclsdmz subnet, it is 134.79.155.15, the address of the mccdev VMS server.
For the lclsca subnet, it is 172.LCLS production, it is 172.27.8.4128, the address of the lcls-builder srv04 server.

The "-m" parameter indicates a netmask to use to access the server.

Finally, the "-f" parameter indicates the name of the file (under /tftpboot on lclslaci@lcls-dev1, elsewhere on mccdev) Note: User's are not allowed to log onto lcls-dev1
containing the sequence of values to be loaded into memory.
For the lclsdev subnet, it is It is set to /rtems/4.910.42/powerpc-rtems/beatnik/img/netboot.flashimg.bin
For the lclsdmz subnet, it is /rtems/4.9.4/powerpc-rtems/beatnik/img/netboot.flashimg.bin
for the lclsca subnet, it is /rtems/4.9.4/powerpc-rtems/beatnik/img/netboot.flashimg.bin_for both production and development. Note that the mount for tftp is mapped to from the environment variable $TFTPBOOT on the development and production control systems. Therefore if you "cd $TFTPBOOT" the path following "-f" should exist.

On the lclsdmz subnetproduction:

On lclsca subnet

For the mvme5500 processor, the command is identical. The same version of the NetBoot program is downloaded, although the output on the screen will be slightly different.
At this point, we'll disable the network activity on all adapters, to ensure nothing interrupts us while we copy the image to flash memory. This is not essential, because it is not likely that any network activity would have an effect on the system at this point.

For the mvme5500 processor, the command is identical. The same version of the NetBoot program is downloaded, although the output on the screen will be slightly different.
At this point, we'll disable the network activity on all adapters, to ensure nothing interrupts us while we copy the image to flash memory. This is not essential, because it is not likely that any network activity would have an effect on the system at this point.

Now we can actually copy the memory image that we downloaded in step 4 above from RAM into Flash. That is, we're copying it from temporary memory into a more permanent memory that will last after power failures or restarts. If you notice in the tftpGet output, it tells us the load address, in this example for the mvme5500, it was 005C3000. The load address is the location to which the file was copied.
We'll copy this file from that memory location into the Flash memory, so it won't be lost. In this example, the flashProgram command is used; the "-s" parameter indicates the source of the data to be copied, in our example 0x005C3000. The "-v" parameter tells the software to be verbose about what it's Now we can actually copy the memory image that we downloaded in step 4 above from RAM into Flash. That is, we're copying it from temporary memory into a more permanent memory that will last after power failures or restarts. If you notice in the tftpGet output, it tells us the load address, in this example for the mvme5500, it was 005C3000. The load address is the location to which the file was copied.
We'll copy this file from that memory location into the Flash memory, so it won't be lost. In this example, the flashProgram command is used; the "-s" parameter indicates the source of the data to be copied, in our example 0x005C3000. The "-v" parameter tells the software to be verbose about what it's doing. It prints a few lines, then asks you to confirm.

...

• At this point, you've confirmed the flash memory contains the right data. The netBoot software will recognize several commands from your keyboard, and it's listed them after you've interrupted its boot process.
• Normally when it runs, netBoot attempts to download the software that you ultimately want to use. To do so, it keeps several parameters in non-volatile memory (NVRAM.)
• Now you're going to set those various parameters and record them in NVRAM. Press "c" to change the parameters that netBoot will use to download software. Keep in mind that your own processors IP address must be entered under "My IP", just as it's name.
• Typically, only the fields marked "My IP", "My name" and "Command Line Parameters" will have values unique to your processor. All other fields should be entered as you see here. If you have questions, please ask a Controls Software Engineer from theEPICS Team.
• The field "Command Line Parameters"is set to:
• (booting from NFS): INIT=/boot/epics/iocCommon/user , followed by a path to your boot-up script. If you're using the AFS filesystem, which is common at SLAC, then your path will typically be something like /u/ <two-chars> / <login user-id> /path-to-example . If you are booting out of the shared lcls group space, the boot-up script is /boot/g
/lcls/epics/iocCommon/"<your-node-name>"/startup.cmd. See the example below.
• /lcls/epics/iocCommon/"<your-node-name>"/startup.cmd . See the example below. Please note that the same DNS and the NTP servers for development and test-facility are used.

  
  

  Facility	TFTP Server	Boot Server	Gateway	DNS	NTP
  Development	LCLS-DEV1 134.79.219.136	AFSNFS 172.23.66.102	134.79.219.1	134.79.111.111 134.79.111.112	134.79.110.75 134.79.110.10
  Test-Facility	LCLS-DEV1 134.79.219.136	AFSNFS 172.23.66.102	172.27.96.1	134.79.111.111 134.79.111.112	134.79.110.75 134.79.110.10
  LCLS	LCLS-SRV04 172.27.8.28	MCCFS2 172.27.8.11	172.27.0.1	134.79.151.12 134.79.151.13	134.79.151.12 134.79.151.13
  FACET		MCCFS2 172.27.8.11	172.27.8.1	134.79.151.12 134.79.151.13	134.79.151.12 134.79.151.13

1. Now you can continue with the boot process. When you're done setting the values in the previous step, you'll be given the list of netBoot commands again. Type "m" to continue with the boot process to make sure everything is correct.
2. You'll see a very long set of messages come from the processor console, ending in a prompt that says "Cexp>". RTEMS has successfully started running on your processor.
3. To get back to MOTLoad, type:

Saving an Automatic Boot Script and Recovery from "gev" errors"

Those few steps that you took before changing the NVRAM are all that are needed to reboot the computer again. These steps may need to be repeated after replacing a battery, or if you get the error "Warning: Global Environment Variable Area is uninitialized, use gevInit" (after issuing the "gevInit" command). Now, we can save those steps so the processor can perform them automatically each time it restarts.

...

...

RTEMS CEXP Functions

LCLS Node NVRAM Settings

• LCLS Node NVRAM Settings

Till's MVME README.mvme5500 file

...