Upgrading Taurus

see note at the end for upgrade problems.
================

For both FTP and Telnet login, use "root" (without quotes) for username and 
password.

Locate your taurus-release-1.xx.yy.tgz file (and taurus-patch-1.xx.yy.tgz files 
if present) and upload them with FTP to the Taurus directory /mnt/ide (if an 
IDE drive is installed) or /mnt/cf (if a compact flash is installed).

Telnet to your taurus, then issue the following commands (assuming an IDE drive
is installed):
  cd /mnt/ide
  tar zxvf taurus-release-1.xx.yy.tgz
  tar zxvf taurus-patch-1.xx.yy.tgz   (if patches are provided)
  cd release-1.xx.yy
  ./taurus_install.sh
Note: The process should take about 15 minutes.
Note: Make sure the are no errors on the screen.

Once the files were successfully installed (you'll see a message saying so), 
start a browser on your PC and go to:
  http://taurus_ip:8080/firmware/ 

Confirm the files have been correctly uploaded by comparing the version numbers
on the page with the versions in the release-1.xx.yy directory.

At the Telnet window opened previously, type:
  ./testcode.sh

Note: The unit will reboot automatically.

Press the center button to start the UI. Make sure everything seems 
normal and you see the waveforms moving on the status page.

Start a browser and go to:
  http://taurus_ip:8080/firmware/ 

Confirm the newly updated files are active, but not default.
 
Telnet again to the unit and type in the following commands:
  cd /mnt/ide
  cd release-1.xx.yy
  ./setdefault.sh

Refresh the browser window and confirm that the active code is now
the default code. 

To check if the upgrade was successful go to the System Info page on the
UI and confirm that versions are the same as those in the directory
/mnt/ide/release-1.xx.yy.   The items should map as follows, where *
is the version number:

Taurus Product V:       directory_name      (release-*)
Digital Processor V:    TDP_ARM_*.nbf
Signal Processor V:     TaurusDsp_*.nbf
Power Manager V:        PowerMgrV*.nbf      (ignore the A/B)
Filter Coeefficients V: Coeff_*.nbf
FPGA V:                 TDP_FPGA_*.nbf
Flash Boot System V:    TCP_u-boot.bin-     (starts with 0.4.8 NMX *) 
Root File System V:     rootfs-upgrade-*.sh (starts with NMX-*)
Kernel V:               TCP_uImage.*        (starts with 2.4.24-NMX-*)
Taurus Server V:        taurusServer-*.tgz

The upgrade is now complete.

More serious upgrade issues.

Is the Taurus configured to use the correct media?  For example, the Taurus
is probably configured to use an IDE HD but the customer actually purchased
CF (compact flash).  If this is the case use the following document to
change the media type.

(See attached file: 15698R1.pdf)

It is very important that the upgrade package be installed on the removable
storage, in this case the CF, otherwise the Taurus may be corrupted.  Check
the root file system using the df command.  The rootfile system should not
be over 50%.

If you don't have enough time to switch the media try the following
commands before upgrading the unit via the CF.

1.  Log on to the Taurus via telnet.
2.  Then enter the following commands:
      pkill -9 taurus (kills all taurus applications)
      kill_konqueror (kills the Integrated User Interface)
      /etc/init.d/hearbeat  (starts the Taurus watchdog)
      /etc/init.d/syslog stop (stops the system log)
       You probably don't need the following but better safe than sorry.
      fdisk /dev/hdc  (format CF)
      mkfs -t ext3 /dev/hdc1 (make ext3 file system)
      mount -t ext3 /dev/hdc1 /mnt/cf (mount the CF)

At this point you should be able to follow the upgrade procedure, ftping
the file to the /mnt/cf/temp/ directory.  If you reboot or power cycle the
unit you will need to re-enter the first four commands of point #2.