Forums - Test signature problem when using Hexagon

4 posts / 0 new
Last post
Test signature problem when using Hexagon
mark2.kim
Join Date: 22 Apr 18
Posts: 1
Posted: Mon, 2019-06-24 01:13
Hi,
 
Now I am trying to use Halide example on Android system using Hexagon SDK.
Before I pushed testsig-xxxxx.so file, I got these errors.
 
01-01 13:01:23.311  7637  7651 E /data/test-hvx128: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig-xxxxx.so. (No such file or directory)
01-01 13:01:23.316  7637  7651 E /data/test-hvx128: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig-xxxxx.so. (No such file or directory)
01-01 13:01:23.317  7637  7651 E /data/test-hvx128: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig-xxxxx.so. (No such file or directory)
01-01 13:01:23.317  7637  7651 E /data/test-hvx128: xxxx/apps_std_imp.c:1020:Error 57: failed to stat testsig-xxxxx.so, file open returned 45, errno is No such file or directory
01-01 13:01:23.318  7637  7651 E /data/test-hvx128: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig-xxxxx.so. (No such file or directory)
01-01 13:01:23.321  7637  7651 E /data/test-hvx128: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig.so. (No such file or directory)
01-01 13:01:23.321   993  1085 E /vendor/bin/cdsprpcd: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig.so. (No such file or directory)
 
After I did some process creating and pushing testsig-xxxxx.so file to device,
I still have these errors.
 
01-01 13:01:48.873 10486 10530 E /data/test-hvx128: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig.so. (No such file or directory)
01-01 13:01:48.874   993  1085 E /vendor/bin/cdsprpcd: xxxx/apps_std_imp.c:729:Error 45: fopen failed for testsig.so. (No such file or directory)
 
are testsig-xxxxx.so and testsig.so diffrenent library?
If then, could you tell me how can I create testsig.so and where I have to push it?
  • Up0
  • Down0
alu0100948226
Join Date: 12 Mar 19
Posts: 5
Posted: Fri, 2019-07-05 04:31

hi!

To create the testsig you can use the script provided by the SDK, further instructions on it are in the Hexagon SDK docs under the signing section. The testsig file must be pushed to /vendor/lib/rfsa/adsp or at least I have it that way. and it's working fine, Hope this help you fix your problem

  • Up0
  • Down0
alu0100948226
Join Date: 12 Mar 19
Posts: 5
Posted: Fri, 2019-07-05 04:32

hi!

To create the testsig you can use the script provided by the SDK, further instructions on it are in the Hexagon SDK docs under the signing section. The testsig file must be pushed to /vendor/lib/rfsa/adsp or at least I have it that way. and it's working fine, Hope this help you fix your problem

  • Up0
  • Down0
371152061
Join Date: 13 May 22
Posts: 11
Posted: Wed, 2022-06-22 01:55

 

I have this file, but still not found

 

polaris:/vendor/lib/rfsa/adsp # pwd

/vendor/lib/rfsa/adsp
polaris:/vendor/lib/rfsa/adsp # ls -l test*
-rw-r----- 1 root root 24784 2022-06-22 16:11 testsig-0x16194c0a.so
 
 
 
fastcv log:
 
2022-06-22 16:48:54.301 7403-7403/com.baidu.snpe D/fastcv_lib_log: Fastcv vendor library
2022-06-22 16:48:54.301 7403-7403/com.baidu.snpe D/fastcv_lib_log: Fastcv vendor library
2022-06-22 16:48:54.301 7403-7403/com.baidu.snpe I/fastcv_lib_log: QCVAQ6_deinit
2022-06-22 16:48:54.302 7403-7403/com.baidu.snpe D/fastcv_lib_log: Begin of domain_channel_open cdsp_domain_handle=0x743e8faf18  value of cdsp_domain_handle=0
2022-06-22 16:48:54.304 7403-7403/com.baidu.snpe I/com.baidu.snpe: Successfully opened fastrpc_shell_3
2022-06-22 16:48:54.335 7403-7403/com.baidu.snpe I/com.baidu.snpe: Successfully created user PD on domain 3 (attrs 0x0, debug_trace 0x0)
2022-06-22 16:48:54.337 7403-7403/com.baidu.snpe I/com.baidu.snpe: fastrpc_perf_init: enabled RPC traces (kernel 0, dsp 0) with frequency 1000
2022-06-22 16:48:54.342 7403-7537/com.baidu.snpe W/com.baidu.snpe: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:749: Warning: fopen returned 0x2 for file testsig-0x16194c0a.so. (No such file or directory)
2022-06-22 16:48:54.343 7403-7537/com.baidu.snpe W/com.baidu.snpe: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:749: Warning: fopen returned 0x2 for file testsig.so. (No such file or directory)

 

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