BusinessPhone Communication Platform 5.1
Maintenance Instruction ASB 150 02

## Upgrading of system software and firmware

This function is used to upgrade the current software/firmware running in an ASB 150 02 exchange to a different or enhanced version.

The upgrading of the ASB 150 02 software/firmware can be performed without exchanging the program memory circuits (EPROMs or Compact Flashcards).

The software/firmware can be uploaded remotely via modem, or direct via V.24 connection by using the BusinessPhone Management Suite

Note

Upgrade procedures cannot be performed via a TCP/IP connection towards the IPU, except for the IPU itself.

The following boards are remote upgradeable:

Software: CPU - D4

Firmware: BTU-B2, BTU-D, ELU-D3, MFU and IPU

The remote upgrading of the IPU is handled differently to the software/firmware upgrade of the other boards and is therefore described in a separate chapter; see Remote upgrading of the IPU.

### Remote upgrading of system software and firmware of BTU-B2, BTU-D, ELU-D3, MFU

#### General

The upgrading procedure of the central software/firmware is divided into three main steps:

- Creating of the upgrade file
  This function is used to generate software/firmware upgrade files based on the available binary files, which are normally used for EPROM programming.
- Upload of the upgrade files
  The generated software/firmware upgrade files will be uploaded into the CPU-D4 by using the integrated terminal application of the BMS
  The CPU-D4 stores the new software/firmware versions in a temporary storage area, the so-called “Upgrade FLASH memory” (separate areas for software and firmware). The CPU-D4 continues to operate while the upgrade files are loaded, as the central processor operates on the program stored in the program memory area, i. e. active FLASH memory.
- Administration of the upgrade data
  When connected to the exchange, the technician has several options of administrating the upgrade process,
  such as:

- Viewing information on the uploaded software and firmware versions
- Defining and cancelling upgrades
- Defining the upgrade time

##### Software upgrade

When the defined upgrade time is reached the CPU-D4 will be automatically restarted. During restart, several actions are performed.

- The content of the upgrade FLASH memory is verified.
- The base data of the active FLASH memory is merged with the data stored in the upgrade FLASH memory.
- After a final verification, the CPU-D4 is restarted and the data of the upgrade FLASH memory is copied into the active FLASH memory.

This process results in a delay of the start-up, which is indicated by flashing LEDs
(see document Fault Tracing, 1545-ASB150 02 Uen).

##### Firmware upgrade

When the defined upgrade time is reached, the CPU-D4 executes a “shutdown” of all peripheral boards. After a successful shutdown has been performed, the CPU-D4 copies the firmware images from its own upgrade FLASH memory onto the FLASH memory on the peripheral board. The order of the firmware image copy is board-type related, which means that equal board types are always updated in parallel.

After a successful copy procedure, the CPU-D4 initiates a system restart.

During the whole upgrade procedure, the yellow LED on the peripheral boards supporting the firmware upgrade flashes rapidly. On boards that do not support the firmware upgrade function, the yellow LED flashes slowly. In addition to the flashing yellow LED, all boards that currently receive the firmware image from the CPU-D4 are indicated by a flashing green LED.

#### Requirements

For a remote upgrade of the software/firmware of ASB 150 02, following board revisions are required

- CPU-D4 (ROF 157 5124/1)

  |  | R-state PCB |  | R2A or higher |
  |  | HW-code |  | 3 or higher |
  |  | FW |  | RYS 102 533 R3A or higher |
  |  | SW |  | LZY 203 2232 (Release 12) or higher |

- FECU connected to CPU-D4)

  |  | SW and FW upgrading: |  | KDU BS 130 12/x (Release 12) or higher |
  |  | only SW upgrading: |  | KDU BS 130 06/x (Release 10) or higher |

- BTU-B2 (ROF 157 5121)

  |  | R-state PCB |  | R7A or higher |
  |  | HW-code |  | 0 or higher |
  |  | FW |  | RYS 102 521 R8A or higher |

