XTORE SAS JBOD Firmware Upgrade Guide

XTOER SAS JBOD Firmware Upgrade Guide:

Last Updated: NOV-22nd -2006

This guide will give you an idea to identify your currently SAS expander version. Please read it careful before choosing a correct latest firmware to upgrade your system(s).

A. Hardware Identify:

1. 3U 16-bay SAS JBOD firmware

2. 2U 24-bay SAS JBOD firmware

3. Other Notes

B. Firmware Upgrade Procedure

1. In-band Firmware Upgrading

2. Out-of-band Firmware Upgrading

Firmware Files content and identification:

3U 16-bay SAS JBOD firmware table Back to top

Caution: If the system firmware was 1.09a with redundant JBOD I/O modules, you need to have one I/O module removed before the process. Please remove one expander module before the firmware upgrade process. The I/O module will be corrupted or end up with unexpected result without following the instruction. You can upgrade the other I/O module following same caution.

After unzipped the latest firmware, there are many files for different models. please check the following the table.

For the model of 3U 16bays SAS JBOD, the firmware table as the following:

Firmware File Archive

Contents

Version

ECx-7153x-1.0xx.zip

Module Type	Backplane Version	Chip Version	Firmware File Name
JBOD Module	A1	VSC-7153B	em53b-1.0xx-bpA1_16d.s3r (3U16bays SAS JBOD)
JBOD Module	A2	VSC-7153B	em53b-1.0xx-bpA2_16d.s3r (3U16bays SAS JBOD)
JBOD Module	A1	VSC-7153C	em53c-1.0xx-bpA1_16d.s3 r(3U16bays SAS JBOD)
JBOD Module	A2	VSC-7153C	em53c-1.0xx-bpA2-16d.s3r (3U16bays SAS JBOD)

1.0XX

Tips: You may use a RS-232 console to check your currently firmware.

Using the 'stat' command of RS-232 console to list information of system modules:

For the 1.07x or earlier version:


	--> stat

Vitesse Semiconductor VSC7153

Status: Status OK CRC: F9BC Versions: Module Vers Description Date Time -------- ----- --------------------------- ----------- -------- PM(7153) 1.07B AIC JBOD-16 SAS_ECM_A2 Jan 11 2006 15:37:21 libsyssv 03.27 System Services Library Aug 12 2005 09:41:18 libsmp 01.01 SMP Diagnostic Library Aug 12 2005 09:40:51 sesssp 01.02 SSP SES Diagnostic library Aug 12 2005 09:40:53 libSMP 01.02 SMP Transport Library Aug 12 2005 09:40:59 libPHY 01.03 PHY Transport Library Aug 12 2005 09:40:55 libSSP 01.03 SSP Transport Library Aug 12 2005 09:41:09 libGUI 00.02 GUI Transport Library Aug 12 2005 09:41:06

In the PM(715x) line. you can check the chip ID (715x), Product ID (JBOD-16 SAS_ECM), Backplane ID (A2) FW revision ID (1.07B) and date code of this firmware. ECM means EC JBOD module

Starting the 1.09a Firmware you may use the command line to check your expander Backplane and Chip version.

Naming scheme of SES 'Product ID' field of all models are revised to ease human identification.
For example:
1. 3U16 JBOD based on 7153-B with a V2 version of backplane is 'EM16-53B-01A2'

The SES ' ProductRev ' field is now assigned firmware version instead of the revision of expander module and backplane.
Note: the console cmd 'ProductRev get' will always report board (expander module and backplane) revision.

--> ProductId get
Product Id: EM16-53B-01A2

--> ProductRev get
Product Rev: 01A2 (expander module and backplane revision)

--> VendorId get
Vendor ID: AIC/XTORE

According to above information the expander firmware will be: em53b_1.0xx-bpA2_16d.s3r

3U-16bays JBOD Module board with VSC-7153"B" chip and A2 version of HDD backplane

2U 24-bay SAS JBOD firmware table Back to top

After unzipped the latest firmware, there are many files for different models. please check the following the table.

For the model of 2U 24bays SAS JBOD, the firmware table as the following:

