Installing the Firmware (*.run)

Precautions

• The .run installation packages support one-click installation. You can select parameters as required to complete the installation. For details, see Parameter Description.
• After the .run installation package is used, do not manually set the environment variable export LD_LIBRARY_PATH to the .so file of the original driver package. Otherwise, the tool in the .run installation package may connect to the dynamic library of the earlier version. The third-party library file path and non-run installation package release library file path are not affected.
• During the installation or upgrade of a software package, do not reset or power off the host or device. Otherwise, device boot or upgrade fails. If this problem occurs, resolve it by referring to Failed to Start the Device Due to Reset or Power-off.
• During capacity expansion or spare part replacement, run the npu-smi info -t board -i id command to query the version number. You are advised to use the same firmware version for all Atlas 300I inference cards on the server. If the firmware versions are different, upgrade the firmware first. Otherwise, the server may fail to identify the Atlas 300I inference cards, or the Atlas 300I inference cards are lost during service running. For details, see A Server Fails to Identify an Atlas 300I Inference Card Due to Inconsistent Firmware Versions.

Procedure

1. Upload the driver package obtained from Obtaining Software Packages to any directory (for example, /opt) in Linux.
2. Use PuTTY to log in to the OS CLI of the server where the Atlas 300I inference card (model 3000) is located. For details, see Logging In to the CLI Using PuTTY over a Network Port.
3. Run the following command to switch to the root user:

   su - root

4. Run the following command to go to the directory where the driver package is stored, for example, /opt:

   cd /opt

5. Run the following command to grant the execute permission on the firmware package:

   chmod +x A300-3000-3010-npu-firmware_<version>.run

6. Run the following command to check the consistency and integrity of the .run installation package:

   ./A300-3000-3010-npu-firmware_<version>.run --check

   If the following information is displayed, the installation package verification is successful:

   Verifying archive integrity...  100%   SHA256 checksums are OK. All good.

   The SHA256 encryption mode is used for software package verification. If "./A300-3000-3010-npu-firmware_<version>.run does not contain an embedded MD5 checksum" and "./A300-3000-3010-npu-firmware_<version>.run does not contain a CRC checksum" are displayed during the verification, the MD5 and CRC encryption modes are not used and can be ignored.

7. Run the following command to complete the installation:
   ./A300-3000-3010-npu-firmware_<version>.run --full

   • For details about how to resolve problems that may occur during the installation, see FAQs.
   • The username and user group cannot be specified during firmware installation. The username and user group of the driver are used for installing the firmware.
   • The firmware installation does not support a specified path and uses the driver installation path by default.
   • Default installation path: /usr/local/Ascend
   • Installation log path: /var/log/ascend_seclog/ascend_install.log
   • Path where the installation path, installation command, and user information of the software package after installation are stored: /etc/ascend_install.info
   • If an NPU 20.2.X or later software package is used for installation, the system logs on the device are transmitted to the host using the msnpureport tool for viewing. For details about the export operation and the storage path of the exported logs, see "msnpureport Instructions" in the Ascend 310 Black Box Log Reference.

     In a container, system logs on the device cannot be viewed and cannot be exported using the msnpureport tool.

8. If the system displays a message indicating that the installation is successful, the firmware is successfully installed. Determine whether to restart the system based on the displayed information. If the system needs to be restarted, perform the following operations. Otherwise, skip this step.
   1. After the installation is complete, run the reboot command on the host OS to reboot the host or power off and then power on the host.
   2. After the host is rebooted, the Ascend 310 automatically enters the OS.

9. Run the following command to check the chip firmware version. If the version is the same as the target version, the installation is successful.
   /usr/local/Ascend/driver/tools/upgrade-tool --device_index -1 --component -1 --version

   If the installation path is specified during driver installation, replace /usr/local/Ascend in the command with the actual installation path.