Version Compatibility
Since the DEEPX SDK maintains strict version dependencies between modules, it is essential to consult the compatibility matrix below when performing updates. DX-AllSuite ensures that all components are integrated and managed in validated, optimal combinations.
DXNN SDK Version Compatibility Matrix
| Release Date | DX-AllSuite | ||||||
|---|---|---|---|---|---|---|---|
| DX-Compiler | DX-Runtime | ||||||
| DX-COM | DX-TRON | DX-FW | NPU Driver | DX-RT | DX-Stream | DX-APP | |
| 2026-08-03 | v2.4.1 | ||||||
| v2.4.1 | v2.4.1 | ||||||
| v2.4.0 | v2.0.1 | v2.7.4 | v2.6.0 | v3.4.1 | v3.1.1 | v3.2.1 | |
| 2026-07-22 | v2.4.0 | ||||||
| v2.4.0 | v2.4.0 | ||||||
| v2.4.0 | v2.0.1 | v2.7.3 | v2.5.1 | v3.4.0 | v3.1.0 | v3.2.0 | |
| 2026-05-14 | v2.3.3 | ||||||
| v2.3.1 | v2.3.3 | ||||||
| v2.3.0 | v2.0.1 | v2.5.6 | v2.4.1 | v3.3.2 | v3.0.1 | v3.1.1 | |
| 2026-05-11 | v2.3.2 | ||||||
| v2.3.1 | v2.3.2 | ||||||
| v2.3.0 | v2.0.1 | v2.5.6 | v2.4.1 | v3.3.2 | v3.0.1 | v3.1.1 | |
| 2026-05-06 | v2.3.1 | ||||||
| v2.3.1 | v2.3.1 | ||||||
| v2.3.0 | v2.0.1 | v2.5.6 | v2.4.1 | v3.3.1 | v3.0.1 | v3.1.1 | |
| 2026-04-10 | v2.3.0 | ||||||
| v2.3.0 | v2.3.0 | ||||||
| v2.3.0 | v2.0.1 | v2.5.6 | v2.4.1 | v3.3.0 | v3.0.0 | v3.1.0 | |
| 2026-02-26 | v2.2.2 | ||||||
| v2.2.1 | v2.2.2 | ||||||
| v2.2.1 | v2.0.1 | v2.5.0 | v2.1.0 | v3.2.0 | v2.2.1 | v3.0.2 | |
| 2026-02-09 | v2.2.1 | ||||||
| v2.2.0 | v2.2.1 | ||||||
| v2.2.0 | v2.0.1 | v2.5.0 | v2.1.0 | v3.2.0 | v2.2.0 | v3.0.1 | |
| 2026-01-16 | v2.2.0 | ||||||
| v2.2.0 | v2.2.0 | ||||||
| v2.2.0 | v2.0.1 | v2.5.0 | v2.1.0 | v3.2.0 | v2.2.0 | v3.0.0 | |
| 2025-11-28 | v2.1.0 | ||||||
| v2.1.0 | v2.1.0 | ||||||
| v2.1.0 | v2.0.0 | v2.4.0 | v1.8.0 | v3.1.0 | v2.1.0 | v2.1.0 | |
| 2025-09-08 | v2.0.0 | ||||||
| v2.0.0 | v2.0.0 | ||||||
| v2.0.0 | v2.0.0 | v2.1.4 | v1.7.1 | v3.0.0 | v2.0.0 | v2.0.0 | |
| 2025-07-23 | v1.0.0 | ||||||
| v1.0.0 | v1.0.0 | ||||||
| v1.60.1 | v0.0.8 | v2.1.0 | v1.5.0 | v2.9.5 | v1.7.0 | v1.11.0 | |
How to Check Your System Version
To ensure system stability, identify the versions of your currently installed components and compare them with the Version Compatibility Matrix provided above.
Step 1. Hardware & Drivers (Target Side)
You can immediately verify the Firmware (FW) and NPU Driver versions using the NPU status utility.
# Display NPU status and driver information
dxrt-cli -s
Step 2. Compiler (Host Side)
Verify the version of the model conversion tool (dxcom). Note that the virtual environment must be activated for the command to be recognized.
# Execute within an activated virtual environment
dxcom -v
Alternative (via Python)
If you are using the compiler as a library, you can also check the version directly via Python.
python3 -c "import dx_com; print(dx_com.__version__)"