Firmware File Archive

Contents

Version

ECx-7154x-1.XXb.zip

Module Type	Backplane Version	Chip Version	File Name
JBOD Module	A0	VSC-7154B	em54b-1.0xx-bpA0.s3r (2U24bays SAS JBOD)
JBOD Module	A1	VSC-7154B	em54b-1.0xx-bpA1.s3r (2U24bays SAS JBOD)
JBOD Module	A0	VSC-7154C	em54c-1.0xx-bpA0.s3r (2U24bays SAS JBOD)
JBOD Module	A1	VSC-7154C	em54c-1.0xx-bpA1.s3r (2U24bays SAS JBOD)

1.0XX

Tips: You may use a RS-232 console to check your currently firmware.

Using the 'stat' command of RS-232 console to list information of system modules:

For the 1.07x or earlier version:


	--> stat

Vitesse Semiconductor VSC7154

Status: Status OK
CRC: F9BC
Versions:
 Module  Vers         Description            Date       Time
-------- ----- --------------------------- ----------- --------

	PM(7154) 1.07B AIC JBOD-24 SAS_ECM_A2  Jan 11 
		2006 15:37:21
libsyssv 03.27 System Services Library     Aug 12 2005 09:41:18
libsmp   01.01 SMP Diagnostic Library      Aug 12 2005 09:40:51
sesssp   01.02 SSP SES Diagnostic library  Aug 12 2005 09:40:53
libSMP   01.02 SMP Transport Library       Aug 12 2005 09:40:59
libPHY   01.03 PHY Transport Library       Aug 12 2005 09:40:55
libSSP   01.03 SSP Transport Library       Aug 12 2005 09:41:09
libGUI   00.02 GUI Transport Library       Aug 12 2005 09:41:06

In the PM(715x) line. you can check the chip ID (715x), Product ID (JBOD-24 SAS_ECM), Backplane ID (A2) FW revision ID (1.07B) and date code of this firmware. ECM means EC JBOD module

Starting the 1.09a Firmware you may use the command line to check your expander Backplane and Chip version.

Naming scheme of SES 'Product ID' field of all models are revised to ease human identification.
For example:
1. 3U16 JBOD based on 7153-B with a V2 version of backplane is 'EM16-53B-01A2'

--> ProductId get
Product Id: EM24-54C-01A0

--> ProductRev get
Product Rev: 01A0 (expander module and backplane revision)

--> VendorId get
Vendor ID: AIC/XTORE

According to above information the expander firmware will be: em54c_1.0xx-bpA0.s3r

2-24bays JBOD Single Module board with VSC-7154 "C" chip and A0 version of HDD backplane

Other Notes: Back to top

From the experience of releasing 1.07A to 1.07B, We decided that we need stick to a 3-stages release process:

Beta stage: for internal test only.
- There may be more than one beta version for a final stable release; for example, there may be 1.07c, 1.07d, 1.07e and so on until we all fee it's good enough to be released publicly.
- In this stage, the last character of the version stamp will always be in lower case.
RC stage: Release Candidate version; may be circulated in our branches or big OEM.
- It is the version considered good enough to be released publicly but still needs final approving from test team.
- Usually, the difference between this version and the last beta version is the last character of the version stamp; the last character of its version stamp will always be in upper case.
  
  For example, if we need to go through 1.07c, 1.07d and 1.07e to get the next stable 1.07 version, the RC version will be 1.07E.
Release stage: the formal release. It is the approved RC version.
- It will usually be just the RC version copy to publicly accessible site.

Note:

Ensure only insert one I/O module for JBOD firmware updating. the other has to be removed.
Starting from 1.07A, 8 Mbit EEPROM chip is required for proper operation.
Don't ever try to upgrade to this version if your current EEPROM is 4 Mbit version (ST-Micro m25p40)

4Mbit and 8Mbit EEPROM
- Unless you have already upgraded to early beta of 1.07 (1.07a or 1.07b, the 'a/b' in lower case), you must issue the following console command prior to actual download operation:

o        tRomSize  8

