Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.atnf.csiro.au/pub/people/vlbi/corrsched/reload.txt%3B1 Дата изменения: Mon Jul 28 05:29:57 2003 Дата индексирования: Tue Dec 25 04:47:16 2007 Кодировка: Поисковые слова: http astrokuban.info astrokuban

From jreynold@atnf.csiro.au Sat Sep 28 14:03:02 1996
Date: Fri, 13 Sep 1996 10:02:55 +1000 (EST)
From: John Reynolds
To: Paul Harbison ,
Edward King
Subject: Reloading S2 vram via Ethernet


Hi Paul and Edward,
Here's the procedure for reloading the S2 from a Sparc
via the Ethernet. This document was written for Warwick, so contains some
ATNF-specific references which should be easy to generalise.

The binary file you need is now on reber as;

/users/vlbi/s2/ros/dump940513


Good luck!

-JER

PS Dave Jauncey (well Dorothy actually) is bringing 40 S2 tapes down today.

------------------------------------------------------------------------

Setting Up an S2 System for Network Software Downloads
------------------------------------------------------

Note: This information applies to Berkeley-style Unix systems such as
SunOS 4.x, and may need to be modified for other systems.


1) Select a local Unix machine to act as host for your S2 systems.

2) Select a "home" directory for S2/VxWorks related files, e.g. /local/vw/.

3) Create a Unix user with userid 'vxworks', and home directory
as selected in (2).

4) Your S2 systems should already have been assigned host names. Add these
systems to the .rhosts file for user 'vxworks', i.e. /local/vw/.rhosts
s2at1.atnf.CSIRO.AU vxworks
s2at2.atnf.CSIRO.AU vxworks
s2at3.atnf.CSIRO.AU vxworks

5) Create the directory /local/vw/ros/data/. The last two components of
this name must be as given, but the preceding ones may be different as
chosen in step (2).

6) Place the S2 SRAM dump file supplied by ISTS in /local/vw/ros/data/.
Example file name: dump940513

7) Check the VxWorks network boot parameters of each S2 system to be
downloaded over the network. This can be done using the 'c' command
in the boot monitor, or the 'bootChange' command in the VxWorks shell
(if in ROS type 'shell' then 'bootChange'). Certain boot parameters
must be correct to access files on the Unix host:

host name: Set this to the internet name of the host chosen in (1).
file name: Set this to the directory chosen in (2) with basename 'vxWorks',
e.g. /usr/local/vxWorks
host inet: Set this to the internet address of the host chosen in (1).
user: Set this to 'vxworks' to match the userid from (3) above.
ftp password: Ensure this entry is blank (enter a dot '.' to clear).

Other fields such as gateway inet should be set as usual (see User's
Manual Section 4.4.1).

At this point you should verify that access to the Unix host works.
VxWorks uses rsh protocol to read files and directories.
Type the following in the VxWorks shell:
ls "/"
which should list the root directory of the Unix host system.

8) You are now ready to actually perform an S2 software upgrade or SRAM
reload. To upgrade using the dump file /local/vw/ros/data/dump940513,
type the following in the VxWorks shell:
restore_sram "940513"
This loads the entire 3 MByte SRAM, and might take about 30 seconds.
You might need to perform additional steps after the software is loaded,
such as programming transports with their new software. Refer to the
release notes that accompany the upgrade for details.


You can also save backup copies of an S2's SRAM to preserve changes such
as batch files and defaults settings:
dump_sram "at3"
will create a file called /local/vw/ros/data/dumpat3 containing the entire
contents of the 3 MB SRAM. Be careful when loading SRAM contents dumped from
one particular S2 into another S2, as some stored values such as the
data-recovery calibration configuration may be incompatible. You may need
to use the ROS 'dr reset flat' command to clean things up. To avoid problems,
we recommend that an SRAM dump only be used to reload the same S2 system from
which it came (distribution dump files supplied by ISTS have been cleaned up
and made "generic", so this restriction does not apply to them).

You can also save and restore certain individual SRAM partitions,
e.g. the /sram/exo/ partition gets corrupted and you want to replace it.
You must first save a valid non-corrupted copy of the desired partition
from a working S2, and then it can be loaded into another S2. Make sure
not to mix data from different software revisions. When in doubt reload
the entire SRAM using restore_sram or the old serial upload method.

Partition name Cmd to save Cmd to restore Unix save file
-------------- ----------- -------------- --------------
/sram/ svram_root ldram_root /local/vw/ros/data/root
/sram/exo/ svram_exo ldram_exo /local/vw/ros/data/exo
/sram/bin/ svram_bin ldram_bin /local/vw/ros/data/bin
/sram/batch/ svram_batch ldram_batch /local/vw/ros/data/batch
/sram/8051/ svram_8051 ldram_8051 /local/vw/ros/data/8051

There is only one Unix save file for each partition, so the next svram command
will overwrite the previous file.

Note: It is possible to corrupt the SRAM through incorrect use of the above
commands. The root and bin partitions /sram/ and /sram/bin must be reasonably
intact to be able to boot into the VxWorks shell. If you can't boot the
VxWorks shell, you also can't use any of these commands, and will have to
restore the SRAM using the old serial download method.


Georg Feil 94/06/06