Forums - Hexagon 3.1 camera streaming example crashes

6 posts / 0 new
Last post
Hexagon 3.1 camera streaming example crashes
guillaume.poirier
Join Date: 16 Feb 17
Posts: 7
Posted: Mon, 2017-04-24 13:06

Hello,

I tried the camera streaming add constant example in "Hexagon_SDK/3.1/docs/Camera streaming/Examples.html". EDIT: I also tried with SDK 3.2 to no avail.

When I do setprop persist.camera.hvx_lib_1 "libmmcamera_hvx_add_constant.so" and open the Snapdragon camera app, it crashes.

If I then disable hvx processing with "setprop persist.camera.hvx_lib_1 """ then I can open properly the Snapdragon camera app and see the video stream.

The adb logcat -vthreadtime > log.txt contains some errors. Here is a sample:

01-22 02:31:06.242   889  3948 E         : hvx_lib_fill_function_table:149 hvx_debug
01-22 02:31:06.243   889  3948 E mm-camera: <IFACE ><ERROR> 706: iface_hvx_stub_lib_open: iface_hvx_stub_lib_open:706 hvx_debug dlopen for hvx stub lib libadsp_hvx_stub.so
01-22 02:31:06.243   889  3948 E mm-camera:
01-22 02:31:06.343  3886  3886 V BoostFramework: BoostFramework() : mPerf = com.qualcomm.qti.Performance@b9f608b
01-22 02:31:06.345  3886  3886 V BoostFramework: BoostFramework() : mPerf = com.qualcomm.qti.Performance@8c8a568
01-22 02:31:06.418   889  3948 E adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:171::error: -5: 0 == (nErr = dlerr)
01-22 02:31:06.418   889  3948 D adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:174: dlopen error: adsp_hvx cannot find file or invalid file descriptor: fd=:-1
01-22 02:31:06.419   889  3948 E mm-camera: <IFACE ><ERROR> 736: iface_hvx_stub_lib_open: iface_hvx_stub_lib_open:736 hvx_debug failed: HVX_STUB_EVENT_QUERY_CAPS rc -1
01-22 02:31:06.419   889  3948 E mm-camera:
01-22 02:31:06.419   889  3948 E mm-camera: <IFACE ><ERROR> 1009: iface_hvx_open: iface_hvx_open:1009 hvx_debug failed: iface_hvx_stub_lib_open rc -1

Also, the documention mentions to open the QXDM application to collect the DSP side log, but I cannot find that application installed on the dev board.

Can you please suggest the proper way to run the camera streaming add constant example ?

Many thanks,

Guillaume

  • Up0
  • Down0
chennak
Join Date: 22 Sep 16
Posts: 78
Posted: Wed, 2017-04-26 01:45

May I know the target you are using ? 

Please try with 3.2 SDK (ignore if you already tried)

can you also the share the build details ? 

  • Up0
  • Down0
guillaume.poirier
Join Date: 16 Feb 17
Posts: 7
Posted: Wed, 2017-04-26 07:32

Hi Chennak,

I am using Open-Q u820 APQ8096 dev kit with Android 6.0.1, kernel version is 3.18.20, and BSP 2.2.

I am using the Windows SDK. I also tried the 3.2 SDK but same issue.

I am using GNU make 3.81 built for i386-pc-mingw32 which is located at Hexagon_SDK\3.2\tools\utils\gow-0.8.0\bin\make.exe to build the OEM plugin.

I am building the QDSP6 lib with V=hexagon_Release_dynamic_toolv80_v60

Please let me know if you need any additional information.

Many thanks,

Guillaume

  • Up0
  • Down0
Sammy Chen
Join Date: 23 May 17
Posts: 1
Posted: Thu, 2017-05-25 00:00

Hello,

I tried the camera streaming add constant example in "Hexagon_SDK/3.0/docs/Camera streaming/Examples.html".

When I do setprop persist.camera.hvx_lib_1 "libmmcamera_hvx_add_constant.so" and open the Snapdragon camera app, it crashes.

If I then disable hvx processing with "setprop persist.camera.hvx_lib_1 "123" then I can open properly the Snapdragon camera app and see the video stream.

The adb logcat -vthreadtime > log.txt contains some errors. Here is a sample:

Line 5847: 05-12 04:28:32.773  4603  4972 E         : hvx_lib_fill_function_table:230 hvx_debug 
Line 5849: 05-12 04:28:32.773  4603  4972 E mm-camera: <IFACE ><ERROR> iface_hvx_stub_lib_open: 614: iface_hvx_stub_lib_open:614 hvx_debug dlopen for hvx stub lib libadsp_hvx_stub.so
Line 5863: 05-12 04:28:32.884  4603  4972 D adsprpc : vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:174: dlopen error: adsp_hvx signature verify start failed for libadsp_hvx_skel.so
Line 5865: 05-12 04:28:32.885  4603  4972 E mm-camera: <IFACE ><ERROR> iface_hvx_stub_lib_open: 644: iface_hvx_stub_lib_open:644 hvx_debug failed: HVX_STUB_EVENT_QUERY_CAPS rc -1
Line 5869: 05-12 04:28:32.886  4603  4972 E mm-camera: <IFACE ><ERROR> iface_hvx_open: 869: iface_hvx_open:869 hvx_debug failed: iface_hvx_stub_lib_open rc -1
 
Could you please suggest the proper way to run the camera streaming add constant example ?

Many thanks,
 
Information of platform:
1. msm8996
2. Qualcomm_Hexagon_SDK_3.0
 
Sammy Chen
  • Up0
  • Down0
guillaume.poirier
Join Date: 16 Feb 17
Posts: 7
Posted: Thu, 2017-05-25 07:16

Hello,

Using SDK 3.2 and flashing my dev kit to Android 7.0 and BSP 3.2 now works for me. It is also better to enable dual ISP:

>adb shell setprop persist.camera.isp.dualisp 1

Cheers,

Guillaume

  • Up0
  • Down0
kelvinwang
Join Date: 7 Feb 17
Posts: 1
Posted: Fri, 2017-06-09 05:06

Hi All,

I am Sammy Chen's colleague.

We have finally gone through the troubles to see the twinkling pink light examples with both SDK 3.0 and 3.2.

In addition, we recognized that there had been a version issue of "hvx_lib.h" between our codebase and HVX SDK, which is located in <platform>/vendor/qcom/proprietary/mm-camerasdk/hvx and caused disorder of function table.

With fixing it we could see camera streaming appeared to be working properly.

However, there are still 2 problems.

1. We were still unable to see the added log of adsp side in logcat, even though it is supposed to show as hvx_add_constant is called.

2. The test device is always going to shut down as long as we leave camera app.

Accoding to the evidence of logcat, It seems to be adsp subsystem failure like the snapet showed below.

We have tried any possible combinations between QDSP6 lib and OEM plugin sides,

and also tried setting persist.camera.isp.dualisp to 1, but all of them did not work.

 

Is there anyone who had this issue before? or any advice we can do to avoid shutdown issue, which is really annoying.

Thank you.

------

Environment:

MSM8996

SDK: 3.2.

Android: 6.0.1

==

01-02 12:37:25.384     0     0 E         : Watchdog bite received from adsp!
01-02 12:37:25.387     0     0 E         : adsp subsystem failure reason: SFR Init: wdog or kernel error suspected..
01-02 12:37:25.395     0     0 I subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = SYSTEM.

 

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