- BTU-D (ROF 157 5112)

  |  | R-state PCB |  | R3A or higher |
  |  | HW-code |  | 1 or higher |
  |  | FW ISDN |  | LZY 203 213/1 R9A or higher |
  |  | FW CAS |  | LZY 203 212/1 R7A or higher |

- ELU-D3 (ROF 157 5130)

  |  | R-state PCB |  | R3A or higher |
  |  | HW-code |  | 0 or higher |
  |  | FW |  | RYS 102 532 R2A or higher |

- MFU (ROF 157 5132))

  |  | R-state PCB |  | R2A or higher |
  |  | HW-code |  | 0 or higher |
  |  | FW |  | RYS 102 538 R2A or higher |

Note

The system can also be equipped with peripheral boards which are equipped with EPROMS (older HW revision than the one mentioned above). These boards are still supported, but of course they cannot be used by the remote firmware upgrading function.

To get an overview of whether or not the CPU-D4 is upgradeable, and which of the peripheral boards are upgradeable, use the following procedure:

1. Connect the BMS to the system
2. Select ’Boards’ in the tree view, to open the context menu
3. Click on “Hardware details”

- .

#### Install the software/firmware files on the BMS Server

The latest binary software/firmware files will be provided by your local Ericsson Support Centre.

Download the required files into a common directory on your PC. All the available files are usually compressed, and after extraction, the following binary ASB150 02 files are available:

Example 1: software Release 12 files

readR1A.xls | This file contains information on the software version.
121R1A.me | These files are necessary for the upgrading program.
C11R1A.bin
C21R1A.bin
C31R1A.bin

Example 2: MFU Firmware R2A

readR2A.xls | This file contains information on the firmware version.
mfu1R2A.bin | These files are necessary for the upgrading program
mfu2R2A.bin

##### File description

- The *.xls files contain additional information on the software version and the firmware version; they are not required for upgrade.
- The *.me file contains information about the software release, the market version and the revision as well as the EPROM generation information.
- The *.bin files represent the content of the FLASH PROMS on the CPU-D4, as well as on the peripheral boards. All the binary files are needed to perform a software or firmware upgrade. The binary files can be used to program EPROMS on the EPROM programmer, but not for direct upload to the PBX. Therefore, it is necessary to create an upgrade file with the BMS which adds the necessary checksum and header information to the file.

Note

If you have no need to burn EPROMS, you can also download the pre-generated firmware upgrade files from the local Ericsson Support Centre.
Regarding the MFU firmware files, two versions of binary files exist. One is used for EPROM programming (total size 4 MBit), and the other is used for remote firmware upgrading, in conjunction with BMS (total size 2 MBit). If you use the 4Mbit versions in conjunction with BMS, the conversions will fail.

To install the firmware/software files on the BMS Server use the following procedure:

1. Start up the BMS and open the Tools Dialog
2. Click on Software/Firmware Upgrade
3. Click on File Manager

- The file manager shows all available *bin, *me and generated *.txt files.
  Click on ’Delete’ if you do not need specific files any longer

1. Click on ’Browse’ to import the required files for the upgrading (needs to be done file per file).

#### Creating the upgrade file

Before creating the software/firmware upgrade file for a PBX, the following information has to be determined:

- Current software release
- Market index
- Software version (Revision)

In the case of the central software, the BMS determines the delta between the new and the currently installed software version and creates an upgrade file (*.txt). For special cases, e.g. changing of the language version, the tool can also generate an upgrade file, which contains the complete software-version.

In the case of the firmware upgrading, the complete firmware application image will always be generated in an upgrade file.

##### File denominations

The file denominations used for remote upgrading are explained as follows:

##### software upgrade files

Example: software Release 10 Index 1 Revision R1A shall be upgraded to Revision R1B

##### firmware upgrade files

Example: ELU-D3

Note

