Forums - snpe-platform-validator fails for DSP on Pixel 4 (Snapdragon 855)

7 posts / 0 new
Last post
snpe-platform-validator fails for DSP on Pixel 4 (Snapdragon 855)
aurelien
Join Date: 16 Jan 23
Posts: 5
Posted: Fri, 2023-05-05 07:01

Hi, I am new to SNPE and trying to first get the `snpe-platform-validator` to run for DSP.

I am using `snpe-2.9.0.4462` and a Google Pixel 4 on Android 13 with a Snapdragon 855 (SM8150).
 
According to the SDK documentation in `snpe-2.9.0.4462/doc/html/overview.html`, section "Supported Snapdragon Devices", the Qualcomm Snapdragon 855 is supported CPU, GPU, DSP and AIP runtimes.

 

With the Pixel 4 connected to my PC (Ubuntu 22.04.2 LTS) via usb, here's what I'm doing:

```

cd ~/Downloads/snpe-2.9.0.4462/

adb push ./bin/aarch64-android-clang8.0/snpe-platform-validator /data/local/tmp/platformValidator/snpe-platform-validator
adb push ./lib/aarch64-android-clang8.0/ /data/local/tmp/platformValidator/lib/
adb push ./lib/dsp/ /data/local/tmp/platformValidator/dsp/
 
adb shell
 
cd /data/local/tmp/platformValidator/
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/data/local/tmp/platformValidator/lib
export ADSP_LIBRARY_PATH="/data/local/tmp/platformValidator/dsp/;/system/lib/rfsa/adsp;/system/vendor/lib/rfsa/adsp;/dsp"
 
ls /data/local/tmp/platformValidator/dsp/
libSnpeDspV65Skel.so  libSnpeDspV66Skel.so  libSnpeHtpV68Skel.so  libSnpeHtpV69Skel.so  libSnpeHtpV73Skel.so  libcalculator_skel.so
 
ls /data/local/tmp/platformValidator/lib/
libPlatformValidatorShared.so  libSNPE.so  libSnpeHta.so  libSnpeHtpPrepare.so  libc++_shared.so  libcalculator.so  libcalculator_htp.so  libhta_hexagon_runtime_snpe.so
 
./snpe-platform-validator --runtime dsp --debug --coreVersion --libVersion --testRuntime
```
 
And obtain the following result:
```
PF_VALIDATOR: DEBUG: Calling PlatformValidator->setRuntime
PF_VALIDATOR: DEBUG: Calling PlatformValidator->RuntimeCheck
PF_VALIDATOR: DEBUG: Setting up QnnBackend
DspTransport.openSession qnn_open failed, 0x00000200
IDspTransport: Unknown rpc status 0x00000200
DspTransport failed,cannot open session, error 0xffffffff
DspTransport.openSession qnn_open failed, 0x00000200
IDspTransport: Unknown rpc status 0x00000200
DspTransport failed,cannot open session, error 0xffffffff
PF_VALIDATOR: ERROR: Snpe-QNN backend initialization failed
PF_VALIDATOR: DEBUG: CPU side validation passed.
 
PF_VALIDATOR: DEBUG: starting calculator test
PF_VALIDATOR: DEBUG: Loading DSP stub: libcalculator.so
PF_VALIDATOR: DEBUG: Successfully loaded DSP library - 'libcalculator.so'.  Setting up pointers.
PF_VALIDATOR: ERROR: -2 . Error while executing the sum function.
PF_VALIDATOR: ERROR: Please use testsig if using unsigned images.
PF_VALIDATOR: ERROR: Also make sure ADSP_LIBRARY_PATH points to directory containing skels.
Unit Test on the runtime DSP: Failed.
SNPE is NOT supported for runtime DSP on the device.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->IsRuntimeAvailable
PF_VALIDATOR: DEBUG: CPU side validation passed.
 
PF_VALIDATOR: DEBUG: starting calculator test
PF_VALIDATOR: DEBUG: Loading DSP stub: libcalculator.so
PF_VALIDATOR: DEBUG: Successfully loaded DSP library - 'libcalculator.so'.  Setting up pointers.
PF_VALIDATOR: ERROR: -2 . Error while executing the sum function.
PF_VALIDATOR: ERROR: Please use testsig if using unsigned images.
PF_VALIDATOR: ERROR: Also make sure ADSP_LIBRARY_PATH points to directory containing skels.
Runtime DSP Prerequisites: Absent.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->GetLibVersion
PF_VALIDATOR: ERROR: The fastRPC library version is not implemented yet.
 
Library version of the runtime DSP: Not Found.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->GetCoreVersion
Core Version of the runtime DSP: Hexagon Architecture V66
```
 
Am I missing something here? Is this SoC really supported for DSP?
 
