Forums - QNN passed UT but qnn-net-run get empty

3 posts / 0 new
Last post
QNN passed UT but qnn-net-run get empty
mmlmonkey
Join Date: 12 Oct 22
Posts: 3
Posted: Wed, 2023-06-14 02:48

when i run qnn-platform-validator --backend=dsp --libVersion --coreVersion --testBackend  on SA8295P 

it got passed . log is here 

dhu:/data/local/tmp/resnet18 # ../bin/qnn-platform-validator --backend=dsp --libVersion --coreVersion --testBackend                                                                              
PF_VALIDATOR: DEBUG: Calling PlatformValidator->setBackend
PF_VALIDATOR: DEBUG: Calling PlatformValidator->isBackendHardwarePresent
PF_VALIDATOR: DEBUG: Calling PlatformValidator->isBackendAvailable
PF_VALIDATOR: DEBUG: Should be able to access atleast one of libraries from : libc.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libc.so
PF_VALIDATOR: DEBUG: Should be able to access atleast one of libraries from : libadsprpc_system.so,libcdsprpc_system.so,libadsprpc.so,libcdsprpc.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libadsprpc_system.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libcdsprpc_system.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libadsprpc.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libcdsprpc.so
Backend DSP Prerequisites: Present.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->getLibVersion
PF_VALIDATOR: ERROR: The fastRPC library version is not implemented yet.
 
Library version of the backend DSP: Not Found.
PF_VALIDATOR: DEBUG: Calling PlatformValidator->getCoreVersion
Core Version of the backend DSP: Hexagon Architecture V68
PF_VALIDATOR: DEBUG: Calling PlatformValidator->backendCheck
PF_VALIDATOR: DEBUG: Should be able to access atleast one of libraries from : libc.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libc.so
PF_VALIDATOR: DEBUG: Should be able to access atleast one of libraries from : libadsprpc_system.so,libcdsprpc_system.so,libadsprpc.so,libcdsprpc.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libadsprpc_system.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libcdsprpc_system.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libadsprpc.so
PF_VALIDATOR: DEBUG: dlOpen successfull for library : libcdsprpc.so
PF_VALIDATOR: DEBUG: Starting calculator test
PF_VALIDATOR: DEBUG: Loading sample stub: libQnnHtpV68CalculatorStub.so
PF_VALIDATOR: DEBUG: Successfully loaded DSP library - 'libQnnHtpV68CalculatorStub.so'.  Setting up pointers.
PF_VALIDATOR: DEBUG: Success in executing the sum function
Unit Test on the backend DSP: Passed.
QNN is supported for backend DSP on the device.
*********** Results Summary ***********
Backend = DSP
{
  Backend Hardware  : Supported
  Backend Libraries : Found
  Library Version   : Not Found
  Core Version      : Hexagon Architecture V68
  Unit Test         : Passed
}

but when i use qnn-net-run  like this

./qnn-net-run --backend ../lib/libQnnHtp.so  --input_list target_raw_list.txt --retrieve_context libresnet18_quantized.serialized.bin --output_dir result

it got empyt in result folder

how can i make it run correctly 

 

update logcat error log 

01-01 23:36:37.140  9524  9524 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2655: Error 0x2: open_shell failed for domain 3 search paths used are /dsp/, /vendor/dsp/, /vendor/dsp/xdsp/ (errno No such file or directory)
01-01 23:36:37.167  9524  9526 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /data/local/tmp/libdsp/qnn-net-run.farf. (No such file or directory)
01-01 23:36:37.167  9524  9526 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/lib/rfsa/adsp/qnn-net-run.farf. (No such file or directory)
01-01 23:36:37.167  9524  9526 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/dsp/qnn-net-run.farf. (No such file or directory)
01-01 23:36:37.200  9524  9524 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1325: Error 0x80000406: remote_handle_open_domain: dynamic loading failed for file:///libQnnHtpV68Skel.so?qnn_skel_handle_invoke&_modver=1.0&_dom=cdsp on domain 3 (dlerror _rtld_map_object_ex: cannot open libc++.so.1, errno 2 (no such file or directory)) (errno
01-01 23:36:37.200  9524  9524 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1398: Error 0x80000406: remote_handle64_open failed for file:///libQnnHtpV68Skel.so?qnn_skel_handle_invoke&_modver=1.0&_dom=cdsp (errno Success)
01-01 23:36:37.203  9524  9525 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1200: Error 0x4e: remote_handle_invoke failed for handle 0x3, method 4 on domain 3 (sc 0x4020200) (errno Operation not permitted)
01-01 23:36:37.203  9524  9525 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1200: Error 0x4e: remote_handle_invoke failed for handle 0x3, method 4 on domain 3 (sc 0x4020200) (errno Operation not permitted)
01-01 23:36:37.204  9524  9525 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/listener_android.c:221:Error 0x4e: listener response with result 0x0 for ctx 0x15d65, handle 0xdf89e8e8, sc 0xffffffff failed : listener thread exited (errno Operation not permitted)
01-01 23:36:37.204  9524  9525 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1222: Error 0x4e: remote_handle64_invoke failed for handle 0x932a5b90, method 3 on domain 3 (sc 0x3000000) (errno Operation not permitted)
01-01 23:36:37.205  9524  9524 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/listener_android.c:64::error: 512: AEE_SUCCESS == (nErr = mod_table_close(handle, errStr, errStrLen, dlErr))
01-01 23:36:37.205  9524  9524 E qnn-net-run: vendor/qcom/proprietary/adsprpc/src/listener_android.c:64::error: 512: AEE_SUCCESS == (nErr = mod_table_close(handle, errStr, errStrLen, dlErr))
  • Up0
  • Down0
weihuan
Join Date: 12 Apr 20
Posts: 270
Posted: Fri, 2023-06-16 18:38

Dear developer,

What's platform you have used? Is Auto, Mobile or other soc?

BR.

Wei

  • Up0
  • Down0
mmlmonkey
Join Date: 12 Oct 22
Posts: 3
Posted: Mon, 2023-06-19 02:05

Auto. Tier1 is aptiv . 

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