Forums - Failed to run calculator example on DSP: logcat: fopen failed for several files

1 post / 0 new
Failed to run calculator example on DSP: logcat: fopen failed for several files
weiyi.li
Join Date: 15 Apr 19
Posts: 2
Posted: Thu, 2019-10-03 14:38

Hi all,

I am trying the calculator example on Snapdragon 845 using Hexagon SDK 3.4.3. Android NDK version is r14.

I followed the mannual, including the signing part.

The CPU run successfully but DSP failed:

./calculator 0 1000 # run on DSP

- starting calculator test
- allocate 4000 bytes from ION heap
- creating sequence of numbers from 0 to 999
- compute sum on the DSP
Error: compute on DSP failed
 

I used adb logcat to see where the problem is and got following

01-01 17:53:29.464 13094 13094 V ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:1724: Successfully opened fastrpc_shell_3
01-01 17:53:29.488 13094 13094 V ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:1870: Successfully created user PD on domain 3 (attrs 0x0)
01-01 17:53:29.491 13094 13096 D ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:1943: Error 4b: get adsp msgd handle failed. domain 3
01-01 17:53:29.495 13094 13095 E ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:729:Error 45: fopen failed for libadspmsgd_adsp_skel.so. (No such file or directory)
01-01 17:53:29.496  1192  1251 E /vendor/bin/cdsprpcd: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:729:Error 45: fopen failed for libadspmsgd_adsp_skel.so. (No such file or directory)
01-01 17:53:29.497 13094 13096 V ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:1006: remote_handle_open: Successfully opened handle 0xb1906380 for adspmsgd_adsp on domain 3
01-01 17:53:29.497 13094 13095 E ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:729:Error 45: fopen failed for testsig-0x######c.so. (No such file or directory)
01-01 17:53:29.497  1192  1251 E /vendor/bin/cdsprpcd: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:729:Error 45: fopen failed for testsig-0x#####.so. (No such file or directory)
01-01 17:53:29.498 13094 13095 E ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:729:Error 45: fopen failed for testsig.so. (No such file or directory)
01-01 17:53:29.499  1192  1251 E /vendor/bin/cdsprpcd: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/apps_std_imp.c:729:Error 45: fopen failed for testsig.so. (No such file or directory)
01-01 17:53:29.500 13094 13096 E ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/log_config.c:174:Found calculator.farf. adspmsgd enabled
01-01 17:53:29.500 13094 13096 D ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:1925: Error 4b: adsp current process handle failed. domain 3
01-01 17:53:29.500 13094 13096 V ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:1006: remote_handle_open: Successfully opened handle 0xb1909e40 for adsp_current_process on domain 3
01-01 17:53:29.500 13094 13094 D ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:989: Error 0x80000406: remote_handle_open_domain: dynamic loading failed for calculator on domain 3 (dlerror cannot open libadspmsgd_adsp_skel.so)
01-01 17:53:29.500 13094 13094 D ./calculator: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/fastrpc_apps_user.c:925: Error 0x2c: remote_handle_invoke failed for handle 0xffffffff, method 0 on domain 3 (sc 0x20100)
 

When I go into /system/lib/rfsa/adsp/, I can see my testsig-0x####.so file.

Does anyone know how can I get the DSP run the calculator example? Thank you!

 

 

 

 

  • Up0
  • Down0

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.