MODULE 13

UPGRADE ASPEN™ ULTRASOUND SYSTEM

Overview 13-3
Objectives 13-3
Purpose 13-3
Instructions 13-3
Upgrade Components 13-4
MO Disk 13-4
SYSCON 13-4
Microcode 13-4
BootPROMs 13-4
Encryption 13-5
Performing an Upgrade 13-6
Preparation 13-6
Upgrade 13-6
Wrap Up 13-6
Upgrade Verification 13-7
Software Verification 13-7
Functional Verification 13-7
Diagnostic Verification 13-7
BBM Clear Procedure 13-8
Warning! 13-8
Connecting a Laptop to AEGIS System/Lynx 13-10
Overview 13-10
Laptop Software Setup 13-10
Cable Connections 13-11
AEGIS System Start Up Example 13-13
AEGIS System Upgrade Example 13-16
Upgrade Questions 13-20
Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

REVISION HISTORY

QRC P/N-REVISION INITIATOR APPROVAL DATE CHANGE

59178 Rev. X1 J. Koeper S. Williams July 1999 Incorporate reviewer comments

A3174 59178 Rev. 1 J. Madarasz S. Williams Dec. 2000 Initial Release

Module 13-2 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Overview

OVERVIEW
OBJECTIVES This module should provide the student the following
understanding:
• the major components of a typical upgrade
• how to perform an upgrade using an MO disk
• how to change firmware on the PCBs
• how to install new encryption
• how to verify the system after an upgrade
• how to reformat the hard drive when software corruption is
suspected

PURPOSE Every upgrade is different. Please use this module as an

introduction, but always refer to the appropriate TIP (depending on
the upgrade performed) that has detailed steps and instructions.

INSTRUCTIONS Perform a simulation of an upgrade. This is not a normal system

upgrade, but the procedure for reinstalling software in case of
corruption. Refer to the appropriate documents in this module for
detailed instructions.
1 Store BBM to a laptop computer. Refer to the BBM TIP.
2 Clear Battery Backed Memory.
3 Hook up your laptop to AEGIS/Lynx to see the upgrade as it
occurs.
4 Reinstall the software using an MO. Choose the selection to reinstall
ALL software (in case of corruption.) Refer to the Hard drive
Reformat TIP.
5 After the upgrade, restore BBM from the laptop.

NOTE: If this were being done in the field, BBM would NOT be restored, but
would be configured manually. Restoring BBM at this point would
reintroduce any software corruption unless a file was saved prior to the
software problem.

6 Run the Z command in Diagnostics to check software and

bootPROMs.
Normally this would be compared to the appropriate upgrade TIP.
7 Check the Configuration Report to verify the system encryption is
still valid.

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 3

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

UPGRADE COMPONENTS
The following items are parts of a typical Aspen system upgrade.
Please refer to the appropriate upgrade TIP for more specific
information.
MO DISK The MO disk contains all system software for the upgrade, which
may include: PONMON, SYSCON, Diagnostics, Microcode, AEGIS
system and SYCON user parameters, Lynx software, and AEGIS
system software.
SYSCON SYSCON, Ponmon and diagnostics reside on the SVC board. The
flash SIMMs in locations J7 & J8 contain all system operating
software. The SIMMs are upgraded by use of the MO disk. The only
other software in the system is microcode and bootPROMs.
MICROCODE Microcode can reside on a MEX board (the system can hold up to 3
MEX boards) or resides on the SCP in flash SIMMs after a 4.0
upgrade.

NOTE: There is no SCP code on the SCP or MEX boards. SCP code is located
in the flash on the SVC board.

BOOTPROMS BootPROMs are used to bring up the system hardware and allow
code to be downloaded to each board from the flash on the SVC.
Each part is labeled with the board it resides on, version number,
and location. Use the special socket tool to carefully remove the old
part. Orient a new part by matching up the arrow or dot within the
socket with the arrow or dot on the top or bottom of the part.
SCP U69 & U72
WFP U37
SVC U29
RP2 U08
DCI U105
UIC2 U19
FEC LO U146
FEC HI U145

