Forums - Issues when using snpe-sample

4 posts / 0 new
Last post
Issues when using snpe-sample
xiafan.su
Join Date: 22 Mar 22
Posts: 4
Posted: Mon, 2022-04-25 01:39

Hi,

I can get snpe-sample and snpe-net-run work for various models and targets(cpu, dsp, aip) in my XR2 device.

But recently when I try to run a model with aip, it works for snpe-net-run, but would fail with snpe-sample with following errors:

PICOA7H10:/data/local/tmp/snpe-sample $ ./snpe-sample -d aip/visbranch_alldata_47_quantized.dlc -i aip/raw_images.lst -r aip                                                                                                                                       

SNPE Version: 1.59.0.3230

npu_get_property status: 0

npu_get_property status: 0

FW CAPS [0] = 0x2007

FW CAPS [1] = 0x5

FW CAPS [2] = 0x0

FW CAPS [3] = 0x0

FW CAPS [4] = 0x0

FW CAPS [5] = 0x0

FW CAPS [6] = 0x0

FW CAPS [7] = 0x0

npu_get_property status: 0

NPU User Driver: npu_read_info 0

npu_get_property status: 0

npu_get_property status: 0

FW CAPS [0] = 0x2007

FW CAPS [1] = 0x5

FW CAPS [2] = 0x0

FW CAPS [3] = 0x0

FW CAPS [4] = 0x0

FW CAPS [5] = 0x0

FW CAPS [6] = 0x0

FW CAPS [7] = 0x0

npu_get_property status: 0

Error while building SNPE object.

I know the error comes from SNPEBuilder, but there is no helpful diagnostic logs for me to debug.

 

Could anyone help, thanks a lot in advance!

  • Up0
  • Down0
xiafan.su
Join Date: 22 Mar 22
Posts: 4
Posted: Mon, 2022-04-25 01:42

I also tried snpe-1.61.0.3358, still no luck.

  • Up0
  • Down0
xiafan.su
Join Date: 22 Mar 22
Posts: 4
Posted: Tue, 2022-04-26 19:31

We noticed that snpe-net-run also fails the AIP run, it just fallback to DSP siliently. We figured out this by checking the md5sum of the results, AIP turns out to have identical results with DSP...

  • Up0
  • Down0
bernicerossen
Join Date: 27 Apr 22
Posts: 10
Posted: Wed, 2022-04-27 09:55

snpe-net-run is not working on my end as well. this issue needs to be resolved soon.

  • 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.