COMMON TAB Number: 2013-20

Upgrading iStar Edge Firmware

BACKGROUND:

We have identified a potential issue with older firmware on the iSTAR Edge product. It may
not reboot after a power outage. We recommend that all iStar Edge units should be
upgraded from any previous firmware version to firmware 5.2.5.19805.

SET UP
The necessary files are located at ftp.swhouse.com. A username and password are required to
access the site and can be obtained by contacting Software House Technical Support. Once
acquired, go to ftp.swhouse.com and select Public. Then select Firmware, then iStar Edge, and finally
EdgeUtility. Download the folder and its contents to the desktop. This can be done by selecting Page
in the top right corner of Internet Explorer, and selecting Open FTP Site in Windows Explorer. Then
right click the EdgeUtility folder, select copy, and paste it on the desktop.

What You Will Need:

1. iStar Edge(s)
2. EdgeUtility folder from ftp site containing:
a. Folder containing files for iStar Edge diagnostics (named edge_flash_test)
b. ICU.exe
c. Firmware BOOT file (5.2.5.19805.BOOT.i4), full firmware file (5.2.5.19805.i4)
3. Network
4. Computer with Ethernet capability
5. Check the note at the end of this document to make sure the discover.ini file is set up
according to the type of network and database you are connecting to before starting this
procedure.
6. iStar Edge Installation and Configuration Guide UM_236 (for reference)

SOLUTION:
You will want to refrain from power cycles to the iSTAR Edge at this point as this can trigger the
underlying issue pointed out in the Background section of this TAB.
(Note: If the iStar is already powered, do not remove or change the power)
Procedure:
1. If iStar Edges are on an existing network run ICU.exe (Password: manager). Make sure that
the iStar Edge(s) connected to the network show up in the list of controllers. You can identify
the controller(s) from the last six digits of its MAC address in the ICU program.
a. If controllers are not showing up in the list of devices, exit the program, check
Ethernet connections, and restart ICU to redo step 3.
2. Run ICU.

Software House 6 Technology Park Drive • Westford, MA 01886 USA 1

Tele: 978 577 4000 • Fax: 978 577 4392 • www.swhouse.com
 3. Close the ICU program.
a. Note: ICU needs to be shut down in order for the edge utilities to run properly.

4. Open the EdgeUtility folder on your desktop and then open the edge_flash_test folder.
5. Once in this folder, find the istar_discover.exe file and double click it.
This will open and run the Discover tool shown similar to Fig.1 or Fig. 2 below.
6. This program discovers your iStar Edge(s) that you have connected to the same network as
the computer. The program will list the MAC address and Name of the controller in Command
Prompt. The program is finished when the connected iStar Edge(s) is listed in Command
Prompt. DO NOT exit the Command Prompt at this point.
a. The program continuously rediscovers the controllers connected to the network, so
ignore single MAC addresses that show up. Only look for MAC addresses listed after
“Found New Edge Panel Hardware Address:00:00:x:x:xx:xx Name:xxxxxxxx”
Fig. 1: istar_discover.exe Output (single controller)
Fig. 2: istar_discover.exe Output (multiple controllers on network):

Repeated MAC Addresses

Software House 6 Technology Park Drive • Westford, MA 01886 USA 2

Tele: 978 577 4000 • Fax: 978 577 4392 • www.swhouse.com
 7. In the edge_flash_test folder, make sure that the program created a file called
edge_addresses.xml within the folder.
8. Open edge_addresses.xml. Look at the list of devices that were discovered, and make sure
that the controllers connected to the network are present.
Fig.3 : edge_addresses.xml (single controller)