NOTE: The Aspen system has a helpful test in manual diagnostics (the Z
command) that displays all the bootPROM versions. This should
always be verified after an upgrade.

Module 13-4 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Upgrade Components

Assembling all the bootPROM versions...

Shutdowns LynxOS...DONE!
Assembling all the diagnostic versions...
Assembling all the board versions...
Software and Hardware Configuration Report - SN 30015
----------------------------------------------------------------------
Aspen Release 2.00 7/29/97

BOOT PROM VERSIONS

SVC2BOOTMON 32.110 Wed Jul 16 18:16:26 1997
DCIBOOT 31.108 Wed Jul 24 17:48:08 1996
FECBOOT 31.201 Tue Nov 12 12:57:10 1996
RPBOOT 32.102 Mon Feb 24 15:10:29 1997
SCPBOOT 31.105 Thu Apr 18 09:49:16 1996
UICBOOT 31.105 Mon Jul 8 21:07:21 1996
WFPBOOT 31.104 Tue Jul 9 17:09:10 1996

Figure 13-1 Example of “Z” command listing

ENCRYPTION The system has encryption codes which configure the system to
provide the user options which have been purchased. Encryption is
stored in BBM and is accessed through the Engineering Menu #109
using TEST + CODE + SHIFT + V.
Notice that the encryption lines are of variable lengths. It is an
option to type in the numbers continuously, without spaces or
formatting. The encryption code will be formatted when it is saved.

NOTE: Always have a copy of the most recent encryption.

Figure 13-2 Encryption - Engineering Menu #109

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 5

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

PERFORMING AN UPGRADE
PREPARATION
◆ To prepare the system for an upgrade
1 Verify functionality of the system prior to the upgrade by running
Power On diagnostics, scanning, and checking major modalities.
2 Store BBM to a laptop, and/or take manual pictures of all user
configuration settings. Refer to the BBM TIP.
UPGRADE
◆ To upgrade the system
1 Upgrade any necessary hardware. Always use ESD precautions.
2 Always refer to TIP 12 or to the upgrade TIP to verify jumper
settings and firmware on newly installed boards.
3 Remove the MEX (if appropriate).
4 Upgrade (if applicable) bootPROMs on the PCBs.
• Use a PROM or PLCC puller and take care not to damage the
device.
• Make note of the checksum and version on the firmware and
verify it against the TIP.
5 Connect a laptop to the AEGIS/DCI serial port on the IOB to view the
upgrade as it occurs. Refer to the procedure later in this module.
6 Insert an MO disk, power up the system, and press the U key on the
keyboard (U for Upgrade).
7 Upgrade the system software by answering the questions displayed
on the system monitor. Refer to the appropriate upgrade TIP.
8 When the software upgrade is complete, reset the system and let it
run through the Power-On Diagnostics. The upgrade MO should be
automatically ejected.
9 Install encryption as needed through the Engineering Menu #109.
10 Configure any new user settings (as necessary).
11 Verify the system as detailed in the Upgrade Verification procedure.
WRAP UP
◆ To wrap-up the upgrade process:
1 Store the new version of BBM if a laptop computer is available.
2 Communicate any necessary information to the customer.
3 Fill out appropriate paperwork.
4 Close any service notifications through the Acuson Help Desk.
5 Return parts.

Module 13-6 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Upgrade Verification

