Forums - Met libdspCV_skel.so No such file or directory when run samples

8 posts / 0 new
Last post
Met libdspCV_skel.so No such file or directory when run samples
nt31921a
Join Date: 26 Feb 14
Posts: 1
Posted: Wed, 2014-06-04 05:31

Hi all,

We met below error message when we run samples

 

D/fastcv_lib_log(19867): Warning: AvailableHwComponent is 0. undefined symbol: fcvAvailableHWComponent
E/adsprpc (19867): vendor/qcom/proprietary/adsprpc/src/listener_android.c:107:listener using ion heap: -1
E/adsprpc (19867): vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: ./libdspCV_skel.so No such file or directory
E/adsprpc (19867): vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/lib/rfsa/adsp/./libdspCV_skel.so No such file or directory
 
But we have those so file in /system/venodr/lib and we use 8974 platform.
 # ls /system/vendor/lib/rfsa/adsp/                               
libdspCV_skel.so
libfastcvadsp.so
libfastcvadsp_skel.so
 
Do anyone tell us what is going on with this issue??
 
Thanks a lot for any help can provided.
Yuching

 

  • Up0
  • Down0
jeff4s Moderator
Join Date: 4 Nov 12
Posts: 106
Posted: Wed, 2014-06-04 19:09

Hi,

These error messages are confusing but harmless. The files in question could be located in multiple default locations and will be searched one after another. An error message will be issued if they are not found. However as long as these files are in one of the default locations such as  /system/vendor/lib/rfsa/adsp/ then DSP implementation should be functional.

Cheers,

-Jeff

  • Up0
  • Down0
razvan23
Join Date: 24 Mar 13
Posts: 4
Posted: Tue, 2015-07-21 07:35

Hi, my app crashes with a similar error, I have had no luck in fixing it:

 

07-21 17:31:25.398: E/adsprpc(14224): vendor/qcom/proprietary/adsprpc/src/listener_android.c:107:listener using ion heap: -1
07-21 17:31:25.398: E/adsprpc(14224): vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: ./libdspCV_skel.so No such file or directory
07-21 17:31:25.398: E/adsprpc(14224): vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:33:apps_std fopen failed: /system/lib/rfsa/adsp/./libdspCV_skel.so No such file or directory
07-21 17:31:25.448: A/libc(14224): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 14777 (ay.driveassist2)
 
 
It crashes on Galaxy S5, but I also tested on a Moto G (1st gen) and it works ok. Any ideas?
  • Up0
  • Down0
ronaldk
Join Date: 9 Oct 12
Posts: 30
Posted: Tue, 2015-07-21 16:06

Hi Razvan,

Do you have more detail logcat after Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 14777 (ay.driveassist2) ?

Have you tried to do software update for your Samsung Galaxy S5?

Forcing FastCV to run only at CPU, by calling fcvSetOperationMode(FASTCV_OP_CPU_PERFORMANCE), might help you avoid the crash untill we find out the root cause and fix it.

Thanks.

  • Up0
  • Down0
ronaldk
Join Date: 9 Oct 12
Posts: 30
Posted: Tue, 2015-07-21 16:08
Hi Razvan,
 
Do you have more detail logcat after Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 14777 (ay.driveassist2) ?
Have you tried to do software update for your Samsung Galaxy S5?
Forcing FastCV to run only at CPU, by calling fcvSetOperationMode(FASTCV_OP_CPU_PERFORMANCE), might help you avoid the crash untill we find out the root cause and fix it.
 
Thanks.
  • Up0
  • Down0
razvan23
Join Date: 24 Mar 13
Posts: 4
Posted: Wed, 2015-07-22 04:27

No logs after that, the app crashes and that's it.

It worked with your suggestion (FASTCV_OP_CPU_PERFORMANCE).. The Galaxy S5 has Android 4.4.2.

  • Up0
  • Down0
ariel.benitah
Join Date: 14 Apr 15
Posts: 5
Posted: Tue, 2015-08-18 06:30

Any progress on this issue?... I have encountered the same problem when running my code on Samsung S3.

thanks for your help.

  • Up0
  • Down0
jeff4s Moderator
Join Date: 4 Nov 12
Posts: 106
Posted: Tue, 2015-08-18 10:21

Hi,

Those messages are harmless. If your app crashes please provide a detailed log.

Cheers,

-Jeff

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