The upgrade file is specially coded (containing line number, checksum,...) and must not be opened by any tool (e.g. editor) as the data may be corrupted.

##### Delta software upgrade

Choosing this option keeps the transmission time as short as possible. The BMS creates a file comprising only the differences between the existing software in the exchange and the new software to which it should be upgraded.

Note

The central software to which the system is to be upgraded must be based on the language version that is already installed in the system. If the language is to be changed, the system must be upgraded with the complete software in the new language.
If the central software is to be upgraded to a new Release, please refer to the chapter Special considerations for the software upgrade, because in most cases some activities, such as firmware upgrading of specific boards or upgrading of the FECU need to be performed in order to guarantee the requested functionality.

Example:

The screen below shows an upgrade from software Release 11 Index 1 Revision R2A to Release 13 Index 1 Revision R1A

.

Click on ’Submit’ to generate the output file r111R2A_r131R1A.txt

##### Full central software upgrade

By choosing this option, a complete new software file with the largest possible file size will be generated.

Example:

The screen below shows a full upgrade to software Release 13 Index 1 Revision R1A.

Click on ’Submit’ to generate the output file Blank_r131R1A.txt

##### Firmware upgrade

In case of the firmware upgrade only complete new files can be generated.

The upgrade (output) file name is related to the RYS-number (product number) of the peripheral board.
(In our example, RYS102538_r2a.txt).

#### Upload and administration of the upgrade data

1. Before starting the upgrade procedure, verify that the system time and date is correct, otherwise modify it.
2. Disconnect the BMS from the system and remove it from the tree view
3. Open the Tools Dialog
4. Click on Software/Firmware Upgrade
5. Select the desired system which is to be upgraded and click on the ’Submit’ button

- The connection to the system will be built up in terminal mode

1. When the connection is established, the main menu will be shown

##### Main Menu

The main menu prompts the following functions:

The CPU-D4 supervises the communication. If no input occurs for more than 15 minutes, the BMS is logged off and the connection is shut down. This is to prevent unnecessary connection fees, in case of a remote connection. The CPU-D4 verifies all entered requests and the menu screen offers a selection of commands that are executed by typing in a letter.

Note

If the menu entry “F Firmware upgrade information” is not available, please check the minimum requirements of the CPU-D4 and the connected FECU. (See Requirements)

- Select the desired function in the menu above by typing in the related letter and clicking on the ’Submit’ button.

##### Menu item "S" - view information about active FLASH and upgrade FLASH

- ACTIVE PROGRAM
  This information applies to the actually running ASB 150 02 software program in the active FLASH.
- UPGRADE PROGRAM
  This information applies to the ASB 150 02 software program, which is stored in the upgrade FLASH. The content is re-written by uploading the new software. During every system restart the content in the upgrade FLASH is checked. If an error is encountered (e.g. wrong checksum or last uploading of new software was not finished) the content of the active FLASH will be copied into the upgrade FLASH.
- SYSTEM MEMORY TYPE
  States the type of the used FLASH proms
- UPGRADE STATE

- This information indicates one of the following states:

- NO Upgrade
  neither software nor firmware upgrade ordered yet.
- Upgrade requested
  software and firmware will be upgraded
- Firmware Error 1
  first error during firmware upgrade
- Firmware Error 2
  second error during firmware upgrade
- UNKNOWN

- Press ENTER or click on the ’Submit’ button to return to the main menu

##### Menu item “T” - view system, and upgrade time

This menu displays the system and upgrade time. No change of time settings is permitted on this screen.

- Press ENTER or click on the ’Submit’ button to return to the main menu

##### Menu item "F" - view information about loaded firmware application images

This menu item contains the following information of already loaded firmware application images in the upgrade FLASH memory:

- Type of loaded firmware application
  such as BTU-B2, BTU-D, ELU-D3 or MFU
- Size of specific firmware application images
  MFU = 512kB; BTU-B2, BTU-D, ELU-D3 =256kB
