Environment Requirements

The operating environment must have been installed. For details, see the CANN Software Installation Guide.

For security purposes, ensure that the directories and files involved in this document meet the security requirements of your organization when using Ascend-DMI.
In an environment where the npu-driver, npu-firmware, and Toolbox are installed but the NNRT or NNAE is not installed, the following functions in Using the Ascend-DMI Tool can be used properly: help and version information query, real-time device status query, software and hardware compatibility test, driver and firmware compatibility test, and device topology detection. However, bandwidth test, computing power test, power consumption test, and fault diagnosis functions are not available.
The preset installation path of the Ascend-DMI is /home/data/Ascend-DMI on the Atlas 500 AI edge station. For other hardware devices, the default installation path of the root user is /usr/local/Ascend. You can change the installation path as required.
The Atlas 500 AI edge station supports only the root user. It can work correctly only after environment variables are added. Run the following commands as the root user:
```
export LD_LIBRARY_PATH=/home/data/Ascend-DMI/lib64:$LD_LIBRARY_PATH 
export PATH=/home/data/Ascend-DMI/bin:$PATH 
. /opt/ascend/nnrt/set_env.sh
```

Add environment variables. Environment variables are not shared by different users and need to be added separately. The following describes how to add environment variables when the installation user of the CANN software is root.
1. If a specified user is used to run the Ascend-DMI tool, the user must have been added to the running user group of the CANN software. You can run the following command to query the running user group of the CANN software:
  source /etc/ascend_install.info; echo ${UserGroup}
2. The CANN software provides a script for setting process-level environment variables. You can reference the script in processes to automatically configure environment variables. The environment variables automatically become invalid after the processes end. The default installation path of the root user is used as an example.
  - Configure environment variables when installing the Toolbox package.
    - For the Atlas 200 (EP), Atlas 200 (RC), and Atlas 200I SoC A1, run the following commands:
```
export PATH=$PATH:/usr/local/Ascend/toolbox/latest/Ascend-DMI/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/Ascend/toolbox/latest/Ascend-DMI/lib64
```
    - For other devices, run the following commands:
```
. /usr/local/Ascend/toolbox/set_env.sh
```
  - Configured environment when installing the development suite package.
```
. /usr/local/Ascend/ascend-toolkit/set_env.sh
```
  - Configure environment variables when installing the NNRT package.
```
. /usr/local/Ascend/nnrt/set_env.sh
```
  - Configure environment variables when installing the NNAE package.
```
. /usr/local/Ascend/nnae/set_env.sh
```
  You can also configure permanent environment variables by modifying the ~/.bashrc file. The procedure is as follows:
  1. Run the vi ~/.bashrc command in any directory as the running user to open the .bashrc file and append the preceding lines to the file. Ensure that the directory meets the security requirements of your organization.
  2. Run the :wq! command to save the file and exit.
  3. Run the source ~/.bashrc command for the modification to take effect immediately.

Parent topic: Preparations