UPGRADE VERIFICATION
SOFTWARE
VERIFICATION
◆ To verify software
1 Go into the ENGINEERING menu and verify that the Version Report
#101 matches the software listing in the upgrade TIP.
2 Verify the Config Report (Engineering menu #102) according to the
new encryption.
3 Run the Z command in MANUAL DIAGNOSTICS to verify the software
and bootPROM listings as described in the Diagnostics Section.
4 Run the MEMEX CHECKSUM test to verify the MEX (if a new one was
installed).
FUNCTIONAL
VERIFICATION
◆ To verify functionality
1 Verify proper system operation by checking major modalities (2-D,
Color, PW, Auto Doppler, Mmode.)
2 Verify AEGIS Static and Dynamic capture and review. Also verify
storage and retrieval of exam using an MO disk.
3 Verify various transducers including V5M (if applicable).
4 Verify ECG module if present.
5 Reconnect and verify any peripherals.
DIAGNOSTIC
VERIFICATION
◆ To perform the diagnostic verification:
• Run the PM or NI Test Suite. The PM suite takes approximately
30 minutes and the NI suite is more comprehensive and may
take over an hour.

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 7

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

BBM CLEAR PROCEDURE

Use this procedure to fix some battery backed memory (BBM)
related system problems (e.g., system locks up during
initialization.) Please also reference the BBM Store/Restore Utility
CPD-006, p/n 56414.

WARNING! • Use in extreme circumstances on the recommendation from

Product Support or the Helpdesk only! This will erase all user
programs, setups and AEGIS system protocols.
• Ideally after a system install and applications visit, BBM should
be stored to a file on a laptop computer. If a valid BBM file is
available (stored prior to corruption) restore this file after
clearing BBM.

Set all BBM to 1 Enter the Diagnostic menu using RESET, TEST or TEST immediately
zeros after power up if the system was off.
2 Select Service Access to get to the Manufacturing Menu. Enter your
access number and password as explained in the diagnostics
section.
3 Use the trackball and select keys to choose: UTILITIES, CLEAR ALL
BBM.
4 Press Y for yes to clear the BBM.
5 Reset the system.

Re-initialize BBM After using the CLEAR ALL BBM utility, you must re-initialize the
BBM to system defaults. The system will not operate properly
unless you complete this step.

NOTE: Some problems may be fixed with this step ONLY, which would not
erase all user settings.

1 Go to the Engineering menu and select #404.

2 Hit the softkey SET to re-initialize the BBM.
3 Reset the System.

Module 13-8 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential BBM Clear Procedure

Download BBM • If you have a file for this serial number with “valid” user
from laptop settings and encryption, use your laptop to download this back
to the system.

NOTE: A valid BBM file is defined as a file that was stored from the system
prior to the software corruption. Do NOT restore BBM that was stored
immediately prior to clearing BBM or the corruption may be
reintroduced.

If you do not have a file with valid BBM perform the following
steps:
Re-install 1 Go to the Engineering menu and select #109;
Encryption 2 Enter system encryption.
3 Hit SAVE.
4 Reset the System.
Turn Aegis back 1 Go to engineering menu #601.
on 2 Select the DCI enable pull-down menu and select STANDALONE to
enable Aegis.
3 Reset the System.
Reinstall User • Reinstall user settings, programs, printer setups, and AEGIS
Specific Settings system protocols.

NOTE: This normally requires Applications support.

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 9

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

CONNECTING A LAPTOP TO AEGIS SYSTEM/LYNX

OVERVIEW This document describes the cabling and setup necessary to connect
a laptop to an Aspen system to view messages from AEGIS system
and Lynx. Lynx is the operating system resident on the hard drive
which runs the AEGIS system software on an Aspen system. The
DCI board controls the start up of the hard drive, Lynx and AEGIS
system software. The DCI also provides the necessary
communication links to the rest of the system and SYSCON via the
SVC and IOB boards.
If a laptop is connected to the DCI serial port on the IOB,
communication messages from the DCI and hard drive can be
viewed. These messages can be extremely helpful during an
upgrade and AEGIS troubleshooting.
LAPTOP SOFTWARE The laptop must be configured to run a terminal emulation
SETUP software. This is the same setup as is used for communicating with
a Sequoia system.
1 Click Start, Programs, Accessories, Hyper Terminal to bring up the
HyperTerminal group directory. (It is included in Windows 95.)
2 Double click Hypertrm icon to start up a new session.
3 Enter a Name for the session (e.g., Aspenconnect). Click OK.
4 At the pop-up Phone Number screen under Connect using, select
Direct to Com1. Then click OK.
5 At the Port Setting of COM1 Properties screen, set all values as
shown below. Then click OK.
• Connect using = Direct to Com 1
• Bits per second = 19200
• Data bits = 8
• Parity = None
• Stop bits = 1
• Flow control = none
6 Depress the ENTER key couple times until the Lynx USER NAME:
prompt appears. The USER NAME: prompt verifies proper connection.

Module 13-10 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Connecting a Laptop to AEGIS System/Lynx

CABLE The laptop can be connected with either of two methods depending
CONNECTIONS on the cables available. Please see the drawing on the next page.

Method 1 Parts needed:

• Null Modem Serial cable (P/N 51031)
• IOB2-AEGIS system cable (P/N 50510)
Connection path:
• Laptop-(Com1 port)<--->Null Modem Serial cable<--->IOB2-
AEGIS system cable<--->Aspen-(IOB2 AUX RGB IN port-10 or
J24). See Figure 1.
Method 2 Parts needed:
• RJ12 to RJ12 serial (modem) cable (P/N 51484)
• DB9pin female to RJ12 adaptor (P/N 53983)
• DB15pin male to RJ12 adaptor (P/N 53416)

NOTE: The modem cable can be used, but a different connector to the IOB is
required!

Connection path:
• Laptop-(Com1 port)<--->DB9pin female to RJ12 adaptor<---
>RJ12 to RJ12 serial cable<--->DB15pin male to RJ12 adaptor<--
->Aspen-(IOB2 AUX RGB IN port-10 or J24). See Figure 1.

NOTE: The modem should usually be connected to port 6 - J20 for remote
access to SVC hardware diagnostics. In the future the modem may also
be connected to port 10 - J24 for remote access to troubleshoot AEGIS
system problems. It is very important that the modem is connected to
the appropriate port or remote access will not be possible. Please see the
drawing on the next page.

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 11

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

Laptop IOB2
Aspen system
5 J19-ethernet
acuson

6 J20-serial B

7 J21-none

8 J22-VCR

9 J23-Betacam
Com1 Port
DB9 Male
10 J24-aux RGB

DB26 Male
DB9 Female DB9 Female
IOB2-SVC
Laptop DB15 Male DB15 Male
adaptor
adaptor IOB2-AEGIS p/n 51471
IOB2-DCI RJ12
p/n 53983 RJ12 cable p/n 50510 RJ12 adapter
p/n 53416
DB 25 Female remote
access to
DB 25 Male h/w diags

Null Modem Serial

cable p/n 51031
RJ12-to-RJ12
RJ12-to-RJ12 (modem) modem cable
cable p/n 51484 p/n 51484
remote
access to
AEGIS system

Note: The laptop can also be connected Serial

to port 1 - J13 for BBM transfers. Modem
Figure 13-3 Laptop Connection to AEGIS System /Lynx

Module 13-12 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Connecting a Laptop to AEGIS System/Lynx

AEGIS SYSTEM The following printout is an example of normal power-up

START UP EXAMPLE communication from the DCI on a functional system at 4.0. This
may be helpful to use in troubleshooting as a comparison if a
system is not functioning properly.
4.0 System START:

DRAM config is 8
Video config is 0
Boot Device config is 10
Reserved config is 7a
XSUM config is 6d

Waiting for Unit Ready.Exec Status 2

Exec Status 2
.
. (repeated)
.

Exec Status 2
.
SCSI Status is 0
DONE
**** Loading...Partition starts at 0x20 block
Dev/Partition info at 1024 is 0x10
i_block call: blk= 32001
(/lynx.os is at inode 18)
i_block call: blk= 32604
.
. (repeated)
.
i_block call: blk= 32743
--- scsi_close() is done! ---loaded
move_end - move_code = 64 bytes
Move the kernel from 0x100000 to 0x1000, using move_code() at
address 0x1a7800
Verify kernel code thru its ’struct exec’:
0x0b 0x01 0x00 0x00 0x00 0x40 0x08 0x00 0x00 0xc0 0x00 0x00 0x70
0xe2 0x01 0x00

0x9c 0xc9 0x00 0x00 0x20 0x10 0x00 0xdb 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00

root device: 0,1

scsincr_scsi: info->vector = 2e
ncr_scsi: info->pic_reset_reg = 0
ncr_scsi: info->pic_siop_reg = f0a08000
ncr_scsi: info->srbase = 0
ncr_scsi: info->srsize = 2000
.
ns32install
ns32install: Physical Addr: 0xb8000000 Logical Addr: 0xdfffd000
ns32_ethernet_support: temp = 0xdead
_ncr_open(): removable = 0 error = 0 ready = 1

DCI LynxOS 2.3 Startup:

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 13

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

DPR driver ID = 23
g up interrupt handlers
Interrupt handler set up
DPR mojor device ID = 27
DPR driver successfully installed

mounting all filesystems

*** Installing PSC video driver (DCI-2) ***

Video driver ID = 24
Interrupt handlers installed
Video interrupts enabled
Board is progressive-scan (DCI-2)
Driver is also progressive-scan, combination okay
DCI board revision is: 2
JPEG daughter card type is JPEG2
JPEG daughter card revision is 0
Video config is NTSC
Initializing parameter sets
Initializing CLUTs
Initializing gamma tables
Memory size = 131072 kbytes, image buffer size = 49152 kbytes
Capture buffer size = 1024 kbytes each (2 buffers)
Video major device ID = 28
*** Video driver successfully installed ***
[1] 18
[2] 20
***************************************
* *
* Boot daemon waiting for interrupt *
* *
***************************************
launchLogProcess, about to fork logging process
launchLogProcess, lolaunchLogProcess, Calling execv, program name
= ’dcilogD’
launchLogProcess, argList[0] = ’dcilogD’
launchLogProcess, argList[1] = ’/acuson/dci/bsem/dcilogD’
gging process started, waiting on semaphore
dcilogD: argc = 2
dcilogD: argv[0] = ’dcilogD’
dcilogD: argv[1] = ’/acuson/dci/bsem/dcilogD’
dcilogD: semaphore path = ’/acuson/dci/bsem/dcilogD’
launchLogProcess, Logging process successfully synched!

user name:[DSM Server, 36] DSMPMain after StdStarter

CSCOMM: <42> DSMP thread is STARTED!
DFS: DOS file system for Lynx
dfs: 40 buffers, 80 FCBs, 5 sessions
DFS server: accepting connections
DicomBoss[1570] main: begin process
server: connection accepted-client FD 10, sid=0
CSCOMM: <44> MOServer thread is STARTED!
DicomBoss[1600] main: logging level at 1
CSCOMM: <45> DFSP thread is STARTED!
CSCOMM: <46> DFS Client thread is STARTED!
CSCOMM: <47> CSCOMM_CB_THREAD thread is STARTED!
CSCOMM: <48> DFS Client thread is STARTED!
DCSCOMM: <50> DFS Client thread is STARTED!
CSCOMM: <52> CSCOMM_CB_THREAD thread is STARTED!

Module 13-14 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Connecting a Laptop to AEGIS System/Lynx

CSCOMM: <56> CSCOMM_CB_THREAD thread is STARTED!

CSCOMM: <57> CSCOMM_CB_THREAD thread is STARTED!
icomBoss[1624] main: connected to SMH
DicomBoss[1676] main: starting main SMH message loop
CSCOMM: <68> MO Monitor thread is STARTED!
ncr_scsi: Unknown sense condition 6
Hostname stored in /etc/ourName is: host-test2
TLogFile::Write, pipelining files
TLogFile::OpenFile, file dcilog.next does not currently exist
TLogFile::OpenFile, no file to rename, creating file dcilog.next
TLogFile::Write, writing first entry to next file
IP address: 157.226.23.22
Hostname stored in /etc/ourLanguage is: english

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 15

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

AEGIS SYSTEM The following is an example of communication from the DCI at the
UPGRADE EXAMPLE start of a normal 4.0 upgrade. This may be helpful to use in

Module 13-16 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Connecting a Laptop to AEGIS System/Lynx

troubleshooting
DRAM config is 8
Video config is 0
Boot Device config is 1
Reserved config is 7a
XSUM config is 7c
Modify Script for MO Drive

Waiting for Unit Ready.Exec Status 2

Exec Status 2
.Exec Status 2
(repeated)
:Exec Status 8
(repeated)
:Exec Status 2
Exec Status 2
.
SCSI Status is 0
DONE
**** Loading...Dev/Partition info at 1024 is 0x4020
i_block call: blk= 3889
(/lynx.os is at inode 18)
i_block call: blk= 4053
.
. (repeated)
.
i_block call: blk= 4192
--- scsi_close() is done! ---loaded
move_end - move_code = 64 bytes
Move the kernel from 0x100000 to 0x1000, using move_code() at
address 0x1a7800
Verify kernel code thru its ’struct exec’:
0x0b 0x01 0x00 0x00 0x00 0x40 0x08 0x00 0x00 0xc0 0x00 0x00 0x70
0xe2 0x01 0x00
0x9c 0xc9 0x00 0x00 0x20 0x10 0x00 0xdb 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00
root device: 1,0
scsincr_scsi: info->vector = 2e
ncr_scsi: info->pic_reset_reg = 0
ncr_scsi: info->pic_siop_reg = f0a08000
ncr_scsi: info->srbase = 0
ncr_scsi: info->srsize = 2000
.
ns32install
ns32install: Physical Addr: 0xb8000000 Logical Addr: 0xdfffd000
ns32_ethernet_support: temp = 0xdead
_ncr_open(): removable = 1 error = 0 ready = 1

LynxOS Startup: a

Setting up interrupt handlers

Interrupt handler set up
DPR driver ID = 23
DPR mojor device ID = 27
DPR driver successfully installed
Date set to Wed Mar 17 06:33:20 PST 1999
/AegisHardDisk/usr/bin/edl v1.3 - SVC a.out/OMF/IEEE695/memory
image reader/loader

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 17

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

Initializing DCI download

Processing a.out file "/upgrade/svc_install_server.68"

.-
Total bytes loaded: 43796
174 download messages: (172 data, 1 start address, 1 load address)
DCI-SVC flash load communications are operational

mounting all filesystems

***************************************
* *
* Boot daemon waiting for interrupt *
* *
***************************************
Creating backup directory structure...
Creating directory: /HDBackup
Creating directory: /HDBackup/acuson
Creating directory: /HDBackup/acuson/dci
Creating directory: /HDBackup/bin
Creating directory: /HDBackup/etc
about to mount /dev/sd0a
ncr_scsi: Unknown sense condition cb
mount: /dev/sd0a on /mnt: Device or address doesn’t exist
about to mount /dev/sd0a
_ncr_open(): removable = 0 error = 0 ready = 1
mount of /dev/sd0a successful
Aegis portion of recall sets exist.
Aegis exam descriptors exist.

This system will be upgraded to Aspen_4.00 release.

Creating ’pre-Aspen_4.0’ /mnt/etc/DCIVersion
Creating ’pre-Aspen_4.0’ /mnt/etc/WebProVersion
Creating ’pre-Aspen_4.0’ /mnt/etc/SuperlinkVersion
Creating ’pre-Aspen_4.0’ /mnt/etc/UcodeVersion

Do you want to continue? (y/n) - y

yesOrNo = y
yesOrNo = y
currOSVersion = 3.5.11a
newOSVersion = 4.1.3
currOSFileSystem = 2.3.0
newOSFileSystem = 2.3.0
currDCIVersion = pre-Aspen_4.0
newDCIVersion = 4.1.7
currWebProVersion = pre-Aspen_4.0
newWebProVersion = 34.204
current Aegis version X Y = 3 5
new Aegis version X Y = 4 1

The hard disk does not need to be reformatted. However, if you suspect
that the hard disk is corrupted, you may choose to reformat it. Choosing
to do so will erase all existing studies.

Reformat the hard disk? (y/n) - y

The hard disk will be reformatted, then Lynx OS and AEGIS

applications will be installed.

You will have an opportunity to preserve the existing

AEGIS configuration. However, all studies will be erased.

Module 13-18 Aspen Service Training Manual P/N 59178 Rev. 1

Acuson Confidential Connecting a Laptop to AEGIS System/Lynx

Do you want to continue? (y/n) - y

currSuperlinkVersion = pre-Aspen_4.0
newSuperlinkVersion = Aspen_4.00

Getting microcode inventory...

overwriting
Initiating flashUcode program download...
starting microcode program load
downloaded 1600 flashUcode program bytes
.
. (repeated)
.
downloaded 35428 flashUcode program bytes
flashUcode program download completed.
35428 bytes transferred
Getting flashUcode program checksum...Executing flashUcode
program...
flashUcode program is now running.
upgradeServer: It took 1992221 counts to reset flashUcode.
Getting ucode inventory...
currUcodeVersion = Aspen_4_0
stdUcodeVersion = Aspen_4_0

Installation options are:

1: Perform standard upgrade which requires the following update(s):

- Hard disk format
- Lynx OS
- AEGIS applications
- SVC FLASH Superlink

2: Modify the existing release or reinstall individual component(s).

Enter option number (1 or 2) - 1

The current AEGIS configuration can be preserved. If you choose

not to preserve it, the following information will be lost:
- Aegis portion of recall sets
- Aegis exam descriptors

Preserve current configuration? (y/n) - y

Creating directory: /HDBackup/acuson/dci/storage
Creating directory: /HDBackup/acuson/dci/storage/ntsc
Creating directory: /HDBackup/acuson/dci/storage/pal

Saving Aegis portion of recall sets...

Saving file: /mnt/acuson/dci/storage/ntsc/ABDOMEN to
/HDBackup/acuson/dci/storage/ntsc
Saving file: /mnt/acuson/dci/storage/ntsc/CAROTID to
/HDBackup/acuson/dci/storage/ntsc
Saving file: /mnt/acuson/dci/storage/ntsc/ESSAIBBM to
/HDBackup/acuson/dci/storage/ntsc
Saving file: /mnt/acuson/dci/storage/ntsc/STRESS~20ECHO1 to
/HDBackup/acuson/dci/storage/ntsc
Saving file: /mnt/acuson/dci/storage/ntsc/STRESS~20ECHO3 to
/HDBackup/acuson/dci/storage/ntsc
Saving file: /mnt/acuson/dci/storage/ntsc/WWWWW to
/HDBackup/acuson/dci/storage/ntsc
(continued)...

P/N 59178 Rev. 1 Aspen Service Training Manual Module 13- 19

Module 13 - Upgrade Aspen™ Ultrasound System Acuson Confidential

UPGRADE QUESTIONS
1 What are two important steps to perform before an upgrade?

2 How can the firmware version be verified after an upgrade?

3 Which PCB has SYSCON on it? __________

4 What is the significance of the 4 digit alphanumeric value on a
bootPROM?

5 When is BBM not reinstalled into the system after an upgrade?

6 What is the benefit of connecting a laptop to an Aspen system

during an upgrade?

Module 13-20 Aspen Service Training Manual P/N 59178 Rev. 1