- State of FW upgrade Flash memory on the CPU-D4
  Shows the status of the upload process to the CPU-D4 upgrade FLASH memory. Normal states are “OK” or “UPGRADE WAS ORDERED”. Any other status information indicates that one or more errors occurred during the last upload process. The upgrade of a specific firmware application image can only be ordered if the state variable indicates “OK” within this menu.
- Product number and revision information
  Product information elements about already loaded/stored firmware application images.
- Checksum of loaded firmware application image
- Amount of spare memory in firmware upgrade FLASH circuit.
  Information about free memory within the firmware upgrade FLASH memory. This is used to check whether there is enough space available on the CPU-D4 for further firmware application images.In ASB 150 02 all firmware application images for the upgradeable boards can be loaded onto the FLASH memory.
- Press ENTER or click on the ’Submit’ button to return to the main menu.

##### Menu item "R"- Remove loaded firmware applications

The menu is used to remove an already loaded firmware application image from the upgrade FLASH memory. One of the reasons for doing so might be that a newer revision is already available.

Note

If an upgrade for a specific firmware application has already been ordered, the upgrade will automatically be deactivated if the images are to be removed.

- Press A-Z to erase the dedicated firmware file
- Press + to erase all firmware files
- Press ENTER or click on the ’Submit’ button to return to the main menu

##### Menu item "U" - Load new software/firmware into upgrade FLASH

- Click on the radio button to select the desired file
- Click on the ’Upgrade’ button to start the upload into the upgrade Flash

Note

If a firmware application image is already stored in the upgrade FLASH memory, it will automatically be destroyed, if a firmware of the same board type is sent again ( e.g. a newer one). Only firmware applications that belong to the installed peripheral boards can be uploaded. If the peripheral board is equipped with a released firmware application (EPROM), it is only possible to load the FLASH PROMs with a higher preliminary or released firmware application.
If a preliminary firmware application is stored on the FLASH PROMS, it is possible to load them with a higher preliminary or released firmware application, as well as an older preliminary firmware application as long it belongs to the same revision series.

The following table shows the possible upgrade and downgrade scenarios.

Note

In case of unexpected major problems in connection with a preliminary revision, it is always possible to downgrade to a prior preliminary revision, whereby the first one always equals the prior released revision.
If the FLASH PROMS are loaded with a firmware application higher than the one stored on the EPROM, the board will always start-up with the data from the FLASH PROM ( this can not be applied for preliminary revsions of the same number series e.g. P1BA->P1BB)

The next screen shows the process of file uploading.

After the file transfer has been started, this screen shows the progress of the uploading process. Each FLASH PROM is numbered with a specific index (1 to 3) and the number shows which FLASH PROM and which MAP is currently re-written. An "X" is displayed as a progress indicator as data is being stored. If an error occurs during transmission, a short error message describing the cause of the error is displayed.

If the file was transferred without any error UPLOADING SUCCESSFULLY COMPLETED ! is displayed.

- Press ENTER or click on the ’Submit’ button to return to the main menu.

##### Menu item "D" – define upgrade time

- Enter the desired upgrade time in the format as stated in the example ( alternative valid format : 0110111730 ) and press ENTER or click on the ’Submit’ button to confirm it.
- The new upgrade time will be displayed in the screen, press ENTER or click on the ’Submit’ button to return to the main menu.
- Enter ’E’ to return to the main menu without changing the ordered upgrade.

Note

If upgrade is ordered, a system restart will cause traffic interruption. Select a time that causes the least disturbance to the customer. The entered upgrade time has to be a time that is later than the system time. The year of the upgrade time has to be the same as the year of the system time.

The time is verified every 5 minutes. Thus, after waiting for up to 5 minutes, upgrading will be activated. If the program in the upgrade FLASH is valid and the system time reaches the upgrade time, the system will automatically perform the upgrade procedure.

