Installing CANN
Prerequisites
Before installation, ensure that the Python environment and pip3 are available. CANN currently supports Python versions 3.7.x to 3.14.x. If this requirement is not met, run the following commands to install them:
1 | sudo apt-get install -y python3 python3-pip |
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.
Installing the Toolkit Development Kit
Install the CANN Toolkit for training, inference, and debugging. It supports training and inference services, model conversion, and developing and building operators, applications, and models.
Before installing the Toolkit, make sure the installation directory has more than 10 GB of free space. If not, clear some space or choose another directory.
Architecture |
Installation Command |
||
|---|---|---|---|
aarch |
|
||
x86_64 |
|
The installation command supports parameters such as --install-path=<path>. For details, see Parameter Description. If you do not specify an installation path, the software is installed to the default path. For the root user, the default path is /usr/local/Ascend. For a non-root user, the default path is ${HOME}/Ascend, where ${HOME} indicates the current user directory.
1 | source ${HOME}/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 ops
The CANN ops package integrates a comprehensive suite of libraries, including the operator foundational framework, operator libraries (covering math, nn, cv, transformer, and ras), 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) workloads.
Before installing ops, ensure that the Toolkit of a compatible version has been installed in the same path. Select the ops software package corresponding to the running device. Installing ops for multiple chips in the same path is not supported. To work with different chips, install the Toolkit and the related ops in separate paths for multi-chip development and deployment.
Product Type |
Architecture |
Installation Command |
||
|---|---|---|---|---|
Ascend 950 products |
aarch |
|
||
x86_64 |
|
|||
Atlas A3 products |
aarch |
|
||
x86_64 |
|
|||
Atlas A2 products |
aarch |
|
||
x86_64 |
|
|||
Atlas training products |
aarch |
|
||
x86_64 |
|
|||
Atlas inference products |
aarch |
|
||
x86_64 |
|
|||
Atlas 200I/500 A2 inference products |
aarch |
|
||
x86_64 |
|
(Optional) Installing the NNAL
The NNAL comprises the Ascend Transformer Boost (ATB) and AscendSiPBoost (SiP) libraries.
Before installing the ATB, install the Toolkit of the matching version and configure environment variables.
Architecture |
Installation Command |
||
|---|---|---|---|
aarch |
|
||
x86_64 |
|
The installation command supports parameters such as --install-path=<path>. For details, see Parameter Description. If you do not specify an installation path, the software is installed to the default path. For the root user, the default path is /usr/local/Ascend. For a non-root user, the default path is ${HOME}/Ascend, where ${HOME} indicates the current user directory.
- ATB:
1source ${HOME}/Ascend/nnal/atb/set_env.sh
- SiP:
1source ${HOME}/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.