Installing CANN (Online Installation Using Yum)

This section describes how to quickly install the CANN software using Yum.

Installing Dependencies

Before installation, ensure that the Python environment and pip3 are available. CANN currently supports Python versions 3.7.x to 3.13.x. If this requirement is not met, run the following commands to install them:
1
sudo yum install -y python3 python3-pip

If the installation fails, the version does not meet the requirements, or the dynamic library libpython3.x.so is not included, perform the operations in Compiling and Installing Python.

Configuring the Ascend Repository

Configure the Ascend repository. Otherwise, the installation will fail.

sudo curl https://repo.oepkgs.net/ascend/cann/ascend.repo -o /etc/yum.repos.d/ascend.repo && yum makecache

Installing the Toolkit

The CANN Toolkit is designed for training, inference, and development and debugging scenarios. It is mainly used for training and inference workloads, model conversion, as well as the development and compilation of operators, applications, and models.

Before installing Toolkit, ensure that the available space of the installation directory is greater than 10 GB. Otherwise, clear the space or change the installation directory.

  1. Run the installation command:
    1
    sudo yum install -y Ascend-cann-toolkit-9.0.0
    

    During online installation using Yum, the Toolkit can be installed only in the default path /usr/local/Ascend directory.

  2. Configure environment variables.
    1
    source /usr/local/Ascend/cann/set_env.sh
    

    The preceding environment variables take effect only in the current window. You can add the preceding command to the environment variable configuration file (for example, the .bashrc file) as required.

Installing the ops

The CANN ops package integrates a comprehensive suite of libraries, including the operator foundational framework, operator libraries (covering math, nn, cv, and transformer), TBE operators, HCCL, HIXL, and the DVPP library. Specifically, it provides dynamic and static library files for single-operator API execution (e.g., aclnn-class APIs), operator source code, and kernel binaries, ultimately optimizing overall execution performance in high-performance computing (HPC) scenarios.

Before installing the ops package, ensure that the Toolkit software package of a compatible version has been installed in the same path. Select the ops software package corresponding to the running device. Currently, installing ops packages for multiple chips under the same path is not supported. You can install the Toolkit and the corresponding ops packages for different chips in separate paths to meet development and deployment requirements in multi-chip environments.

Table 1 Installing the ops

Product Type

Installation Command

Atlas 350 Accelerator Card

1
sudo yum install -y Ascend-cann-950-ops-9.0.0

Atlas A3 series

1
sudo yum install -y Ascend-cann-A3-ops-9.0.0

Atlas A2 series

1
sudo yum install -y Ascend-cann-910b-ops-9.0.0

Atlas training series

1
sudo yum install -y Ascend-cann-910-ops-9.0.0

Atlas inference series

1
sudo yum install -y Ascend-cann-310p-ops-9.0.0

Atlas 200I/500 A2 inference products

1
sudo yum install -y Ascend-cann-310b-ops-9.0.0

(Optional) Installing the NNAL

The NNAL comprises the ATB and SiP libraries.

Before installing the ATB, install Toolkit of the matching version and configure environment variables. Use the same user to do these operations.

  1. Run the installation command:
    1
    sudo yum install -y Ascend-cann-nnal-9.0.0
    

    During online installation using Yum, the Toolkit can be installed only in the default path /usr/local/Ascend directory.

  2. Configure environment variables.
    • ATB:
      1
      source /usr/local/Ascend/nnal/atb/set_env.sh
      
    • SiP:
      1
      source /usr/local/Ascend/nnal/asdsip/set_env.sh
      

    The preceding environment variables take effect only in the current window. You can add the preceding command to the environment variable configuration file (for example, the .bashrc file) as required.