During the upgrade procedure, the application image will be transferred from the upgrade FLASH circuits to the required interface boards, or to the active software FLASH memory circuits on the CPU-D4 to be executed after the following board or system restart.

In case of power failure or unexpected system restart during the upgrade procedure, the upgrading of peripheral interface boards will be repeated up to three times! Upgrading of central software applications will be repeated until successfully executed!

Note

The software/firmware versions stated on the PROMS sticker become obsolete after a remote upgrade.

Lead time for firmware upgrading including system restart:

Type | transmit time from the CPU to the peripheral board | restart time
ELU-D3 | ~ 5 min. | ~ 9 min.
MFU | ~ 21 min. | ~ 14 min.
BTU-B2 | ~ 10 min. | ~ 9 min.
BTU-D (ISDN) | ~ 10 min. | ~ 9 min.
BTU-D (CAS) | ~ 10 min. | ~ 9 min.

##### Menu item "C" – cancel ordered upgrade time

- Enter ’D’ to cancel an already ordered upgrade. This reset has no influence on the selected applications to be used for the upgrade.
- Enter ’E’ to return to the main menu without cancelling the ordered upgrade.

##### Menu item "O"- Order upgrade of loaded software/firmware applications

The menu will be used to select whether or not the software and/or specific firmware applications available in the FLASH memory circuit shall be used for upgrade purposes during the next updating procedure.

Because of backward compatibility, it will always be the peripheral interface board that is to be updated first. After successful firmware upgrading of the peripheral interface (up to three re-tries in case of errors during upgrading), the central software is upgraded.

- Press A-Z to order or cancel the upgrade of the desired firmware
- Press # to order or cancel the upgrade of the software
- Press + to order an upgrade for the software as well as all uploaded firmware versions
- Press - to cancel all upgrades
- Press ENTER or click on the ’Submit’ button to return to the main menu

After ordering the upgrade procedure for different peripheral interface boards and/or central software, the upgrade time has to be set for performing the requested upgrade procedure.

##### Menu item "E" - Exit remote upgrading

Note

If no input occurs for more than 15 minutes, the system logs out and automatically shuts down the connection

### Special considerations for the software upgrade

#### Upgrading of an ASB 150 02 Release 8 system to Release 13

1. Connect RASC to the system
2. Open the Configuration dialog
3. Save the ASB 150 02 configuration with ’Transfer to file’ (database)
4. Switch off the system
5. If the cabinet BDV 113 08 is used, change to PUB 6 if necessary
6. Update the firmware (exchange the PROMS) on all boards according to the latest compatibility list
7. Remove the CPU-D3 (CPU-D2, CPU-D) from the cabinet
8. Insert the CPU-D4 including originally delivered FLASH PROMS (e.g. with Release 13 R1A or higher)
9. Plug the desired FECU onto the CPU-D4 (if needed)

Note

CPU-D4 must have at least HW code 3 to support remote firmware upgrade and at least the FECU KDUBS 130 12/x (x=1-10)

1. Change the voice prompts on the VMU-HD
2. Insert the coldstart strap on the CPU-D4
3. Restart the system
4. When the system is up again, remove the coldstart strap on the CPU-D4
5. Set date and time of the system to a value later than 1:30 a.m., because at this time a system check is performed which might cause an interruption of step 19
6. Start up the BMS
7. Select ’Import RASC BACKUP file’ and import the previously saved ASB 150 02 data

Note

If the Release 8 system was equipped with a CPU-D, the data transfer to the system will be rejected
The datafile needs to be modified in RASC off-line mode to a CPU-D_, before it can be imported

1. Select the imported system from the selection list and connect the BMS to the system
2. Click on the system in the tree view to open the context menu and click on ’Admin’
3. Select ’Transfer to exchange: old Programming Model’ to upload the imported data to the system
4. Set command 4603 to YES
5. Restart the system

Note

The very first restart may last very long!

1. Correct date and time if necessary

#### Upgrading of an ASB 150 02 Release 9, Release 10 system to Release 13

