Mellanox Firmware Tools (MFT) User`s Manual
Contents
1. 20 3 2 flint Synopsis 20 ddl SWE Descrip onse bari A ds 20 322 Command Description nie to peek eee se a Ree bale lato 23 3 2 3 Additional Debug Production Commands 0000 ccc eens 27 Chapter 4 spark InfiniScale III Firmware Burning Tool oooooooooo 37 4 1 Overview 37 4 2 spark 37 AQu SPA SYNOPSIS sas sp n elene ade dns a ADA eno 37 Appendix A PSID Assignment 40 A l PSID Field Structure 40 A 2 PSID Assignment and Integration Flow 40 Appendix A Flow Examples mlxburn 41 Appendix A Debug Utilities 43 A l itrace Utility 43 A 2 mstdump Utility 45 A 3 mlxi2c Utility 46 AA4 12c Utility 47 A 5 mget temp Utility 49 Appendix A In Band Access to Multiple IB Subnets 50 Mellanox Technologies 1 J Rev 1 50 Appendix A MTUSB 1 USB to I2C Adapter 52 A 1 Overview 52 A 2 Hardware Installation 53 A 3 Software Installation 53 2 Mellanox Technologies Rev 1 50 Revision History Printed on December 29 2011 Table 1 Revision History Table Date Revision Description December 2011 1 50 Added the following note This step in not required in Windows to the following sec tions e Section 1 3 MFT Access to Hardware Devices on page 8 e Section C 1 22. dev mst SW MT48436 lid 0x0005 mlx4 1 2 You can use the above device names with the MFT tools Mellanox Technologies 51 J Rev 1 50 spark InfiniScale IIl Firmware Burning Tool Appendix E MTUSB 1 USB to I2C Adapter E 1 Overview The MTUSB 1 is a USB to C bus adapter This chapter provides the user with hardware and soft ware installation instructions on machines running Linux or Windows operating systems Figure 3 MTUSB 1 Device MTUSB 1 Device I2C Cable E 1 1 Package Contents Please make sure that your package contains the items listed in Table 7 and that they are in good condition Table 7 MTUSB 1 Package Contents MTUSB 1 device USB to I2C bus adapter USB cable USB A to USB B 1 8m I2C cable 9 pin male to male cable 1 5m 9 pin female to 3 pin small large 0 3m E 1 2 System Requirements The MTUSB 1 is a USB device which may be connected to any Personal Computer with a USB Host Adapter USB Standard 1 1 or later and having at least one USB connection port E 1 3 Supported Platforms MTUSB 1 supports the same platforms that are supported by the MFT tools package 52 Mellanox Technologies Rev 1 50 E 2 Hardware Installation To install the MTUSB 1 hardware please execute the following steps in the exact order I Connect one end of the USB cable to the MTUSB 1 and the other end to the PC 2 Connect one end of the I2C cable to the MTUSB 1 and the other end to
3. I Read two bytes from address 0 of target I2C device at address 0x56 gt i2c a 1 d 2 dev mst mtusb 1 r 0x56 0x00 0000 2 Write two bytes to the address above then read them gt 12c a 1 d 2 dev mst mtusb 1 w 0x56 0x00 0x1234 gt 12c a 1 d 2 dev mst mtusb 1 r 0x56 0x00 3412 3 Read as separate 16 bytes in hexadecimal format starting from address 0 of the target device above gt 126 a 1 x 16 dev mst mtusb 1 r 0x56 0x00 12340000000000000000000000000000 48 Mellanox Technologies Rev 1 50 C 4 2 Exit Return Values The following exit values are returned e 0 successful completion e gt 0 an error occurred C 5 mget_temp Utility The mget temp utility reads the hardware temperature from Mellanox Technologies devices with temperature sensors ConnectX ConnectX 2 ConnectX 3 BridgeX devices and 4th gener ation switches and prints the reading in Celsius degrees C 5 1 Operation The MST driver must be started prior to running mget temp To start mget temp I Start the MST driver mst start or mst restart 2 Run mget temp with the following command line syntax mget temp OPTIONS where OPTIONS are h Print this message d lt dev gt mst device name 1 activate and initiate thermal diodes for temperature measurement intru sive On some systems the thermal sensors are not activated by default To initiate the thermal sensors run mget temp 1 once
4. gt A device that is burnt with blank GUIDs MACs will not boot as a functional network device as long as the GUIDs MACs are not set A Flow Example I Generate a striped image with blank guids gt mlxburn fw fw ConnectX2 rel mlx MHQH29B XTR Al ini wrimage fw ConnectX2 rel bin striped image blank guids I Generating image I Image generation completed successfully 2 Burn the image to a flash using an external burner 3 Optional After assembly query the image on flash to verify there are no guids on the device eee dew Mc ee 2 Ga image type Conmecex FW Version 253 Device ID 26428 Chip Revision BO Description Node F re Boz Sys image CURDS bi IE Ne IE EEE CIE EE WE ISIE in 32 Mellanox Technologies Rev 1 50 MACs IE JE AE IC AE ENE JE Rie EE JE AE HON EE EE EE AE IEA Se Ede IE Board ID n a MT 0D80110009 VSD n a PSID MT 0D80110009 W GUIDs MACS values and their CRC are not set 4 Set the correct GUIDs Since the image is with blank GUIDs this operation takes less than I second gt flint d dev mst mt26428 pci cr0 guid 0x0002c9030abcdef0 mac 0x0002c9bcdef1 sg 5 Query the image on flash to verify that the GUIDs are set correctly gt flint d dev mst mt26428 pci cr0 q Image type ConnectX FW Version DO Device ID 26428 Chip Revision BO Description Node Porti Rote Sys image GUIDs 0002c9030abcdef0 0002c9030abcdefl 0002c9030abcdef2 0002
5. Set the output value of the given GPIO pin set fan lt fan name gt lt Tach num gt lt power persent gt Set the power percent of the given fan set power lt module name gt lt off on gt Power on off the specified module Supported modules MTS3610 LEAF MTS3610 SPINE set led lt led name gt lt color gt Change the color of the specify led to the given color scan Scan the 12c slave addresses show lt info_type gt Show information about the system or specific subsystem module related to m flag The information types are devs v List the 12c components v adds detailed information to the list modules List the detachable subsystems modules temp The temperatures of the components ADM1024 LM075 PCF8591 volt The voltage values of ADM1024 PCF8591 ports The present qsfp ports on the system fans The speed of fans power The power voltage current values of the power supplies slot num The slot number of the system only for FJ SWITCH leds The current colors of the LEDs inventory The inventory of the present modules Examples I Point to an InfiniScale IV device to enable accessing it directly by firmware utilities mlxi2c d dev mst mtusb 1 p IS4 PRIM 2 Display the temperature values of InfiniScale IV or BridgeX temperature sensors in the sys tem mlxi2c d dev mst mtusb 1 show temp 3 Display the addresses of all I2C accessible devices mlxi2c d dev mst mtusb 1 scan C 4
6. 25218 For MT25208 InfiniHost II Ex in MemFree mode HCA cards Lion Mini family 25204 For MT25204 InfiniHost HI Lx HCA cards Tiger Cheetah fami lies 25408 For MT25408 ConnectX Dual 10Gb s InfiniBand VPI Port Adapter Cards 25418 For MT25408 ConnectX Dual 20Gb s InfiniBand VPI Port Adapter Cards 26418 For MT25408 ConnectX Dual 20Gb s InfiniBand VPI Port Adapter Cards with PCI Express Gen 2 26428 For MT25408 ConnectX IB Dual 40Gb s InfiniBand VPI Port Adapter Cards with PCI Express Gen 2 25448 For MT25408 ConnectX EN NIC cards 26448 26468 For MT25408 ConnectX EN 10GigE cards with PCI Express Gen 2 26478 For MT25408 ConnectX 2 EN 40GigE cards with PCI Express Gen 2 25458 For MT25458 ConnectX EN 10GBASE T cards 26458 For MT25458 ConnectX EN 10GBASE T cards with PCI Express Gen 2 25438 For MT26438 ConnectX 2 VPI w Virtualization 43132 For MT43132 InfiniScale based switch systems 47396 For MT47396 InfiniScale III based switch systems 48436 For MT48436 InfiniScale IV based switch systems IB SDR Mellanox Technologies 15 J Rev 1 50 mlxburn FW Image Generator Burner 48437 For MT48436 InfiniScale IV based switch systems IB DDR 48438 For MT48436 InfiniScale IV based switch systems IB QDR 64102 64122 For MT64102 BridgeX based gateway systems 1016 For MT1016 PhyX devices 51000 For MT58100 SwitchX based switch systems 4099 For MT27500 Connec
7. Indicate that the target EEPROM to be burnt is for an InfiniScale MT43132 device If this option is not specified the target EEPROM is for an InfiniScale III MT47396 device Not supported for In band access Affected commands burn is3_12c lt 12c_addr gt Provides the I2C address of the switch device If this flag is not specified then the the default address for Mellanox switch devices is Ox6c pe_12c lt 12c_addr gt Provides the I2C address of the primary EEPROM By default this address is read from the Mellanox switch device Use this flag only if the switch device is not accessible Mellanox Technologies 37 J se_12c lt i2c addr gt h elp hh nofs s ilent sim y es V The commands of spark are b urn qluery v erify bb ri rb Rev 1 50 spark InfiniScale III Firmware Burning Tool Provides the I2C address of the secondary EEPROM By default this address is read from the Mellanox switch device Use this flag only if the switch device is not accessible Prints this help message and exits Prints an extended command help Do not burn the firmware image in failsafe mode Print errors only Affected commands burn Simulates an EEPROM burn without actually writing the EEPROM Use this flag to compare the image currently on the EEPROM with the given image file Affected commands burn Non interactive mode Assume the answer to all questions is
8. gt rpm e mft kernel mft 1 4 3 Install MFT On Windows OS I Download the Windows MFT MSI from http www mellanox com products management tools php 2 Double click the MSI and follow the instructions for installation 10 Mellanox Technologies Rev 1 50 1 4 4 Uninstall MFT Windows To uninstall WinMFT perform one of the following I Activate the Add or Remove Programs utility of Windows and click the Remove button of the MFT tool entry 2 Click start gt Programs gt Mellanox gt WinMFT gt uninstall 1 4 5 Install MFT On VMware ESX Server 3 5 I Download the mstflint for VMware ESX Server 3 5 RPM from the Mellanox Management Tools webpage http www mellanox com products management_tools php 2 Download the MFT for VMware ESX Server 3 5 RPM from the Mellanox Management Tools webpage 3 To install the RPMs run DERISO gt rpm 1 mft X X Xvmware lt kernel version gt rpm 1 4 6 Uninstall MFT VMware ESX Server 3 5 1 To uninstall MFT run Pe Aeon IT gt Col e MS 1 5 Reference Documents and Downloads e To download firmware images and their release notes see http www mellanox com under Firmware downloads e Mellanox OFED for Linux is a software stack that can be downloaded from http www mellanox com gt Products gt InfiniBand SW Drivers e Mellanox WinOF for Windows is a software stack that can be downloaded from http www mellanox com gt Products g
9. Operation on page 43 e Section C 2 1 Operation on page 45 e Section C 3 1 Operation on page 46 e Section C 4 1 Operation on page 47 e Section E 3 Software Installation on page 53 July 2011 1 40 e Updated Section 1 1 Supported Operating Systems on page 6 e Updated Section 5 Supported Mellanox Devices on page 8 e Updated Mlxburn format e Added Section 2 4 2 SwitchX Switch Examples on page 16 e Added Section 3 2 3 4 Disabling enabling Access to the Hardware on page 35 e Updated Section 3 flint Firmware Burning Tools on page 20 e Updated Section 3 2 2 1 Burning a FW Image on page 24 e Updated Section 3 flint Firmware Burning Tools on page 20 e Added the striped_ image flag to Section 3 2 3 1 Setting GUIDs and MACs on page 27 December 2010 1 30 e Updated table in Section 2 MFT Software Dependencies on Linux e Removed sw sys entries from the document e Added device 25438 for MT26438 ConnectX 2 VPI w Virtualization e Added Section 3 2 3 2 Preparing a Binary Firmware Image for Pre assembly Burn ing on page 32 e Added section On 4th Generation Devices on page 29 e Updated sections Install MFT On Linux OS on page 10 and Uninstall MFT Linux on page 10 e Removed section isw Utility e Added Preparing a Binary Firmware Image for Pre assembly Burning on page 32
10. Restoring signature Nose aM OK OK ind dev met 51 Image Type FW Version Rom Info Device ID Chip Revision Description GUIDs MACs Board ID Connect TOO type PXE version 3 0 0 devid 25418 proto VPI 25418 A0 Node PORLI Pore Sys image 0002c9000120d050 0002c9000120d051 0002c9000120d052 0002c9000120d053 02c90120d050 02c90120d051 VSD MT 04C0110002 34 Mellanox Technologies Rev 1 50 VoD VSD PSID MT 04C0110002 3 2 3 4 Disabling enabling Access to the Hardware The secure host feature enables ConnectX family devices to block access to its internal hardware registers The hardware access in this mode is allowed only if a correct 64 bits key is provided Examples I Set the key flint d dev mst mt26428 pci cr0 set key 22062011 Setting the HW Key OK Restoring signature OK 4 A driver restart is required to activate the new key ha 2 Access the FW while it s disable BING 0 de Not mod peca E Cannot open dev mst mt26428 pci cr0 HW access is disabled on the device i ia abi e Cle iste mie Zo Ze joi oral ye ose noble ii vo mal RN coses 3 Enable the FW flint d dev mst mt26428 pci cr0 hw access enable Enter Key 4 Disable the FW flint d dev mst mt26428 pci cr0 hw access disable 3 2 3 5 Reading a Word from Flash To read one dword from Flash memory use the following command line flint d lt device gt rw addr where device
11. in the second stage The burning process retains device specific data such as GUIDs UIDs MACs VSD and BSN Also the burn process is failsafe by default Figure 2 FW Generation and Burning Exp ROM 12 Mellanox Technologies Rev 1 50 mlxburn runs both stages by default but it may perform only one by means of command options If the wrimage is specified see Section 2 3 mlxburn Synopsis only image generation is per formed Specifying the image option skips the image generation stage and loads the provided image generated in a previous run of mlxburn using the wrimage option When generating an image file for a Mellanox InfiniScale III switch device the pro duced image file name must end with a img extension ha 2 2 1 Firmware Customization A Mellanox firmware image can be customized usually to fit a specific board type The custom ization is done by using a FW parameter set file in the image generation stage This file has a ini format Each parameter set file has a unique parameter set ID PSID which is kept in the device Flash EEPROM and allows retaining device configuration during future FW updates During a device FW update mlxburn reads the PSID from the device and uses the corresponding ini file when generating the FW image mlxburn searches for the files in the same directory of the FW release When mlxburn is used to generate an image file or when no cor
12. nofs guids 0002c9000100d060 0 0 0002c9000100d060 D 7 MT48436 InfiniScale IV switch inband firmware update a a o oe A SN oan 8 MT58100 SwitchX switch Burn the image on a blank Flash device Meaning no GUIDs MACS are currently burnt on the device therefore they must be supplied with guid guids and mac macs by the burning com mand Moreover the burn process cannot be failsafe when burning a blank Flash therefore the nofs flag must be specified gt flint d dev mst mtusb 1 i tmp fw sx bin nofs guids 000002c900002100 0 0 000002c900002100 macs 0002c9002100 0002c9002101 Db 9 MT58100 SwitchX switch inband firmware update Tone eee e Mellanox Technologies 25 J Rev 1 50 flint Firmware Burning Tools 3 2 2 2 Querying the FW Image To query the FW image on a device use the following command line Hi d deve G e To query the FW image in a file use the following command line PAE r Image e q where device Device on which the query 1s run image file Image file on which the query is run Examples a Query the FW on the device gt flint d dev mst mt25418 pciconf0 query b Query the FW image file gt tline Sl 29406 2 1 000 MO6H29 ASC Al bin query 3 2 2 3 Verifying the FW Image To verify the FW image on the Flash use the following command line flint d lt device gt v e To verify the FW image in a file use the following command line flint i lt image file gt
13. 0002c900001 0002c900002 2 The guid flag is supported by all Mellanox Technologies adapters and switch devices 16 Mellanox Technologies Rev 1 50 e Generate an MT48436 image and perform an In Band update of the device with LID 0x18 mlxburn dev lid 0x000E fw fw sx mlx e Generate and burn a new MSX6025 via I2C Set the I2C network to access the InfiniScaleIV switch mlxi2c d dev mst mtusb 1 p SX Burn the new image the flash is still blank specifying the Node GUID system GUID base MAC and Switch MAC Note that 4 guids in quotes should be specified as an argument to the guids flag The 2 middle GUIDs are ignored by SwitchX and should be set to 0 mlxburn d dev mst mtusb 1 fw fw sx mlx conf MSX6025F Al ini guids 000002c900002100 0 0 000002c900002100 macs 0002c9002100 0002c9002101 nofs 2 4 3 InfiniScale IV Switch Examples e Burn an MTS3600 switch system via I2C a Set the I2C network to access the InfiniScale IV switch mlxi2c d dev mst mtusb 1 p IS4 PRIM b Burn with quick query qq to shorten burn time mlxburn dev dev mst mtusb 1 fw fw IS4 mlx qg e Burn an MTS3600 switch system using the In Band access method mlxburn dev dev mst SW MT48438 lid 0x0003 fw fw 154 mlx e Generate and burn a new MTS3600 via I2C a Set the I2C network to access the InfiniScaleIV switch mlxi2c d dev mst mtusb 1 p IS4 PRIM b Burn the new image the flash is still blank specif
14. 1 Overview The flint Flash interface utility performs the following functions e Burns a binary firmware image to the Flash device attached to an adapter bridge or switch device e Burns an Expansion ROM image to the Flash device attached to a ConnectX Con nectX 2 adapter device e Queries for firmware attributes version GUIDs UIDs MACs PSID etc e Enables executing various operations on the Flash memory from the command line for debug production e Disables enables the access to the device s hardware registers and changes the key used for enabling This feature is functional only if the burnt firmware supports it 3 2 flint Synopsis flint switches lt command gt parameters 3 2 1 Switch Descriptions d evice lt device gt The device to which the Flash is connected Affected commands All 1 mage lt image gt Binary image file Affected commands burn verify qq Quick query the device for firmware information This operation can be specified when executing either a query or burn operation When speci fied flint will not perform full image integrity checks This may shorten execution time when running over slow interfaces e g I2C MTUSB 1 Affected commands burn query guid lt GUID gt Base value for up to 4 GUIDs which are automatically assigned the fol lowing values guid gt node GUID guid 1 gt port guid 2 gt port2 guid 3 gt system image GUID Affected c
15. T board symbol 000 Board version symbol 0001 Parameter Set Number A 2 PSID Assignment and Integration Flow To assign and integrate the new PSID to produce the new FW I Write the new FW configuration file in INI format 2 Assign it with a PSID in the format described above Use your own vendor symbol to assure PSID uniqueness If you do not know your vendor symbol please contact your local Mellanox FAE 3 Set the PSID parameter in the new FW configuration file 40 Mellanox Technologies Rev 1 50 Appendix B Flow Examples mlxburn To update an MT47396 InfiniScale III and MT48436 InfiniScale IV switch devices having a specific GUID for example 0x00000006660abcd0 or LID the following are the recommended steps to update the device firmware gt For Linux device names should be listed with the dev mst prefix For Windows no pre fix 1s required A I Make sure all subnet ports are in the active state One way to check this is to run opensm the Subnet Manager root mymach gt etc init d opensmd start opensm start OK 2 Make sure the local ports are active by running ibv_devinfo 3 Obtain the device LID There are two ways to do that a Using the mst ib add command The mst ib add runs the ibdiagnet ibnetdiscover tool to discover the InfiniBand fabric and then lists the discovered IB nodes as an mst device These devices can be used for access by other MFT tools roo
16. TECHNOLOGIES Mellanox Technologies Mellanox Technologies Ltd 350 Oakmead Parkway Beit Mellanox Sunnyvale CA 94085 PO Box 586 Yokneam 20692 U S A Israel www mellanox com www mellanox com Tel 408 970 3400 Tel 972 0 4 909 7200 972 0 74 723 7200 Fax 408 970 3403 Fax 972 0 4 959 3245 Copyright 2011 Mellanox Technologies All rights reserved Mellanox BridgeX ConnectX CORE Direct InfiniBridge InfiniHost InfiniScale PhyX SwitchX Virtual Protocol Interconnect and Voltaire are registered trademarks of Mellanox Technologies Ltd FabricIT MLNX OS and Unbreakable Link are trademarks of Mellanox Technologies Ltd All other trademarks are property of their respective owners Mellanox Firmware Tools MFT User s Manual 2 Mellanox Technologies Document Number 2329 J Rev 1 50 Table of Contents Chapter I T troduction aca aia dass a adi RN 5 1 1 Supported Operating Systems 6 1 2 Software Prerequisites df EZE o ion dere te th ted oie os in eo ate a een a a edb tes ee Ae ht it RO 7 MD SOT WIT Oy St a iS SAA A ARA Ti Zor Of IR A acanto ni 7 1 3 MFT Access to Hardware Devices 8 1 4 MFT Installation 10 LA TOS MET ONLI OS ar sac ott Settee fhe ha aes E
17. i2c Utility The 12c utility provides low level access to the I2C bus on any Mellanox switch platform enabling the user to read or write data C 4 1 Operation The MST driver must be started prior to running 12c tool To start 12c I Start the MST driver mst start or mst restart 1 This step in not required in Windows Mellanox Technologies 47 J Rev 1 50 spark InfiniScale III Firmware Burning Tool 2 Run i2c with the following command line syntax e NS ian Zio cede ile aa where OPTIONS can be the following h Prints this message a lt addr_width gt Sets address width in bytes to the specified value May be 0 1 2 or 4 Default 1 d lt data width gt Sets data width in bytes to the specified value May be 1 2 or 4 Default is 1 x lt data len gt Presents each byte of data as two hexadecimal digits such as 013C20343B Note that this option is mutually exclusive with the d option The remaining parameters are lt device gt Valid MST device lt emd gt Command May be r ead or w rite lt i2c_addr gt 2C slave address lt addr gt Address of length addr width inside I2C target device to read write operation Note that the lt addr gt value is ignored if lt addr_witdh gt 0 lt data gt Data bytes of length data width to write to target device 7 All parameters are interpreted as hexadecimal values a Examples
18. in the device s Programmer s Reference Manual Setting or clearing bits of the trace mask register enables or disables respectively the generation of specific types of trace messages The TRACE MASK parameter must be a hexadecimal or decimal number and its value will be written into the trace mask register Changing trace mask will not change or remove mes sages previously stored in the trace buffer so disabled types of messages can still be displayed by itrace if they were previously generated Example For Linux device names should be listed with the dev mst prefix For Windows no pre L gt fix is required itrace d dev mst mt25204 pci cr0 nomap m Oxffffffff tpt This generates output regarding the sequence numbers timestamps and records of operations such as the following IRISC Trace Viewer Mellanox InfiniHost V4 4 2 Jul 31 2007 16 56 59 EV Versvomen ies 022 09 07 AAN 00000001 00000003 00000004 00000005 00000006 00000007 00000008 00000009 0000000a 0000000b 0000000c 0000000d 00000029 0000002a 0000002b 0000002c elbs9bdl clb59ede dda895e4 dda89760 dda89868 dda97ccf dda97e47 dda97f4f dda9a8 6 dda9aa6e dda9ab79 ddaaadc1 ddaee521 ddaee60c ddaee8ce ddaee9 2 SCHD SEDE OCRD SCRDE SCHED SCD SCADE OCRD SCRDE SODE SCADE SCR INFO INFO MAD SCRD SOP 0x0004102 exes super schedu
19. is the device the dword is read from addr is the address of the word to read Example flint d dev mst mt23108 pci cr0 rw 0x20 Mellanox Technologies 35 J Rev 1 50 flint Firmware Burning Tools 3 2 3 6 Writing a Dword to Flash To write one dword to Flash memory use the following command line flint d lt device gt ww addr data where device is the device the dword is written to addr is the address of the word to write data is the value of the word Example flint d dev mst mt23108 pci conf01 ww 0x10008 0x5a445a44 3 2 3 Writing a dword to Flash Without Sector Erase To write one dword to Flash memory without sector erase use the following command line flint d lt device gt wwne addr data where device the device the dword 1s written to addr the address of the word to write data the value of the word Example flint d dev mst mt23108 pci cr0 wwne 0x10008 0x5a445a44 Note that the result may be dependent on the Flash type Usually bitwise and between the speci fied word and the previous Flash contents will be written to the specified address 3 2 3 8 Erasing a Sector To erase a sector that contains a specified address use the following command line flint d lt device gt e addr where device is the device the sector is erased from and addr is the address of a word in the sector that you want to erase Example flint d dev mst mtusb 1 e 0x1000 36 Mellanox Technologie
20. may cause the device to malfunction Use only if you know what you are doing skip_1s Allow burning the FW image without updating the invariant sector to ensure failsafe burning even if the invariant sector of the image is differ ent from the one burnt on the Flash Note Some FW releases may include important changes to the invariant sector that must be included in the FW update process In these cases the skip is flag should not be used Please refer to the specific FW release notes for details s ilent Print errors only Affected commands burn y es Non interactive mode Assume the answer yes to all questions Affected commands all no Non interactive mode Assume the answer no to all questions Affected commands all vsd lt vendor specific data gt A VSD string composed of up to 208 characters will be written to the VSD section in the flash If not specified the current VSD will be preserved use image ps Burn vsd as it appears in the given image Default Retain current vsd on Flash Affected commands burn use image guids Burn guids uids macs as appears in the given image Affected commands burn use image rom Do not save the ROM which exists in the device Affected commands burn dual image Make the burn process burn two images on flash previously default algo rithm Current default failsafe burn process burns a single image in alternating locations Affected commands burn
21. text format to the console For more details see the QUERY DEBUG MESSAGE command interface description in the device s Programmer s Reference Manual available via https docs mellanox com requires a cus tomer login account C 1 2 Operation In order to print the firmware traces it is required that e Debug firmware is burnt and loaded to the device e The driver is up Specifically this means that For adapters with on board memory The SYS ENABLE command has been executed For adapters without on board memory MemFree The RUN FW command has been executed e The desired trace mask is set see the m flag below The MST driver must be started prior to running itrace tool To start itrace 1 Start the MST driver mst start or mst restart 2 Enter the following command o Om ll Na where IRISC NAME is the iRISC for which traces are to be printed This can be specified once any where in the command line as a special option without the leading hyphen Run itrace h to get a list of iRISC names for each adapter device options can specify any of the following h help Displays help about itrace usage m mask 7TRACE_MASK Sets the Trace Mask 1 Thisstep in not required in Windows Mellanox Technologies 43 J Rev 1 50 spark InfiniScale III Firmware Burning Tool To enable generating trace messages for an iRISC the trace mask register must be set according to the specifications
22. the system board you wish to control via the I2C interface If the system board uses a 3 pin connector instead of a 9 pin connector connect the appropriate converter cable as an extension to the I2C cable on the 9 pin end then connect its 3 pin end to the system board E 3 Software Installation The MTUSB 1 device requires that the Mellanox Firmware Tools MFT package be installed on the machine to which MTUSB 1 is connected see Section 1 4 MFT Installation on page 10 of this manual for installation instructions For a Windows machine it is also required to install the MTUSB 1 driver visit http www dio lan com to download this driver This driver is required for the first use of the MTUSB 1 device Once you have the requirements installed you may verify that your MTUSB 1 device is detected by MFT software as described below 1 Start the mst driver Enter mst start or mst restart if mst start was run earlier 2 To obtain the list of mst devices enter mst status If MTUSB 1 has been correctly installed mst status should include the following device in the device list it generates On Linux dev mst mtusb 1 On Windows mtusb 1 1 This step in not required in Windows Mellanox Technologies 53 J
23. v where device is the Flash device to verify and image file is the image file to verify Examples flint d dev mst mt25418 pci cr0 v A ge ae So 3 2 2 4 Managing an Expansion ROM Image I To burn an Expansion ROM image use the following command flint d lt mst device gt brom lt image name gt rom The brom command installs the ROM image on the Flash device or replaces an already exist ing one 26 Mellanox Technologies Rev 1 50 Example flint d dev mst mt25418 pci cr0 brom example rom Current ROM info on flash N A New ROM info type GPXE version 2 0 100 devid 25418 proto IB Burning ROM image Ok Restoring signature OK 2 To read an Expansion ROM image to a file use the following command flint d lt mst device gt rrom lt image name gt rom Example flint d dev mst mt25418 pci cr0 rrom example rom flint d dev mst mt25418 pci cr0 q Image type ConnectX FW Version 2 6 1410 Rome inten type GPXE version 2 0 100 devid 25418 proto IB Device ID 25418 Chip Revision A0 Description Node Bert Ret Sys image GUIDE 0002c9000100d050 0002c9000100d051 0002c9000100d052 0002c9000100d050 MACs 0002c9000001 0002c9000002 Board ID ME 04C0T T0002 VSD POTI MT 04C0110002 3 To remove the Expansion ROM use the following command flint d lt mst device gt drom Example flint d dev mst mt25418 pci cr0 drom Removing ROM image OK Restoring signature OK tf
24. yes Affected commands All Version information Burns the binary image to the EEPROM Parameters None Examples spark d dev mst mtusb 1 i imagel img burn spark d dev mst mtusb 1 guid 0x2c9000100d050 i imagel img b Queries miscellaneous EEPROM and firmware characteristics Parameters None Example spark d dev mst mtusb 1 query Verifies the entire EEPROM Parameters None Example spark d dev mst mtusb 1 v Burns the given image as is Burn Block No checks are performed on EEPROM or on the given image Also no fields e g BSN or GUIDs are read from the EEPROM Parameters None Example spark d dev mst mtusb 1 i image1 img bb Reads the firmware image on the EEPROM and writes it to a file Parameters filename to write the image to in img format Example spark d dev mst mtusb 1 ri file img Reads a block of data from a single eeprom to the given file Parameters lt eeprom address gt lt start offset gt lt data size gt lt output file name gt 38 Mellanox Technologies Rev 1 50 Example spark d dev mst mtusb 1 rb 0x56 0x0 0x1000 out img swreset SW resets the target switch device In response to this command the tar get switch device continues to transport packets to their destinations ignores management packets that are destined to the target switch device itself resets itself after about 15 seconds from receiving the command The 15 second delay is intended t
25. 3 2 3 Additional Debug Production Commands 3 2 3 1 Setting GUIDs and MACs To set GUIDs MACs UIDs for the given device use the sg set guids command with the guid s uid s and or mac s flags Mellanox Technologies 21 J Rev 1 50 flint Firmware Burning Tools On pre ConnectX Devices Oxff GUID values and a blank CRC In other words the firmware image was gener 74 On pre ConnectX devices the sg command is applicable only for images with blank A ated using the blank_guids flag The following is an example of a complete flow where a blank GUIDs image is first generated and burnt to the Flash Then the GUIDs are set using the sg command I Generate the image with blank guids gt mlxburn fw fw 25408 rel mlx c MHGH28 XTC Al ini wrimage A tmp fw 25408 rel 2 3 000 MHGH28 XTC Al noguids bin striped image blank guids SIS Generating Image I Image generation completed successfully 2 Query the image to verify that the GUIDs and MACs are blank gt flint i tmp fw 25408 rel 2 3 000 MHGH28 XTC Al noguids bin striped image q Image type ComneetTX FW Version a nN Device ID 25418 Chip Revision AQ Description Node Porti Porr Sys image GUIDs E E E E EE MACs Ce Board ID n a MT 0440110002 VSD n a PESTO MT 0440110002 Warning GUIDs MACs values and their CRC are not set gt 3 Burn the blank GUIDs image This image can be pre burn
26. CA board flint This tool burns a firmware binary image or an expansion ROM image to the Flash device of a Mellanox network adapter bridge switch device It includes query functions to the burnt firmware image and to the binary image file spark This tool burns a firmware binary image to the EEPROM s attached to an InfiniScaleIII switch device It includes query functions to the burnt firmware image and to the binary image file The tool accesses the EEPROM and or switch device via an I2C compatible interface or via vendor specific MADs over the InfiniBand fabric In Band tool Debug utilities A set of debug utilities e g itrace mstdump mlx12c and 12c Mellanox Technologies 5 J Rev 1 50 Introduction Figure 1 Mellanox Firmware Tools A Scheme of Operation Mellanox USB r om am om am am am am am r e am am am am am am am am TO FC Adapter I I I I I I I SE I I I nni i i IS 7 I I f Mellanox SwitchX Based Mellanox ri in l yee ina iv I USB I j ao y Y 2 Mellanox IB Adapter cola Jie LE gt te e e e e l gt b Note In Band capabilities are not supported by Mellanox Ethernet Adapters 1 1 Supported Operating Systems MFT distributions are available for the following operating systems Linux Windows and VMware ESX Server 3 5 Please refer to the release notes of your version
27. Mellanox TECHNOLOGIES Mellanox Firmware Tools MFT User s Manual Rev 1 50 www mellanox com Rev 1 50 NOTE THIS HARDWARE SOFTWARE OR TEST SUITE PRODUCT PRODUCT S AND ITS RELATED DOCUMENTA TION ARE PROVIDED BY MELLANOX TECHNOLOGIES AS IS WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PROD UCTS IN DESIGNATED SOLUTIONS THE CUSTOMER S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO S AND OR THE SYSTEM USING IT THEREFORE MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANT ABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT INDIRECT SPE CIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING BUT NOT LIMITED TO PAY MENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CON TRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY FROM THE USE OF THE PRODUCT S AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBIL ITY OF SUCH DAMAGE Mellanox
28. T device Mellanox Technologies 13 J Rev 1 50 mixburn FW Image Generator Burner wrimage lt fw image file gt Write the generated binary image to the provided file name fw lt mellanox fw file gt Specify the Mellanox firmware file to use file extension is mlx format lt BINARY IMAGE gt Specify which image format to use Can be used only with the wrimage flag Default is BINARY image lt fw image file gt Use the given firmware image to burn file extension is bin or img conf lt parameter set file gt Firmware configuration file ini Needed for image generation not using the dev flag or if auto detection of configuration fails conf dir lt dir gt Instruct the burn operation to look for auto detected configuration files under the specified directory rather than under the firmware file directory fw_dir lt dir gt Instruct the burn operation to look for auto detected firmware files under the specified directory nofs When specified the burn process will not be failsafe A non failsafe burn is required on the rare occasion when a new firmware version has modi fications in the Invariant Sector nofs img When specified the generated image will not be failsafe If burning is also specified it will not be failsafe either exp_rom lt exp rom file gt Integrate the given expansion rom file to the FW image The given file may be in img or bin rom raw binary format If th
29. aa ere eas 10 LA DUnimstaloMETEnmu sra rd si Valdes 10 14 3 distal MET On Windows OS cicle rade gle Sings et 10 1 4 4 Uninstall MFT Windows ce or 11 145 install MPT On VMware ESX Server 35 05 ella A eRe eee ee 11 1 4 6 Uninstall MFT VMware ESX Server 3 5 rcar re cincta nics iaaias i true u ceerde 11 1 5 Reference Documents and Downloads 11 Chapter 2 mlxburn FW Image Generator amp Burner oooooooooooooooo 12 2 1 Overview 2 2 2 Firmware Generation and Burning with mlxburn 12 222 FitrmmwareCustonmizalioni si sisi rotori nali She alesh 13 2 3 mlxburn Synopsis 13 2 5 Additional UDI OPUS ri A AA AA 16 2 4 Examples of mlxburn Usage 16 24 1 Host Channel Adapter Examples 0 000 dd re dd a a 16 2 42 cx Switch Examples fect alot a ds ed o ada 16 2 4 3 Intimscale TV Switch Examples nta ds ic ds e A eee eek 17 2AA Badee Xx Gateway Example edi 18 2 4 5 InfimScale III Switch Examples coil rss ta 18 2 5 Exit Return Values 19 Chapter 3 flint Firmware Burning Tools ccc cece cw wee creer cece eee eeees 20 3 1 Overview
30. after device power up Then wait for at least half a second before running mget temp for reading the temperature Examples The following steps show how to initialize and then read temperature sensors 1 Initiate thermal sensors mget temp d dev mst SW MT48438 lid 0x000F i 2 Wait half a second and then read the temperature by running mget temp d dev mst SW MT48438 lid 0x000F 1 This step in not required in Windows Mellanox Technologies 49 J Rev 1 50 spark InfiniScale III Firmware Burning Tool Appendix D In Band Access to Multiple IB Subnets In most cases an adapter is connected to a single InfiniBand subnet The LIDs Infiniband Local IDs on this subnet are unique In this state the device access MADs are sent to the target LID from the first active port on the first adapter on the machine In case that the different IB ports are connected to different IB subnets source IB port on the local host should be specified explicitly The device name would be in the format lt any string gt lid lt lid number gt source adapter name source IB port number For example e On Linux lid 3 mlx4 0 1 e On Windows lid 3 0 1 Say we have the following setup Host H1 HCA 0 HCA 1 InfiniScale IV o gt 31 32 33 34 35 15 16 17 18 19 20 21 22 23 24 25 26 27 28 E AAA AO EEEE A SI N mM a InfiniS
31. age 10 e mlxburn tool added Expansion ROM auto detection description e flint tool added the blank guids flag and the sg command e Added Section 3 2 3 1 describing how to set GUIDs MACs on a Flash device with blank GUIDs MACs August 2007 0 60 e Updated tool usage examples to use ConnectX devices e Added Appendix C Debug Utilities June 2007 0 50 e Added the mac flag to the flint and m xburn tools to support the ConnectX EN 10GigE adapter e Added Section 4 3 ibspark on page 29 that describes ibspark the In Band firm ware burning tool for InfiniScale HI switches e Modified Chapter 2 mlxburn FW Image Generator amp Burner on page 18 to describe m xburn support for burning switch systems with multiple InfiniScale InfiniScale III switch devices e Added Appendix B Flow Examples mlxburn to describe burning switches In Band and via a direct I2C connection January 2007 0 40 e MFT for Windows is now part of the WinIB software package therefore to install MFT on a Windows machine you need to install WinIB and enable MFT See Section 1 4 3 Install MFT On Windows OS on page 10 e Added flint flag use image ps e Removed flint flags crc bsn January 2006 0 30 MFT version 1 0 1 e Added querying options for VPD for mlxburn e Added examples to demonstrate support of MT43132 InfiniScale device by mlxburn and spark e Reorganized the flint Firmware Burner on p
32. age 26 chapter e Added the Appendix PSID Assignment October 2005 0 20 Added Windows distribution to MFT MFT version 0 5 1 Added the following sections e Section 1 1 Supported Operating Systems on page 6 e Section 1 3 MFT Access to Hardware Devices on page 8 e Section 1 2 Software Prerequisites on page 7 e Section 1 4 MFT Installation on page 10 August 2005 0 10 First release Linux distribution only MFT version 0 5 0 4 Mellanox Technologies J Rev 1 50 1 Introduction The Mellanox Firmware Tools MFT package is a set of firmware management tools for a single InfiniBand node MFT can be used for e Generating a standard or customized Mellanox firmware image e Querying for firmware information e Burning a firmware image to a single Mellanox device The following is a list of the available tools in the package together with a brief description of what each tool performs The tools apply to single Switch Systems or adapter cards but not to clusters Table 1 Mellanox Firmware Tools MFT Available Tools mlxburn This tool provides the following functions e Generation of a standard or customized Mellanox firmware image for burning in bin binary or img format e Burning an image to the Flash EEPROM attached to a Mellanox HCA or switch device e Querying the firmware version loaded on an HCA board e Displaying the VPD Vital Product Data of an H
33. banks lt banks gt Set the number of attached Flash devices banks log lt log_file gt Print the burning status to the specified log file flash params lt type log2size num of flashes gt Use the given parameters to access the flash instead of reading them from the flash Supported parameters Type The flash s type M25PXxx M25Pxx SST25VFxx W25QxxBV log2size The log2 of the flash size 22 Mellanox Technologies Rev 1 50 num of flashes The number of the flashes connected to the device V Print version information 3 2 2 Command Descriptions The flint utility commands are Common FW Update and Query b urn Burn flash qluery full Query misc flash firmware characteristics use full to get more informa tion v erify Verify entire flash swreset SW reset the target un managed switch device This command is sup ported only in the In Band access method Expansion ROM Update brom lt ROM file gt Burn the specified ROM file on the flash drom Remove the ROM section from the flash rom lt out file gt Read the ROM section from the flash Initial Burn Production bb Burn Block Burns the given image as 1s No checks are done sg nocrc Set GUIDs SV Set the VSD Misc FW Image operations ri lt out file gt Read the fw image on the flash dc out file Dump Configuration print fw configuration file for the given image dh out file Dump Hash print hash f
34. c9030abcdef3 MACS 0002c9bcdefl 0002c9bcdef2 Board ID n a MT 0D80110009 SIDE n a BON MT 0D80110009 Method 2 Pre burn an Image with Specific GUIDs MACs for Each Device In this method a base image is generated with arbitrary default GUIDs and then updated with the correct guids for each device Example Flow I Generate the base image with arbitrary default GUIDs Aa Une CON DO Se MO IRA rage COMES E SIDA striped image 2 Per device set the device specific GUIDs in the image gt flint i fw ConnectX2 rel bin guid 0x0002c9030abcdef0 mac 0x0002c9bcdefl striped image sg Mellanox Technologies 33 J Rev 1 50 flint Firmware Burning Tools 3 Optional Query the image to verify the GUIDs are set The striped image flag must be specified when querying a striped image Dantes AE E Image type FW Version Device ID Chip Revision Description GUIDs MACs Board ID MSD BSD ConnectX ZONA 26428 BO Node Port Poste Sys image 0002c9030abcdef0 0002c9030abcdefl 0002c9030abcdef2 0002c9030abcdef3 0002c9bcdef1 0002c9bcdef2 n a MT 0D80110009 n a MT 0D80110009 Now the fw ConnectX2 rel bin image can be pre burned to the flash After the assembly the device would be fully functional 3 2 3 3 Setting the VSD To set the vsd for the given image device 4th generation use the sv command with vsd flag Example Dain tracey Cov Mot MEAS S Setting the VSD
35. cale III 2 3 4 6 6 wv E me ee go Host H2 Host H3 n a m ne H1 host has 2 adapters Port 1 of the first adapter is conected to the InfiniScale III switch and port 2 of the second adapter is connected to the InfiniScale IV switch Since the 2 adapters on the H1 are not connected to the each other there are 2 seperate IB subnets in this setup Subnetl nodes H1 IS3 switch and H2 Subnet2 nodes H1 IS4 switch and H3 50 Mellanox Technologies Rev 1 50 Running ibv_devinfo command on H1 would list the 2 adapter names For ConnectX adapters the names would be mlx4 0 and mlx4 1 Running mst ib add would add ib devices from the default port first active port on the first adapter only Subnet nodes would be listed To add the nodes of the second subnet the source adapter and port should be specified to the mst ib add command in the following format mst ib add lt hca name gt lt hca port gt Example 1 Add nodes of both subnets Run gt mst ib add mlx4 0 1 gt mst Lo add mlx4 1 2 2 List the devices gt mst status dev mst CA MT25418 H1 HCA 1 lid 0x0001 mlx4 0 1 dev mst CA MT25418 H2 HCA 1 lid 0x0005 mlx4 0 1 dev mst SW MT47396 lid 0x0003 mlx4 0 1 dev mst CA MT25418 H1 HCA 1 lid 0x0010 mlx4 1 2 dev mst CA_MT25418 H3 HCA 1 lid 0x0012 mlx4 1 2
36. e full flag may have undesired side effects and require resetting the device ha Example root mymach mstdump dev mst mt25408 pci cr0 gt mt25408 dmp This dumps the internal configuration data of the device into the file mt25408 dmp C 3 mlxi2c Utility The mlxi2c utility provides access via the I2C MST device to Mellanox 4th generation switch and bridge BridgeX devices C 3 1 Operation The MST driver must be started prior to running mlx12c To start mlxi2c I Start the MST driver mst start or mst restart 2 Run mlxi2c with the following command line syntax mixi2e switches lt command gt parameters switches summary d lt device gt MST 12c device name default dev mst mtusb 1 Affected commands all S lt system gt System type default Auto Detection Supported systems MTS3600 FJ SWITCH BX4020 BRIDGEX EVB BX4010 MTS3610 MTPDK24 IS5025 IS5030 IS5035 Affected commands all m Subsystem module name Affected commands show h Print this help information V Print version and exit lt command gt summary q lt i2c component gt Query an i2c component Supported components Adm1024 LM075 PCA9555 PCA9505 ISMIC PCF8591 p lt i2c_component gt Route the 12c path to the indicated 12c component init gpio lt gpio name gt Configure the GPIO pins 46 Mellanox Technologies Rev 1 50 set gpio lt gpio name gt lt pin name gt lt value gt
37. e Added the striped image flag in sections mlxburn Synopsis on page 13 and Switch Descriptions on page 20 October 2009 1 20 e Added support for Mellanox MT25408 ConnectX 2 MT25408 ConnectX 2 EN MT25458 ConnectX 2 ENf MT64102 BridgeX and MT1016 PhyX devices e Removed ibspark text no longer supported e Added the option fw_ dir to mlxburn e Added Section 2 4 4 BridgeX Gateway Examples e Added support for Expansion ROM images see Section 3 2 2 4 Managing an Expansion ROM Image e Added Section C 3 mlx12c Utility e Added Section C 5 mget temp Utility December 2008 1 10 e Added support for In Band device access for the Windows operating system See Section 1 2 and Section 1 3 e Added Appendix E MTUSB 1 USB to IC Adapter November 4 2008 1 01 e Added VMware ESX Server 3 5 support See Section 1 2 3 Section 1 3 Section 1 4 5 Section 1 4 6 and Section 2 1 e Added the ul flag to m xburn see Section 2 3 Mellanox Technologies 3 J Rev 1 50 Table 1 Revision History Table Date Revision Description August 2008 1 0 e Added support for Mellanox InfiniScale IV switch device e Expanded In Band support with the command mst ib add e Modified the Windows MFT installation now it is a standalone installation e Added the qq flag to flint April 2008 0 65 e Added MFT installation instruction in Section 1 4 MFT Installation on p
38. e exp rom file is set to AUTO expansion rom file is auto detected from the files rom in the exp rom dir see below Note Exp rom auto detection is done for devices that are already burned with an exp rom image If exp rom AUTO is specified for a device with no exp rom it would be burnt with no exp rom To add exp rom to a device manually supply the exp rom file to use exp rom dir lt exp rom dir gt The directory in which to look for expansion rom file when exp rom AUTO is specified By default exp rom files are searched in lt fw file directory gt exp_rom fwver When a device is given Display current loaded firmware version When a FW file is given fw flag Display the file FW version force Run mlxburn in non interactive mode vpd on Linux only Display the Read Only section of the PCI VPD Vital Product Data of the given device l vpd rw on Linux only Display the Read Only and Read Write sections of the PCI VPD of the given device vpd prog rw I lt rw fields file gt on Linux only Program the VPD W tag the writable section of the VPD with the data given in the rw keywords file File lines format KEYWORD VALUE In order to set binary data to a keyword add BIN to the keyword name in this case the data is a hexadecimal string of even length Example file V1 MY ASCII KEYWORD 1 The VPD query may not be enabled on certain board types Also VPD operations are available
39. enter mlxburn image fw BridgeX bin dev dev mst mt64102 pci crl 2 4 5 InfiniScale Ill Switch Examples e To update firmware on an MT47396 InfiniScale III device enter mlxburn fw IS3FW BIN dev dev mst mtusb 1 7 This firmware update cannot be performed before initializing the MST device mtusb 7 1 to connect to the I2C compatible bus of the InfiniScale III and its EEPROM e To generate an image for the InfiniScale HI switch device enter mlxburn fw IS3FW BIN conf MTS2400 A00 INI wrimage IS3FW img gt The generated firmware image to be burnt to a switch device must have a 1mg file name extension da 18 Mellanox Technologies Rev 1 50 e To update firmware on an MT43132 InfiniScale device in a switch system such as Flextronics F X430066 Stallion 8 4X IB port switch enter mlxburn image Stallion 5 5 0 eeprom dev dev mst mtusb 1 dev type 43132 A This firmware update cannot be performed before initializing the MST device mtusb 1 to connect to the I2C compatible bus of the InfiniScale and its EEPROM hai e To generate an MT47396 image and perform an In Band update of the device with LID 0x11 enter mlxburn dev lid 0x11 fw IS3FW BIN 2 5 Exit Return Values The following exit values are returned e 0 successful completion e gt 0 an error occurred Mellanox Technologies 19 J Rev 1 50 flint Firmware Burning Tools 3 flint Firmware Burning Tools 3
40. for supported platforms and kernels gt 4 Unless explicitly specified the usage of the tools is identical for all operating systems gt 6 Mellanox Technologies J Rev 1 50 1 2 Software Prerequisites 1 2 1 On Linux Table 2 MFT Software Dependencies on Linux Software Package Required Version 1 OFED can be downloaded from http www openfabrics org Note that installing OFED is not required if you wish to install MFT without In Band capabilities 2 For the mst ib add command to run one of the OFED packages ibutils or ibutils2 or infiniband diags should be installed and available in the PATH For details on OFED installation see the link in Section 1 5 Reference Documents and Downloads on page 11 1 2 2 On Windows Table 3 MFT Software Dependencies on Windows Software Package Required Version I2CBridge 0 1 4 or later Dimax s Driver for USB to I2C Adapter WinOF 2 0 0 or later optional NOTE The tools package must also be installed as part of the WinOF installation 1 Visit http www diolan com to download this driver This driver is required for the first use of the MTUSB 1 device It is not required for MFT software installation 2 WinOF is required only for In Band access The package can be downloaded from www mellanox com gt Products gt InfiniBand SW Drivers 1 2 3 On VMware ESX Server 3 5 Table 4 MFT Software Dependencies on VMware ESX Se
41. ile for the given image HW Access Key set key key Set Update the HW access key which is used to enable disable access to HW The key can be provided in the command line or interactively typed after the command is given NOTE The new key is activated only after the device is reset hw access lt enable disable gt key Enable disable the access to the HW The key can be provided in the com mand line or interactively typed after the command is given Low Level Flash Operations cfi Query flash device parameters e rase lt addr gt Erase sector rw lt addr gt Read one dword from flash ww lt addr gt lt data gt Write one dword to flash wwne lt addr gt Write one dword to flash without sector erase wbne lt addr gt lt size gt lt data gt Write a data block to flash without sector erase rb lt addr gt lt size gt out file Read a data block from flash The following sections provide the command line syntax for the following flint utility commands together with examples of usage Mellanox Technologies 23 J Rev 1 50 flint Firmware Burning Tools e Section 3 2 2 1 Burning a FW Image on page 24 e Section 3 2 2 2 Querying the FW Image on page 26 e Section 3 2 2 3 Verifying the FW Image on page 26 e Section 3 2 2 4 Managing an Expansion ROM Image on page 26 3 2 2 1 Burning a FW Image The FLINT utility enables you to burn the Flash from a binary image T
42. ler pusy done exeqpc valid2freed 0x0 vec busy valid 0x00000010 SOP 0 x0007T00 exes super scheduler busy done acaso Opotate OO ROAT GOOD ID exeqpc valid2freed 0x0 vec busy valid 0x00000010 SOP 0x000400 exes super scheduler busy_ Writing Opstate SOPSTATE GOOD TOEN HNI exeqpc valid2freed 0x0 vec busy valid 0x00000010 SOP Ux 000000 exes super scheduler busy writing QpState SOPSTATE GOOD IDLE exeqpc valid2freed 0x0 vec busy valid 0x00000010 SOP 0x000400 exes super scheduler busy_ IPCdata 00 0x0labcd0a IPCdata 01 0x00000014 exes mad QPN 0x000000 nda nds 0x7c58d014 SQP 0x000000 sqpc_ access db algorithm INC 44 Mellanox Technologies Rev 1 50 0000002d ddaef0d5 SCHD exes is cuele try fo insert UU dae SCHD SOP 0 x000000 exes scheduler chosen 0000002f ddaefoaa SCHD EXES GO 0x0 W wait Runs itrace in wait mode itrace will exit only if you press lt Ctrl C gt This is not the default behavior of itrace Without the w option itrace will exit if there have been no new traces in the last 0 5 seconds d d DEVICE Specifies the name of the MST device driver for accessing the cr space The default value 1s dev mst mt23108 pci cr0 To run itrace via the I2C interface use this option to specify the following d device where the device is an I2C device such as mtusb 1 nomap Sets itrace not to directly access memory via memory mapping for read ing the trace buffer but t
43. nt will re burn the current image using the given GUIDs MACs UIDs 1 Change the GUIDs MACs on a device A tad Com a cua W Running quick query Skipping full image integrity checks Image type ConnectX FW Version AI Rom Info type PXE version 3 0 0 devid 25418 proto VPI Mellanox Technologies 29 J Rev 1 50 flint Firmware Burning Tools 2 Change the GUIDs MACs on an image file 30 Mellanox Technologies Rev 1 50 Mellanox Technologies 31 J Rev 1 50 flint Firmware Burning Tools PSID MT 04C0110002 3 2 3 2 Preparing a Binary Firmware Image for Pre assembly Burning In some cases OEMs may prefer to pre burn the flash before it is assembled on board To generate an image for pre burning for 4th generation devices ConnectX and newer use the mlxburn striped image flag The striped image file layout is identical to the image layout on the flash hence making it suitable for burning verbatim When pre burning the GUIDs MACs inside the image should be unique per device The following are two methods to pre burn an image You can choose the best method suitable for your needs Method 1 Pre burn an Image with Blank GUIDs MACs In this method the image is generated with blank GUIDs and CRCs The GUIDs are set after the device is assembled using the flint sg command To set GUIDs take less than 1 second when run ning on an image with blank GUIDs through a PCI device
44. o allow for spark to reset other switches in the fabric Example spark d 0x13 swreset this command SW resets the switch device with LID 0x13 Mellanox Technologies 39 J Rev 1 50 spark InfiniScale III Firmware Burning Tool Appendix A PSID Assignment In some cases OEMs or board manufacturers may wish to use a specific FW configuration not supplied by Mellanox After setting the new FW parameters in an INI file the user should assign a unique PSID Parameter Set ID to this new configuration The PSID is kept as part of the FW image on the device NVMEM The firmware burning tools use this field to retain FW settings while updating FW versions This appendix explains how to assign a new PSID for a user customized FW and how to indicate to the burning tools that a new PSID exists A Please change FW parameters with caution A faulty setting of FW parameters may result in undefined behavior of the burnt device ha A 1 PSID Field Structure The PSID field is a 16 ascii byte character string If the assigned PSID length is less then 16 characters the remaining characters are filled with binary 0s by the burning tool Table 6 provides the format of a PSID Table 6 PSID format Board Version Parameter Set 3 characters 3 characters gt characters as 3 ed ileg with 0 Example A PSID for Mellanox s MHXL CF128 T HCA board is MT_ 0030000001 where MT_ Mellanox vendor symbol 003 MHXL CF128
45. o burn the entire Flash from a raw binary image use the following command line flint d devie 1 gt oud GUID gourds lt 4 GUIDS gt mae MAC macs lt 2 MACs burn where device Device on which the flash is burned fw file Binary firmware file GUID s optional for InfiniBand adapters and 4th generation switches One or four GUIDs If 4 GUIDS are provided guids flag they will be assigned as node Port 1 Port 2 and sys tem image GUIDs respectively If only one GUID is provided guid flag it will be assigned as node GUID Its values 1 2 and 3 will be assigned as Port 1 Port 2 and system image GUID respectively If no guid guids flag is provided the current GUIDs will be preserved on the device gt For 4th generation four GUIDs must be specified but Ports 1 and 2 GUIDs are ignored and should be set to 0 7 A GUID is a 16 digit hexadecimal number If less than 16 digits are provided leading zeros will be inserted MAC s optional for Ethernet and VPI adapters and switches If 2 MACs are provided macs flag they will be assigned to Port 1 and Port 2 respectively If only one MAC is provided mac flag it will be assigned to Port 1 MAC 1 will be assigned to Port 2 If no mac macs flag is provided the current LIDs will be preserved on the device gt A MAC isa 12 digit hexadecimal number If less than 12 digits are provided leading zeros will be inserted ha 24 Mellanox Technol
46. o use the adapter memory access Gateway instead By default itrace accesses the memory directly If the cr space device specified by the d parameter is one of the I2C devices nomap is switched on no propel Sets itrace not to animate the propeller in wait mode w option By default animation is enabled V version Prints the MFT version and exits c color Enables color in trace output D dump Dumps the trace buffer and exits This option is useful for debugging itrace 1t dumps the contents of the trace buffer in row format gt Typing help at the command line displays manual pages describing the syntax of the itrace utility ha C 2 mstdump Utility The mstdump utility dumps device internal configuration data The data can be used by for hard ware troubleshooting It can be applied to all Mellanox adapter devices BridgeX device InfiniS cale III switch devices and 4th generation switch devices C 2 1 Operation The MST driver must be started prior to running mstdump tool To start mstdump I Start the MST driver mst start or mst restart 1 This step in not required in Windows Mellanox Technologies 45 J Rev 1 50 spark InfiniScale III Firmware Burning Tool 2 Enter an mstdump command that complies with the following command syntax mstdump fulli lt mst device gt gt lt dump file gt where the u11 flag dumps all internal registers A On BridgeX devices using th
47. ogies Rev 1 50 Examples I Update the FW on the device keeping the current GUIDs and VSD Note This is the com mon way to use flint gt flint d dev mst mt25418 pci cr0 i fw 25408 2 1 000 MHGH28 XSC Al bin burn 2 Update the FW on the device specifying the GUIDs to burn gt flint d dev mst mt25418 pci cr0 i 25408 2 1 000 MHGH28 XSC Al bin guid 12345678deadbeef burn 3 Update the FW on the device specifying the MACs to burn gt flint d dev mst mt25448 pci cr0 i fw 25448 6 0 111 MNEH28 XTC Al bin mac 12345678beef burn 4 Burn the image on a blank Flash device This means that no GUIDs are currently burnt on the device therefore they must be supplied with guid guids by the burning command Moreover the burn process cannot be failsafe when burning a blank Flash therefore the nofs flag must be specified gt flint d dev mst mt25418 pci cr0 i 25408 2 1 000 MHGH28 XSC Al bin nofs guid 1234567812345678 burn 5 Read FW from the device and save it as an image file gt flint d dev mst mt25418 pci cr0 ri Flash Image Copy bin 6 MT48436 InfiniScale IV switch Burn the image on a blank Flash device This means that no GUIDs are currently burnt on the device therefore they must be supplied with guid guids by the burning command Moreover the burn process cannot be failsafe when burning a blank Flash therefore the nofs flag must be specified gt flint d dev mst mtusb 1 i tmp fw is4 bin
48. ommands burn sg guids lt GUIDs gt 4 GUIDs must be specified here These GUIDs will be assigned to node portl port2 and system image GUID respectively Affected commands burn sg 20 Mellanox Technologies Rev 1 50 mac lt MAC gt MAC base address value Each of the two ConnectX EN ports is assigned a MAC address as follows MAC is assigned to Port I MAC 1 is assigned to Port 2 Affected commands burn sg l macs lt MACs gt 2 MAC addresses must be specified here one for each ConnectX EN port The first MAC address is assigned to Port 1 and the second MAC address to Port 2 Affected commands burn sg uid lt UID gt BridgeX only Derive and set the device UIDs GUIDs MACs WWNs UIDs are derived from the given base UID as per Mellanox s methodol ogy Affected commands burn sg uids lt UIDs gt BridgeX only 29 space separated UIDs must be specified here in the fol lowing order GO MAC PIO GO0 MAC PIl G0 MAC PI2 G0 MAC PEO G0 MAC PEl G0 MAC PE2 G0 MAC PE3 G0 FC WWPN P0 G0 FC WWPN P1 G0 FC WWPN P2 G0 FC WWPN P3 G0 IB NODE GUID G0 IB PORT GUID G0 FC WWNN Gl MAC PIO GI MAC PII GI MAC PI GI MAC PEO Gl MAC PEl Gl MAC PE2 GI MAC PE3 G1 FC WWPN PO Gl FC WWPN P1 GI FC WWPN P2 Gl FC WWPN P3 G1 IB NODE GUID G1 IB PORT GUID G1 FC WWNN IB SYSTEM GUID Affected commands burn sg blank_guids Burn the image with blank GUIDs and MACs where applicable These values can be se
49. only for devices with a PCI interface 14 Mellanox Technologies Rev 1 50 V2 BIN 1234abcd White spaces before and after VALUE are trimmed vpd set keyword i lt keyword assignment gt on Linux only Add or change a keyword value in the VPD W tag the writable section of the VPD with the data given in the keyword assignment string The string format is identical to a line in the rw key words file described above Other keywords in the VPD W tag are not affected by this operation query Query adapter or switch devices for firmware information on Linux only Use this flag to access hardware using the PCI user level method When using this flag the argument of the dev flag should be the PCI number of the target device in the format lt bus dev fn gt I I striped image For image generation only The striped image is used as its file layout is similar to the image layout on the flash The striped image can be used for pre burning using an external burner or flint bb command dev type lt Mellanox Device ID gt mlxburn must know the Mellanox device ID in order to work properly This option should be used if auto detection of the device type taken from the firmware file fails The following 1s the list of supported device IDs 23108 For MT23108 InfiniHost based HCA cards Cougar family 25208 For MT25208 InfiniHost III Ex in InfiniHost mode with local attached memory HCA cards Lion Cub family
50. or PCI and I2C access In Band devices can be assigned by running the mst ib add com mand 8 Mellanox Technologies J Rev 1 50 To list the available mst device names on the local machine run mst status on Linux and Win dows only Notes for Windows e The mst service which provides PCI access to the target adapter is run automatically upon boot e To access an adapter or switch device via the USB bus A USB to I2C Adapter should be used to connect the host USB port and the I2C port of the target device Upon the first usage of this interface you will be requested to install the USB to I2C Adapter driver I2CBridge Note for VMware ESX Server 3 5 e Only PCI user level access to Mellanox devices is supported on VMware ESX Server 3 5 machines See below The format of an mst device name is as follows e Via PCI mt lt dev id gt pci lt crX confX gt where X 1s the index of the adapter on the machine _crX devices access the adapter directly recommended if possible confX devices use configuration cycles to access the adapter For example mt25418 pci crd e Via USB to I2C adapter For example mtusb 1 e Via In Band lt string gt lid lt lid number gt For example AM OS o o o eZ The mst ib add command adds devices in the format for adapters and bridges Coen ee e ono dd cionci for switches SW lt device id gt lid lt lid number gt See Step 3 in Appendix B Fl
51. ow Examples mlxburn on page 38 for instructions on how to obtain the device LID 1 Visit http www xdimax com to download this driver Mellanox Technologies 9 J Rev 1 50 Introduction See Appendix D In Band Access to Multiple IB Subnets on page 52 for details on how to access devices in multiple IB subnets e Via PCI user level lt bus dev fn gt gt The mst device name obtained in this method can only be used with the mlxburn tool with the ul flag be For example if you run spci d 1563 Mellanox devices and PCI Device IDs will be displayed gt sony Lon acl Islas 02 00 0 Ethernet controller Mellanox Technologies Unknown device 6368 rev al 1 4 MFT Installation 1 4 1 Install MFT On Linux OS From MFT version 2 6 2 MFT installation method on Linux OS is RPM based MFT applications are installed using a pre compiled binary RPM and Kernel modules are distributed as a source RPM and compiled by the installation script To install MFT perform the following 1 Download the Linux MFT package from the Mellanox Management Tools webpage http www mellanox com products management_tools php 2 Untar the downloaded package 3 Run install sh 4 Start the mst driver by running mst start A It is possible to customize some installation parameters such as the target installation path Run install sh help for details 1 4 2 Uninstall MFT Linux To uninstall MFT Linux run
52. responding parame ter set file is found the user should explicitly specify which parameter set file to use To produce an image file the user needs to provide the option wrimage lt target file gt To actually burn the image to the Flash EEPROM attached to a Mellanox adapter or switch device the user needs to specify the option dev lt mst device gt see the synopsis section below If run in burning mode mlxburn auto detects the firmware parameter set with which the device was previously burnt It locates and uses this parameter set file to generate the appropriate image for the device by merging the FW release with the specific parameter set required To inhibit image generation the image lt pre generated image file gt should be used It instructs mlxburn to use the given file for burning the device 2 3 mlxburn Synopsis mlxburn h v lt dev mst device wrimage fw image gt lt iw mellanox fw file image fw image img dir img direcory fw dir fw dir gt conf fw conf file nofs nofs_ img format BINARY IMAGE dee peace pe Mero ae e one eo ro een lt conf dir gt fwver vpd vpd_ rw vpd prog rw lt rw keywords file gt vpd set keyword lt keyword assunto pers enel die Peer where h Display a short help text V Print version info and exit V lt INFORM WARNING DEBUG gt Set the verbosity level Default is WARNING dev lt mst dev gt Burn the image using the given MS
53. rver 3 5 Software Package Required Version OFED s mstflint RPM OFED 1 1 or later 1 OFED s mstflint RPM can be downloaded from http www mellanox com products management tools php Mellanox Technologies T J Rev 1 50 Introduction 1 3 MFT Access to Hardware Devices Table 5 lists the Mellanox devices supported by MFT the supporting tools and the access methods to these devices Table 5 Supported Mellanox Devices HW Access Method HCA InfiniBand MT23108 MT23108 InfiniHost MT23108 InfiniHost mixbum flint MT25208 InfiniHost III MT25204 InfiniHost III VPI Network Adapter MT25408 ConnectX mlxburn flint MT25408 ConnectX 2 MT25408 ConnectX 3 Ethernet Adapter NIC MT25408 ConnectX EN mlxburn flint MT25408 ConnectX 2 EN Switch MT58100A0 Switchx mlxburn flint MT48436 InfiniScale IV MT47396 InfiniScale III MT43132 MT43132 InfiniScale 1 For managed switch products only MFT tools access Mellanox devices via the PCI X PCI Express interface via a USB to I2C adapter Mellanox P N MTUSB 1 or via vendor specific MADs over the InfiniBand fabric In Band gt In Band device access requires the local IB port to be in the ACTIVE state and con nected to an IB fabric All MFT tools address the target hardware device using an mst device name This name is assigned by running the command mst start In Windows it is not required to run the mst start com mand f
54. s Rev 1 50 4 spark InfiniScale III Firmware Burning Tool 4 1 Overview The spark tool enables burning a binary firmware image to the EEPROM device attached to an InfiniScale MT43132 or InfiniScale III MT47396 switch device via a direct I2C connection or via vendor specific MADs over the InfiniBand fabric This tool is described in Section 4 2 4 2 spark 4 2 1 spark Synopsis spark switches lt command gt parameters where switches are d evice lt device gt defines the Mellanox device to which the EEPROM is connected Affected commands All see the commands below 1 mage lt image gt Image file is in 1mg format Affected commands burn verify query guid lt GUID gt Uses the given guid as the node guid of the burnt image By default the guid is taken from the image on the EEPROM Affected commands burn sysguid lt GUID gt Use the given guid as the system image guid of the burnt image By default this value is taken from the current image on the EEPROM Affected commands burn bsn lt BSN gt Mellanox Board Serial Number BSN The vallid BSN format is MTxxxxx R xx ddmmyy nnn cc By default this value is taken from the current image on the EEPROM Affected commands burn ndesc lt Descr gt Use the given string max 64 characters as the node description By default this value is taken from the current image on the EEPROM Affected commands burn isl
55. t InfiniBand SW Drivers e ibdiag tools run man ibdiagnet for details on a machine with OFED installed Mellanox Technologies 11 J Rev 1 50 mixburn FW Image Generator Burner 2 mixburn FW Image Generator amp Burner 2 1 Overview mlxburn is a tool for firmware FW image generation and or for burning a firmware image to the Flash EEPROM attached to a Mellanox device Both functions or a single function of mlxburn can be activated by means of command line options see Section 2 3 mlxburn Synopsis It can also query for firmware attributes e g firmware version GUIDs etc and VPD info of adapter cards and switch systems mlxburn allows for cusomization of standard Mellanox firmware for OEM specific needs e g a specific adapter board type See Section 2 2 1 Firmware Customization on page 13 gt On VMware ESX Server 3 5 you must use mlxburn with the ul flag Aa 2 2 Firmware Generation and Burning with mlxburn The mlxburn firmware update flow is composed of two separate stages image generation and image burning In the image generation stage a given Mellanox firmware release in mlx format for adapters bridges and 4th generation switches and in BIN file format for InfiniScale II switches is processed together with a board specific configuration in1 file to generate a burn able firmware image This image is burnt to the Flash EERPROM attached to a Mellanox device
56. t later using the sg command see details below NOTE An image that is burnt with blank GUIDs MACs will fail to boot the machine as long as the GUIDs MACs are not set Affected commands burn clear semaphore Force the clearing of the Flash semaphore on the device This flag should come BEFORE the d evice flag in the command line No command is allowed when this flag is used NOTE Using this flag may result in an unstable behavior and flash image corruption if the device or another flash application is currently using the flash Handle with care byte_ mode Shift the address when accessing Flash internal registers May be required for burn write commands when accessing certain Flash types on Infini Host IIEx HCAs no flash verify Do not verify each write on the Flash device 1 The mac and macs options are applicable only to Mellanox Technologies Ethenet adapter and switch devices Mellanox Technologies 21 J Rev 1 50 flint Firmware Burning Tools striped_image Use this flag to indicate that the given image file is in a striped image format See mlxburn Synopsis striped image flag for details Affected commands query verify h elp Print this message and exit hh Print extended command help nofs Do not burn image in failsafe mode allow psid change Allow burning a FW image with a different PSID Parameter Set ID than the one currently on flash Note that changing a PSID
57. t mymach gt mst ib add I Discovering the fabric Running opt bin ibdiagnet skip all I Added 3 in band devices To list the discovered mst inband devices run mst status root mymach gt mst status MST modules MST PCI module loaded MST PCI configuration module loaded Inband devices dev mst CA MT25418 sw005 HCA 1 lid 0x0001 dev mst SW MT47396 lid 0x0011 Mellanox Technologies 41 J Rev 1 50 spark InfiniScale IIl Firmware Burning Tool b Using the ibnetdiscover tool run 1 Run m xburn with the LID retrieved in step 3 above to perform the In Band burning opera tion Burn the InfiniScale III switch Burn the InfiniScale IV switch 42 Mellanox Technologies Rev 1 50 Appendix C Debug Utilities C 1 itrace Utility C 1 1 Overview The itrace utility extracts and prints trace messages generated by the embedded RISC processors of Mellanox Technologies InfiniBand or Ethernet adapter devices These trace messages inform developers of software drivers about internal status events critical errors etc for each iRISC Trace messages generated by iRISCs are stored in the trace buffer The trace buffer is located in host memory for MemFree adapter cards 1 e without on board memory and in adapter memory for adapter cards with on board memory The utility is a command line application controlled by command line parameters It prints trace messages in
58. t on the flash in an early produc tion phase In this example the flint bb command is used in order to burn the image as is gt flint d dev mst mt25418 pci cr0 i tmp fw 25408 rel 2 3 000 MHGH28 XTC Al noguids bin bb Block burn The given image will be burnt as is No fields such 28 Mellanox Technologies Rev 1 50 as GUIDS VSD are taken from current image on flash Burn process will not be failsafe No checks will be performed ALL flash including the Invariant Sector will be overwritten If this process fails computer may remain in an inoperable state Do you want to continue y n n y 100 4 Set the GUIDs and MACs using the flint sg command gt flint d dev mst mt25418 pci cr0 guid 0x0002c90001777050 mac 0x0002c9777051 sg 5 Query the image on the Flash to verify that the GUIDs and MACs were set correctly gt flint d dev mst mt25418 pci cr0 q Image type ConnectX FW Version DOSE Device ID 25418 Chip Revision AQ Description Node Boka i POE Sys image GUIDs 0002c90001777050 0002c90001777051 0002c90001777052 0002c90001777053 MACs OU Zee Wee 0002c9777052 Board ID n a MT 0440110002 VOD n a Bore MT 04A0110002 On 4th Generation Devices On 4th generation devices the sg command can operate on both the image file and the image on the flash When running the sg command on an image on the flash if the GUIDs MACs UIDs in the image are non blank the fli
59. tX 3 2 3 1 Additional mixburn Options The following is a list of additional options Please see Chapter 3 flint Firmware Burner for the HCA options and Chapter 4 spark Switch Firmware Burning for the switch options For adapters bridges and 4th generation switches ao a aee Wises a las psi a quis E a E a S log blank guids flash params allow psid change no flash verify use image rom Override cache replacement Suse images guias panel For InfiniScale III switches UI ss quasi nes ie Eee Messo 2 4 Examples of mlxburn Usage 2 4 1 Host Channel Adapter Examples e To update firmware on an MT25408 ConnectX adapter device with the configuration file 1n1 auto detected enter mlxburn fw fw 25408 rel mlx dev dev mst mt25418 pci cr0 e To generate a failsafe image file for the same adapter above without burning enter mlxburn fw fw 25408 rel mlx conf MHEH28 XTC Al ini wrimage fw 25418 bin e To update firmware on the same adapter above with the configuration file in1 explic itly specified enter mlxburn fw fw 25408 rel mlx dev dev mst mt25418 pci cr0 conf MHEH28 XTC Al ini 2 4 2 SwitchX Switch Examples e Burn an MSX6025 switch system using the In Band access method mlxburn dev dev mst SW MT51000 000002c900002100 lid 0x000E fw fw sx mlx 1 The arguments of the guids and macs flags must be provided within quotation marks for example mlxburn macs
60. ying the Node and System GUIDs Note that 4 guids in quotes should be specified as an argument to the guids flag The 2 middle GUIDs are ignored by the InfiniScaleIV and should be set to 0 mlxburn dev dev mst mtusb 1 fw fw IS4 mlx conf MTS36000 1UNC Al ini guids 0002c9000100d060 0 0 0002c9000100d060 nofs Mellanox Technologies 17 J Rev 1 50 mixburn FW Image Generator Burner e Generate and Burn a new MT3600 switch system via I2C in 2 steps a Generate the image mlxburn fw fw IS4 mlx conf MTS36000 1UNC Al ini wrimage fw is4 bin b Burn using flint tool flint d dev mst mtusb 1 i tmp fw is4 bin nofs guids 0002c9000100d060 0 0 0002c9000100d060 b e To generate an MT48436 image and perform an In Band update of the device with LID 0x18 enter mlxburn fw fw IS4 mlx dev lid 0x18 2 4 4 BridgeX Gateway Examples e To update firmware on BridgeX device with the configuration file ini auto detected enter mlxburn d dev mst mt64102 pci crl fw fw BridgeX rel mlx e To generate a failsafe image file for the same BridgeX above without burning enter mlxburn fw fw BridgeX rel mlx conf MTB4020 PC0 Al ini wrimage fw BridgeX bin e To update firmware on the same BridgeX above with the configuration file ini explicitly specified enter mlxburn fw fw BridgeX rel mlx dev dev mst mt64102 pci crl conf MTB4020 PC0 Al ini e To burn a firmware binary file for a BridgeX device
Download Pdf Manuals
Related Search