You may like to use the 'fwcfg' command to check if the ROM configuration is correctly set up. The response of 'fwcfg' should look similar to following:

ROM Location

Primary  : BFC00000

Secondary: BFC80000

If the address at the 'Secondary' line is BFC40000 then you either didn't issue the 'tRomSize' command correctly or your version of FW is too old and doesn't support the 'tRomSize' command. Try the command again or get a preprogrammed chip.

How to upgrade firmware? back to top

This chapter describes how to upgrade firmware using either In-band Windows® GUI utility or out-of-band RS-232 console via the x-modem protocol. Using GUI utility to upgrade is recommended.

In-band Firmware Upgrade back to top

The following steps are recommended as a step-by-step to upgrade firmware with the “FWLOAD.EXE” executable application.

1. Apply power to the SAS JBOD.
2. Using a PC with a SAS Host Adapter (updated with latest firmware and drivers), connect the JBOD with the provided SAS cable.
3. Boot up the PC with the SAS Host Adapter.
4. After logging into Windows, if the SSP virtual PHY is enabled with the proper firmware loaded into the SAS Expander device of the JBOD, then the “Found new hardware” Windows will appear, see Figure 1.

Figure1. SAS device detected in Windows

5. The “Found New Hardware Wizard” window will start, see Figure 2.

Figure2. Found New Hardware Wizard looking for SAS Expander driver

6. When the Found New Hardware Wizard asks to install drivers for the SAS Expander device, click on the “Cancel” button to bypass driver installation, see Figure 3.

Figure3. Found New Hardware Wizard asks to install drivers for SAS Expander

7. Once Windows has completed the logon process, save the latest firmware image to a known location on the PC.
8. Copy the “FWLOAD.EXE” executable application from the provided CD to a known location on the PC, see Figure 4.

Figure4. “FWLOAD.EXE” executable application

9. Run the “FWLOAD.EXE” executable application; the application will proceed with detecting the SAS devices connected to the Host PC.
10. After the application detects the SAS devices, the Firmware Loader window will be displayed, see Figure 5.

Figure5. Firmware Loader window

11.Click the “Browse” button and locate the latest firmware image that was saved to the PC, see Figure 6.

Figure6. Firmware Loader window with firmware selected

12. After the firmware image has been selected, click the “Update” button to start the SAS In-Band firmware update routine.
13. A progress bar will be shown to indicate the status of the firmware update routine.
14. After 1 to 2 minutes, the firmware update will be completed, and the Firmware Loader window will be displayed again, see Figure 5.
15. Close the Firmware Loader application window.
16. For continued proper operation, shutdown and restart the SAS JBOD, and restart the host PC.
The firmware update procedure should now be completed with the “FWLOAD.EXE” executable application. If there are any questions, or if further information is required, please contact your local dealer or sales representative.

SAS Out-of-band Firmware Upgrade Back to top

In case you failed the main firmware ROM during the FWLOAD.EXE upgrading, there is another way to upgrade via the serial port.

Caution: If the system firmware was 1.07B with redundant JBOD modules. Please remove second expander module before the firmware upgrading. it's only can support single module firmware updating each time by RS-232 console. If it doesn't remove the secondary expander, it could be causing a seriously non-recoverable failure or an upgrade failure issue. If so, the only way is that the EEPROM needs to be replaced.

Perform Preliminaries:

1. provided serial cable (DB9 to stereo mini jack) x 1
2. HyperTerminal 6.3 or earlier version (with settings 9600, none, 8, 1, none)
3. The IO module (To disconnect all the SAS connectors be recommended)

Procedure:

1. Power on the JBOD (the IO module without SAS connectors connected)
2. Press “Enter” Twice for the arrow signal comes out
3. arrow “-->” command line for the system ready
4. --> stat to check the current latest firmware
5. --> fwupdate to start upgrading

7. To select Transfer – "Send File" of the menu bar

8. To select a correct firmware

9. To select “ XModem” protocol and click “Send” to transfer firmware

10. Start firmware upgrading

11. After completely done firmware updating. Restart the JBOD
12. Ensure the latest firmware updated is successful by entering "stat" Command

Back to top