1. Connect RASC to the system
2. Open the Configuration dialog
3. Save the ASB 150 02 configuration with ’Transfer to file’ (database)
4. Verify the mounted battery backed up memory size of the CPU-D4. The value should be higher than 256K (Click on Maintenance - System - EEPROM and read out the value ’Total EEPROM Size’)
5. Switch off the system
6. Update the firmware (exchange the PROMS) on all boards according to the latest compatibility list
7. Update the CPU-D4 with the latest software FLASH PROMS e.g. with Release 13 R1A or higher
8. Replace the existing FECU of the CPU-D4 with KDUBS 130 13 / x (x=1-10) if needed

Note

CPU-D4 must have at least HW code 3 to support remote firmware upgrade and at least the FECU KDUBS 130 12/x (x=1-10)

1. If the battery-backed-up memory size on the CPU-D4 is lower than 256KB, an additional 256 KB RAM
   (KDYBS 101 02 /1) has to be mounted
2. Change the voice prompts on the VMU-HD
3. Insert the coldstart strap on the CPU-D4
4. Restart the system
5. When the system is up again, remove the coldstart strap on the CPU-D4
6. Set date and time of the system to a value later than 1:30 a.m. because at this time a system check is performed which might cause an interruption of step 17
7. Start up the BMS
8. Select ’Import RASC BACKUP file’ and import the previously saved ASB 150 02 data
9. Select the imported system from the selection list and connect the BMS to the system
10. Click on the system in the tree view to open the context menu and click on ’Admin’
11. Select ’Transfer to exchange: old Programming Model’ to transfer the imported data to the system
12. Set command 4603 to YES
13. Restart the system

Note

The very first restart may last very long!

1. Correct date and time if necessary

#### Upgrading of an ASB 150 02 Release 11 or Release 12 system to Release 13

1. Connect the BMS to the system
2. Click on the system in the tree view, to open the context menu and click on ’Admin’
3. Select ’Transfer to database’ (enable ’Load Configuration Data’ and ’Load Terminal Types’) to save the
   ASB 150 02 configuration
4. Upgrade thre the firmware on all boards according to the latest compatibility list either by exchanging the EPROMS (Release 11 systems) or by using the remote upgrade facility. (Use the procedures described in chapter Remote upgrading of system software and firmware of BTU-B2, BTU-D, ELU-D3, MFU and Remote upgrading of the IPU)

Note

As the upgrade procedure requires a coldstart, upgrading must not be performed via remote modem connection.

Note

CPU-D4 must have at least HW code 3 to support remote firmware upgrade and at least the FECU KDUBS 130 12/x (x=1-10)

1. Upload the latest software to the CPU-D4 (use the procedures described in chapter Remote upgrading of system software and firmware of BTU-B2, BTU-D, ELU-D3, MFU)
2. Insert the coldstart strap on the CPU-D4
3. Change the voice prompts on the VMU-HD/MFU
4. Wait until the defined upgrade time is reached. The system automatically performs a restart.
5. When the system is up again, remove the coldstart strap on the CPU-D4
6. Replace the existing FECU of the CPU-D4 with KDUBS 130 13 / x (x=1-10) if needed
7. Set date and time of the system to a value later than 1:30 a.m. because at this time a system check is performed which might cause an interruption of step 16
8. Start up the BMS
9. Connect the BMS to the system
10. Click on the system in the tree view to open the context menu and click on ’Admin’.
11. Select ’Transfer to exchange: old Programming Model’ to transfer the transfer the previous data to the system.
12. Set command 4603 to yes
13. Restart the system

Note

The very first restart may last very long!

1. Correct date and time if necessary

#### Updating of an ASB 150 02 Release 13 system with the latest software revision (e.g. R1A to R1C)

