If the build has finished successfully, you should find the built packages like below.
```console
$ ls ~/GBS-ROOT/local/repos/tizen/aarch64/RPMS/
-npu-engine-2.4.2-1.aarch64.rpm npu-engine-example-2.4.2-1.aarch64.rpm
-npu-engine-devel-2.4.2-1.aarch64.rpm npu-engine-utils-2.4.2-1.aarch64.rpm
+npu-engine-2.5.0-1.aarch64.rpm npu-engine-example-2.5.0-1.aarch64.rpm
+npu-engine-devel-2.5.0-1.aarch64.rpm npu-engine-utils-2.5.0-1.aarch64.rpm
```
## Library Linking
$ cd meta-trinity
$ ls
build conf COPYING.MIT hw README.md recipes-app recipes-bsp recipes-ddk recipes-devtools recipes-kernel
-$ vim recipes-ddk/npu-engine/npu-engine_2.4.2.bb
+$ vim recipes-ddk/npu-engine/npu-engine_2.5.0.bb
[ ... ]
SRC_URI = "git://git@github.sec.samsung.net/AIP/NPU_SystemService.git;protocol=ssh;branch=tizen"
[ ... ]
[ ... ]
$ petalinux-build
$ ls build/tmp/deploy/rpm/aarch64 | grep npu-engine
-npu-engine-2.4.2-r0.aarch64.rpm
-npu-engine-testcases-2.4.2-r0.aarch64.rpm
+npu-engine-2.5.0-r0.aarch64.rpm
+npu-engine-testcases-2.5.0-r0.aarch64.rpm
```
As our FPGA board supports `ssh` connection, the created packages can be simply copied.
```
$ cd build/tmp/deploy/rpm/aarch64/
-$ scp npu-engine-2.4.2-r0.aarch64.rpm root@[FPGA IP Address]:.
-$ scp npu-engine-2.4.2-testcases-r0.aarch64.rpm root@[FPGA IP Address]:.
+$ scp npu-engine-2.5.0-r0.aarch64.rpm root@[FPGA IP Address]:.
+$ scp npu-engine-2.5.0-testcases-r0.aarch64.rpm root@[FPGA IP Address]:.
```
Then, you can install them using `rpm` command in the FPGA board.
```
$ ssh root@[FPGA IP Address]
[ ... ]
-# rpm -ivh npu-engine-2.4.2-r0.aarch64.rpm --force
+# rpm -ivh npu-engine-2.5.0-r0.aarch64.rpm --force
# ls -al /usr/lib/libnpu-engine.so
rwxr-xr-x 1 root root 210872 May 28 05:27 /usr/lib/libnpu-engine.so
-# rpm -ivh npu-engine-testcases-2.4.2-r0.aarch64.rpm --force
+# rpm -ivh npu-engine-testcases-2.5.0-r0.aarch64.rpm --force
# ls -al /usr/lib/npu-engine/bin/
drwxr-xr-x 2 root root 4096 May 28 05:24 apptests
drwxr-xr-x 2 root root 4096 May 28 05:24 unittests
List of devices attached
emulator-26101 device m-0405-1
$ ls -1 RPMS
-libmrpsim-3.8.71-0.i686.rpm
-nnstreamer-trix-engine-2.4.2-0.i686.rpm
-npu-engine-2.4.2-0.i686.rpm
-npu-engine-utils-2.4.2-0.i686.rpm
+libmrpsim-3.8.82-0.i686.rpm
+nnstreamer-trix-engine-2.5.0-0.i686.rpm
+npu-engine-2.5.0-0.i686.rpm
+npu-engine-utils-2.5.0-0.i686.rpm
$ bash install.sh
...
```
If the build has finished successfully, you should find the built packages like below.
```console
$ ls ../*.deb
-../npu-engine_2.4.2_amd64.deb ../npu-engine-example_2.4.2_amd64.deb
-../npu-engine-dev_2.4.2_amd64.deb ../npu-engine-utils_2.4.2_amd64.deb
+../npu-engine_2.5.0_amd64.deb ../npu-engine-example_2.5.0_amd64.deb
+../npu-engine-dev_2.5.0_amd64.deb ../npu-engine-utils_2.5.0_amd64.deb
```
Then, install your packages manually.
```console
-$ dpkg -i ../npu-engine_2.4.2_amd64.deb
+$ dpkg -i ../npu-engine_2.5.0_amd64.deb
$ ls /opt/trinity/lib
libnpu-engine.so
```