Running PowerServe on SA8295

[cwplugovrai]

Hi all,
first i really like the project, its very well organized.
I currently struggle to get it run on an 8295.

I compiled the project with:
cmake -B build
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_TOOLCHAIN_FILE=$NDK/build/cmake/android.toolchain.cmake
-DANDROID_ABI=armeabi-v7a
-DANDROID_PLATFORM=android-35
-DGGML_OPENMP=OFF
-DPOWERSERVE_WITH_QNN=ON
-DPOWERSERVE_ENABLE_HTPRPCPOLL=OFF
-DPOWERSERVE_ENABLE_HMXPWRCFG=OFF
-DPOWERSERVE_USE_DUMMY=ON

When i try to run it. It complained about missing libc++.so.1 and libc++abi.so.1
I fixed that by adding both to qnn_libs. Nevertheless i still dont get it running.
Maybe i have wrong library versions.
Here is the output i get:

scylla_arm64_vendor:/data/local/tmp/proj/bin # ./powerserve-server -d ..
[INFO ] Compiled on: Sep 26 2025 at 13:50:35
[INFO ] QNN core API version: 2.22.0
[INFO ] QNN backend API version: 5.29.0
[INFO ] QNN system API version: 1.2.0
[INFO ] QNN backend properties:
[INFO ] - Create context from binary list: Yes
[INFO ] - Dynamic batch: Yes
[INFO ] - Early termination: No
[INFO ] - Dynamic dimensions: Yes
[INFO ] - Blockwise quantization: Unknown
[INFO ] - Blockwise quantization with expansion: Unknown
[INFO ] - Vector quantization: Unknown
[INFO ] - Tensor sparsity: Yes
[INFO ] - Updateable application tensor: Yes
[INFO ] - Updateable native tensor: Yes
[INFO ] - Updateable static tensor: Yes
QnnDsp DspTransport.openSession qnn_open failed, 0x80000406, prio 100
QnnDsp IDspTransport: Unable to load lib 0x80000406
QnnDsp DspTransport failed,cannot open session, error 0x00000008
QnnDsp Unable to load Skel Library. transportStatus: 8
QnnDsp Failed to retrieve skel build id: err: 1008
QnnDsp Failed to create transport for device, error: 1008
QnnDsp Failed to load skel, error: 1008
QnnDsp Transport layer setup failed: 1008
QnnDsp Failed to parse default platform info: 1008
QnnDsp Failed to load default platform info: 1008
QnnDsp Failed to parse platform config: 1008
libc++abi: terminating due to uncaught exception of type powerserve::EnvironmentException: [Exception][QNN] BasicException: EnvironmentException
[Exception][QNN] EnvironmentException: failed to create QNN device
[Exception][QNN] System error: Success

Anybody who successfully ran it on 8295?

Thanks
Cornelius

[SorryMaker2022]

@cwplugovrai This has also troubled us for weeks before we adapted the project to SA8295. The problem is, you have to get THE CORRECT SET of libraries.

Here is a quick fix worthy of trying:
First acquire the correct version of Hexagon Tools from Qualcomm (we were using Hexagon Tools 8.4.03 by then), you can use QPM CLI or anything you like. Assume you put your files in $Hexagon_tools. Then the correct files are:

$Hexagon_tools/8.4.03/Tools/target/hexagon/lib/v68/G0/pic/libc++.so.1
$Hexagon_tools/8.4.03/Tools/target/hexagon/lib/v68/G0/pic/libc++abi.so.1

Push them into your device and try again. I am not sure how your linker will behave so I will not give instructions on the file paths, as there are some other Android system libraries of the same name. A quick method is to put the libraries in the same directory with your executable and run the executable in the directory. Or you can try to check the linking priorities and figure out where this file should be.

You can check the difference of the libraries by using readelf -a libxxx.so, I have forgotten what it should print, but pay attention to the ISA and file class part.

[SorryMaker2022]

Here's a full view of how the error we met was raised, if the method provided above does not work, I hope this will give you a clue:

Qualcomm SDKs uses a series of libraries, some run on the Hexagon NPU (For example, ***Skel.so), some run on the ARM CPU (For example, ***Stub.so).

The two libraries above are the necessary libraries on the NPU side but not installed by default in some devices. Besides there are two libraries with the same name in the Android system.

So when the program links libc++ and libc, it tries to link the system libraries and fail. Sometimes QNN reports symbol undefined or something like that, that is because the Android libraries do not contain the symbols in the Skel libraries. I remember there's a variable somewhere in the project that can make the execution log output full debug info and indicate how the error happened.

[cwplugovrai]

That was a good hint, i am already one step closer. I guess i need to convert the model for the 8295 because the 8G3 are propbably not compatible right? or its another libc issue

[INFO ] Load model model-2025_01_14 from ../Llama-3.2-1B-PowerServe-QNN29-8G3/qnn
[INFO ] Loading "llama3_2_1b.bin"...
[INFO ] load binary file ../Llama-3.2-1B-PowerServe-QNN29-8G3/qnn/llama3_2_1b.bin (size: 512659464) into address space [0x6edc7a6000, 0x6efb08f008)
Serializer failed to get context blob.
Fail to get context blob with err 30002
Failed to get context blob meta info or shared blob meta info .etc.
Failed to create context from binary with err 0x7532
libc++abi: terminating due to uncaught exception of type powerserve::EnvironmentException: [Exception][QNN] BasicException: EnvironmentException
[Exception][QNN] EnvironmentException: failed to create QNN context from binary: ../Llama-3.2-1B-PowerServe-QNN29-8G3/qnn/llama3_2_1b.bin
[Exception][QNN] System error: Success
Aborted

[SorryMaker2022]

I believe using an incompatible set of convert settings will fail. But I am not sure about the error code, you can check the docs within your QNN SDK for error 30002 (API / Full API / Error Codes) to see if there are any other errors.

8G3 and 8295 has different HTP architectures. As Qualcomm do not allow other orgs to distribute their SDKs, we offered the dockers of mainstream devices for ease of use. I think it may not be necessary to re-configure a convert environment, but you do need to change the convert settings. You can take a walk through the tools/qnn_converter directory, the entrance is converter.py. We offer options for converting models for other hardware.

BTW, basically SA8295's HTP is a "initial" version, so many advanced features are not supported. If you have access to newer hardware like SA8397, which is much newer, you can probably give up 8295 :D