9. If all controllers present, close .xml file. You can now close the CMD Prmpt.
10. Next, go back into the edge_flash_utility folder and double click on flash_test.exe. this will
run and then create a folder called:
#########_edge_test_results.xml.
a. This program may take a few minutes to compile the full .xml file depending on the
size of your network and the number of iSTAR Edges you have. Once the program is
completed, the .xml file is created, the CMD Prmpt will close. This program is
running diagnostics on the iSTAR Edges to ensure the new firmware can be flashed
via ICU.
11. Open the newly created .xml file. Read through it carefully to ensure that the iStar Edge(s)
have passed all of the following diagnostic tests: fboot, eboot, ui_checksum, kgi_checksum.
(see Fig.4 below). If so, close the .xml file and proceed to step 12.

Example of iSTAR Edge that Passes:

Fig.4: #########_edge_test_results.xml (single controller)

Software House 6 Technology Park Drive • Westford, MA 01886 USA 3

Tele: 978 577 4000 • Fax: 978 577 4392 • www.swhouse.com
 Example of iSTAR Edge that Fails:

Fig.5: #########_edge_test_results.xml for failed fboot and eboot (single controller)

(Note: you may see 1 or 2 bad blocks detected, this is considered normal. What you do not want to
see is bad blocks in quantity of 100’s or greater.)

***If an iStar Edge has failed any of the four diagnostic tests (fboot, eboot,
ui_checksum, or kgi_checksum), please refer to the REPAIRS section on the
last page.**

12. The iStar Edge controllers are ready to have the firmware flashed to them using ICU.
a. First flash the controller with the BOOT image (5.2.5.19805.BOOT.i4), and then the
main image (5.2.5.19805.i4).

Software House 6 Technology Park Drive • Westford, MA 01886 USA 4

Tele: 978 577 4000 • Fax: 978 577 4392 • www.swhouse.com
REPAIRS

Repairs must be done in this order, or controller may become unrecoverable.

a) fboot: if the fboot failed the flash test, then run flash_test.exe again (step 10). If fboot passes the
second time, move on to eboot repair. If the fboot fails a second time, then the controller is
defective and needs to be returned to Tyco Security Products following the standard RMA
process.

b) eboot: if the eboot failed the flash test, then run flash_test.exe again (step 10). If passes the
second time, move on to kgi_checksum_test repair. If the eboot fails a second time, then the
controller is defective and needs to be returned to Tyco Security Products following the standard
RMA process.

c) kgi_checksum_test: if the kgi_checksum_test failed the flash test, then you must flash the
controller with the BOOT image via ICU, and rerun flash_test.exe. This must be done before the
main image can be flashed to the controller.

d) ui_checksum_test: if the ui_checksum_test failed the flash test, then flash the controller with the
main image of the firmware via ICU and rerun flash_test.exe

**Note: Do not remove power at any time BEFORE or DURING the repair procedure.

***Note: In the edge_flash_test folder, the discovery.ini file is set up as; database=False,
and network=True. This is set for a typical database and network. You will need to
adjust these two parameters based on the type of database and network at the site.
Instructions are in the discovery.ini file if you need to adjust these two parameters.

If you have any questions regarding this Technical Advisory Bulletin, please contact Software House Technical Support.
North America & Latin America: Toll Free: 800-507-6268, Option 3 or International: 561-912-6259, Option 3
EMEA: Toll Free: +800 CALLTYCO or (+800-2255 8926), Direct: +31 475 352 722, Hours: 8 am to 6 pm CET
[email protected]
Asia/Pacific: Toll free: +800-2255 8926, Direct: +86-21-61638640, China Hotline: 400-6858-226, India: 18001082008,
Hours: 9 am to 5 pm CCT Email: [email protected]
Complete Support Contact List
Information furnished by Software House is believed to be accurate and reliable. However, no responsibility is assumed by
Software House for its use, nor any infringements of other rights of third parties which may result from its use. No license is
granted by implications or otherwise under any patent rights of Software House.

Software House 6 Technology Park Drive • Westford, MA 01886 USA 5

Tele: 978 577 4000 • Fax: 978 577 4392 • www.swhouse.com