1. Upload the firmware on all boards according to the latest compatibility list. (Use the procedures described in chapter Remote upgrading of system software and firmware of BTU-B2, BTU-D, ELU-D3, MFU and Remote upgrading of the IPU
2. Upload the latest software to the CPU-D4 (use the procedures described in chapter Remote upgrading of system software and firmware of BTU-B2, BTU-D, ELU-D3, MFU)

### Remote upgrading of the IPU

Compared to the remote upgrading of the Central Software, BTU-B2, BTU-D, ELU-D3, MFU, the IPU cannot be upgraded via the CPU-D4. The IPU uses its own LAN connection to upload a new application image (firmware) onto the Compact Flashcard via FTP (File Transfer Protocol). The connection to the IPU can be built up from the customer´s Intranet as well as from the Internet.

Other than in the remote upgrading of the Central Software, BTU-B2, BTU-D, ELU-D3 or MFU, the binary file will be placed directly onto the Compact Flashcard without any conversion.

#### Requirements

##### LAN/Firewall Configuration

In order to get in touch with the IPU also from the Internet, the customer‘s LAN system administrator has to open the specific path to the IPU or provide a modem entry point to the customer’s LAN.

#### Install the IPU firmware files on the BMS Server

The latest binary firmware files will be provided by your local Ericsson Support Centre.

Download the required application image into a common directory on your PC. The available files are normally compressed, and after extraction the following IPU files are available:

Example: IPU Firmware R2A

File name | Function
readR2A.htm | This file contains information on the application image revision.
IPU_R2A.bin | This binary file contains the application image of the IPU

##### To install the IPU firmware files on the BMS Server use following procedure:

1. Start up the BMS
2. Open the Tools Dialog
3. Click on IPU Firmware Upgrade

1. Click on ’File Manager’

- The file manager shows all available *bin, *me and generated *.txt files.
  Click on ’Delete’ if you do not need specific files any longer

1. Click on ’Browse’ to import the required application image for the upgrading (only *.bin).

#### Uploading the application image onto the Compact Flash card of the IPU

1. Select IPU Firmware Upgrade
2. Select the desired System and click on ’Connect’

Note

The connection settings of the desired system must be set to Connection Type ’IPU’

1. When the connection is established the following screen will pop up

- According to the picture above, the application image R1C and R2A are currently stored on the
  compact Flash card.

1. Click on the connected system in the tree view to open the context menu
2. Click on the button ’Upload Image’
3. Click on the radio button to select the desired file
4. Click on the button ’Upload’ to transfer the file to the Compact Flash card of the IPU

#### Verify the validity of the uploaded application image

Before the new application image is set to ’active’ on the IPU, it should be verified whether the file is a valid application image.

1. Click on the connected system in the tree view to open the context menu
2. Click on the button ’Check Image’
3. Click on the radio button to select the desired application image
4. Click on the button ’check Image’ to verify whether the application image has been transferred correctly
5. If you get a negative confirmation, you should remove the file again from the Compact Flash card

#### Multiple application images on the Compact Flash card

Especially when running field trials with preliminary application image revision it make sense to keep the previously released revision also on the the Compact Flash Card.

1. Click on the connected system in the tree view to open the context menu
2. Click on the button ’Set active Image’
3. Click on the radio button to select the desired application image
4. Click on the button ’Set Active’ to mark the selected image, as the active one for the next board restart

Note

If no specific file was set as active file, the IPU will take by default the file with the lastest date information.

#### Remove unused application images

If you have no need for multiple application images on the Compact Flash card, you can remove all the unused ones.

1. Click on the connected system in the tree view to open the context menu
2. Click on the button ’Remove Image’
3. Click on the radio button to select the desired file

Note

You must at least keep one application image for proper operation

1. Click on the button ’Remove’ to delete the selected file on the Compact Flash card.

#### Finalise the upgrade procedure

In order to activate the application image, the IPU has to be restarted

1. Click on the connected system in the tree view to open the context menu
2. Click on the button ’Restart IPU’

Revision: J © Ericsson Enterprise 2003