Thanks for your help.
  • Up0
  • Down0
weihuan
Join Date: 12 Apr 20
Posts: 270
Posted: Fri, 2023-05-05 08:37

Dear developer,

855 was latency plarform for SNPE SDK support. 

Could you help to convert your models on SNPE SDK 2.9 on Ubuntu18.04 and push to you device for verification?

BR.

Wei

  • Up0
  • Down0
aurelien
Join Date: 16 Jan 23
Posts: 5
Posted: Tue, 2023-05-09 02:10
Thanks for your reply Wei. I am not using any models, just trying to make sure my device/SoC is supported for DSP runtime by running the snpe-platform-validator tool.
 
Are you suggesting that I use a different tool / application to check that?
  • Up0
  • Down0
zhangjun141
Join Date: 24 Jun 23
Posts: 4
Posted: Wed, 2023-07-12 03:35

i met this problem.have you solved this problem?

  • Up0
  • Down0
mchuh
Join Date: 1 Aug 23
Posts: 4
Posted: Mon, 2023-08-28 18:29

Hello, I met the same issue:
```

sdm845:/data/snpe-2.10 # ./bin/snpe-platform-validator --runtime dsp --debug --coreVersion --libVersion --testRuntime
/system/bin/sh: ./bin/snpe-platform-validator: inaccessible or not found
127|sdm845:/data/Kong/snpe-2.10 # ./bin/aarch64-android-clang8.0/snpe-platform-validator --runtime dsp --debug --coreVersion --libVersion --testRuntime                                                           
PF_VALIDATOR: DEBUG: Calling PlatformValidator->setRuntime
PF_VALIDATOR: DEBUG: Calling PlatformValidator->RuntimeCheck
PF_VALIDATOR: DEBUG: Setting up QnnBackend
DspTransport.openSession qnn_open failed, 0xfffffffb
IDspTransport: Unknown rpc status 0xfffffffb
DspTransport failed,cannot open session, error 0xffffffff
DspTransport.openSession qnn_open failed, 0xfffffffb
IDspTransport: Unknown rpc status 0xfffffffb
DspTransport failed,cannot open session, error 0xffffffff
PF_VALIDATOR: ERROR: Snpe-QNN backend initialization failed
PF_VALIDATOR: DEBUG: CPU side validation passed.
 
PF_VALIDATOR: DEBUG: starting calculator test
PF_VALIDATOR: DEBUG: Loading DSP stub: libcalculator.so
PF_VALIDATOR: DEBUG: Successfully loaded DSP library - 'libcalculator.so'.  Setting up pointers.
PF_VALIDATOR: ERROR: -2 . Error while executing the sum function.
PF_VALIDATOR: ERROR: Please use testsig if using unsigned images.
PF_VALIDATOR: ERROR: Also make sure ADSP_LIBRARY_PATH points to directory containing skels.
Unit Test on the runtime DSP: Failed.
SNPE is NOT supported for runtime DSP on the device.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->IsRuntimeAvailable
PF_VALIDATOR: DEBUG: CPU side validation passed.
 
PF_VALIDATOR: DEBUG: starting calculator test
PF_VALIDATOR: DEBUG: Loading DSP stub: libcalculator.so
PF_VALIDATOR: DEBUG: Successfully loaded DSP library - 'libcalculator.so'.  Setting up pointers.
PF_VALIDATOR: ERROR: -2 . Error while executing the sum function.
PF_VALIDATOR: ERROR: Please use testsig if using unsigned images.
PF_VALIDATOR: ERROR: Also make sure ADSP_LIBRARY_PATH points to directory containing skels.
Runtime DSP Prerequisites: Absent.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->GetLibVersion
PF_VALIDATOR: ERROR: The fastRPC library version is not implemented yet.
 
Library version of the runtime DSP: Not Found.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->GetCoreVersion
Core Version of the runtime DSP: Hexagon Architecture V65
```
  • Up0
  • Down0
mengweiw
Join Date: 26 Nov 23
Posts: 4
Posted: Tue, 2023-12-05 23:15

Dear developer,

I used the same command in the 'snpe-2.9.0.4462' sdk without any errors. I found that 'libSnpeDspV66Stub.so' is missing from your '/data/local/tmp/platformValidator/lib/' library, so I think you can re-download the SNPE-2.9 sdk and try again.

BRs

  • Up0
  • Down0
mengweiw
Join Date: 26 Nov 23
Posts: 4
Posted: Tue, 2023-12-05 23:40

Dear developer,

I used the same command in the 'snpe-2.9.0.4462' sdk without any errors. I found that 'libSnpeDspV66Stub.so' is missing from your '/data/local/tmp/platformValidator/lib/' library, so I think you can re-download the SNPE-2.9 sdk and try again.

BRs

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.