Forums - DSP monitoring in Snapdragon 835

6 posts / 0 new
or Register
Last post
DSP monitoring in Snapdragon 835
annemaelle.b
Join Date: 12 Mar 18
Posts: 6
Posted: Mon, 2018-04-23 00:51
Top

Hi,

I would like to monitor DSP utilization on my phone (Xiaomi Mi 6) which has an Adreno 540 GPU.

However, when I connect it to the Snapdragon Profiler and start a new Trace capture, I only see Trace and not DSP. Is there a setting I forgot to set?

Thank you,

  • Up0
  • Down0
Re: DSP monitoring in Snapdragon 835
Carlos Dominguez Moderator
Join Date: 27 Jul 15
Location: San Diego
Posts: 110
Posted: Mon, 2018-04-23 11:41
Top

Hi,

We will try to reproduce your issue internally. To help us narrow it down faster, can you please provide us with logcat information? 

Thanks,

Carlos

  • Up0
  • Down0
Re: DSP monitoring in Snapdragon 835
annemaelle.b
Join Date: 12 Mar 18
Posts: 6
Posted: Mon, 2018-04-23 20:09
Top

I am not sure I understand what you are asking for. I don't have a specific error, it is just that I don't have access to DSP monitoring.

In my terminal I have this :

I: Scanning for devices...
I: Started QNX device scan
I: Device added: b1e7c8e2 127.0.0.1
I: Device 'b1e7c8e2' discovered.
I: Device 'b1e7c8e2' ready.
I: Starting service: adb -s b1e7c8e2 shell LD_LIBRARY_PATH=/data/local/tmp/SnapdragonProfiler /data/local/tmp/SnapdragonProfiler/sdpservice -clientIP 127.0.0.1 -cmdNetPort 6500
I: Server socket 0x00000002 listening on tcp://0.0.0.0:6500
I: Listening for command net connections on port 6500...
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Device 'b1e7c8e2' connected.
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: DataProvider replicated (0x4C1A3F91): SDPTrace Plugin
I: Client connecting to file transfer network at 127.0.0.1:6502
I: DataProvider replicated (0x0C792CE5): OpenCLDataProvider
I: Client connecting to file transfer network at 127.0.0.1:6504
I: DataProvider replicated (0x164DD690): ThermalDataprovider
I: Client connecting to file transfer network at 127.0.0.1:6506
I: DataProvider replicated (0x530B60FE): PowerDataPlugin
I: Client connecting to file transfer network at 127.0.0.1:6508
I: DataProvider replicated (0xAC149610): NetworkDataProvider
I: Client connecting to file transfer network at 127.0.0.1:6510
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500
I: DataProvider replicated (0x97E53411): CPUDataProvider
I: Client connecting to file transfer network at 127.0.0.1:6512
I: Server socket 0x00000002 accepted connection on tcp://0.0.0.0:6500

(SnapdragonProfiler:9359): Gtk-CRITICAL **: gtk_box_pack: assertion 'child->parent == NULL' failed
I: DataProvider reIn plicated (0xFB53BFE2): GGPMDataProvider
I: Client connecting to file transfer network at 127.0.0.1:6514
I: DataProvider replicated (0xEE72972E): VulkanDataPlugin
I: Client connecting to file transfer network at 127.0.0.1:6516
I: DataProvider replicated (0xBD2D700E): OpenGLESDataPlugin
I: Client connecting to file transfer network at 127.0.0.1:6518

I don't know what you would like to see from the phone logcat

  • Up0
  • Down0
Re: DSP monitoring in Snapdragon 835
Carlos Dominguez Moderator
Join Date: 27 Jul 15
Location: San Diego
Posts: 110
Posted: Wed, 2018-04-25 14:16
Top

We were not able to reproduce the issue in a Xiaomi Mi 6 running on Android 8.0. We do see DSP metrics.

Logcat would help us understand if the DSP data providing mechanisms hook up correctly or if something it's preventing it to do so. If you are concerned about propiertary logs that may be outputed there you can run logcat as shown below:

adb loccat -s SDPCore

This will filter out everything except Snapdragon Profiler logging and would give us some of the information we need to diagnose your issue.

  • Up0
  • Down0
Re: DSP monitoring in Snapdragon 835
annemaelle.b
Join Date: 12 Mar 18
Posts: 6
Posted: Wed, 2018-04-25 18:27
Top

Hi,

Here is my logcat obtained with the command adb logcat -s SDPCore :

04-26 09:19:09.461 31097 31097 I SDPCore : GLES_DP: GfxConnection: Starting connection thread
04-26 09:19:09.462 31097 31097 I SDPCore : Provider 'OpenGLESDataPlugin' (0xBD2D700E) connecting to 127.0.0.1:6500 (non-blocking)...
04-26 09:19:09.463 31097 31243 I SDPCore : GLES_DP: GfxConnection: Successfully connected to port 20817
04-26 09:19:09.470 31097 31246 I SDPCore : Client socket 0xBD2D700E connected to tcp://127.0.0.1:6500
04-26 09:19:09.471 31097 31248 I SDPCore : GLES_DP: Sending QSTREAM Token 0x1020002
04-26 09:19:09.553 31097 31097 I SDPCore : Provider 'OpenGLESDataPlugin' (0xBD2D700E) connected to 127.0.0.1.
04-26 09:19:09.706 31097 31248 I SDPCore : GLES_DP: GfxConnection: state is ready. app: com.android.browser
04-26 09:19:09.706 31097 31248 I SDPCore : GLES_DP: Moving ESXConnectionState from state 1 to state 2
04-26 09:19:09.971 31097 31243 I SDPCore : GLES_DP: GfxConnection: Successfully connected to port 20817
04-26 09:19:09.972 31097 31258 I SDPCore : GLES_DP: Sending QSTREAM Token 0x1020002
04-26 09:19:10.059 31097 31258 I SDPCore : GLES_DP: GfxConnection: state is ready. app: /data/local/tmp/SnapdragonProfiler/pluginGPU-GGPM
04-26 09:19:10.059 31097 31258 I SDPCore : GLES_DP: Moving ESXConnectionState from state 1 to state 2
04-26 09:19:10.477 31097 31243 I SDPCore : GLES_DP: GfxConnection: Successfully connected to port 20817
04-26 09:19:10.478 31097 31259 I SDPCore : GLES_DP: Sending QSTREAM Token 0x1020002
04-26 09:19:10.634 31097 31259 I SDPCore : GLES_DP: GfxConnection: state is ready. app: /data/local/tmp/SnapdragonProfiler/pluginGPU-QGL
04-26 09:19:10.635 31097 31259 I SDPCore : GLES_DP: Moving ESXConnectionState from state 1 to state 2
04-26 09:19:10.981 31097 31243 I SDPCore : GLES_DP: GfxConnection: Successfully connected to port 20817
04-26 09:19:10.982 31097 31260 I SDPCore : GLES_DP: Sending QSTREAM Token 0x1020002
04-26 09:19:11.135 31097 31260 I SDPCore : GLES_DP: GfxConnection: state is ready. app: /data/local/tmp/SnapdragonProfiler/pluginGPU-OpenGLES
04-26 09:19:11.135 31097 31260 I SDPCore : GLES_DP: Moving ESXConnectionState from state 1 to state 2
04-26 09:19:11.516 31097 31097 I SDPCore : GLES_DP: Sending QSTREAM Token 0x4020044
04-26 09:19:11.516 31097 31097 I SDPCore : GLES_DP: Sending QSTREAM Token 0x4020044
04-26 09:19:11.516 31097 31097 I SDPCore : GLES_DP: Sending QSTREAM Token 0x4020044
04-26 09:19:11.517 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [com.android.browser] Pid [14019] ready to profile
04-26 09:19:11.623 31097 31097 I SDPCore : GLES_DP: Sending QSTREAM Token 0x4020044
04-26 09:19:11.623 31097 31097 I SDPCore : GLES_DP: Sending QSTREAM Token 0x4020044
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: Sending QSTREAM Token 0x4020044
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [com.android.browser] Pid [14019] ready to profile
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [/data/local/tmp/SnapdragonProfiler/pluginGPU-GGPM] Pid [31101] ready to profile
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [/data/local/tmp/SnapdragonProfiler/pluginGPU-GGPM] Pid [31101] ready to profile
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [/data/local/tmp/SnapdragonProfiler/pluginGPU-QGL] Pid [31105] ready to profile
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [/data/local/tmp/SnapdragonProfiler/pluginGPU-QGL] Pid [31105] ready to profile
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [/data/local/tmp/SnapdragonProfiler/pluginGPU-OpenGLES] Pid [31097] ready to profile
04-26 09:19:11.624 31097 31097 I SDPCore : GLES_DP: GfxConnection: App [/data/local/tmp/SnapdragonProfiler/pluginGPU-OpenGLES] Pid [31097] ready to profile
04-26 09:19:59.609 31101 31101 I SDPCore : Provider 'GGPMDataProvider' listening for files @ tcp://*:6514
04-26 09:19:59.610 31101 31101 I SDPCore : Provider 'GGPMDataProvider' listening for options @ tcp://*:6515
04-26 09:19:59.757 31105 31105 I SDPCore : Provider 'VulkanDataPlugin' listening for files @ tcp://*:6516
04-26 09:19:59.758 31105 31105 I SDPCore : Provider 'VulkanDataPlugin' listening for options @ tcp://*:6517
04-26 09:20:01.047 31097 31097 I SDPCore : Provider 'OpenGLESDataPlugin' listening for files @ tcp://*:6518
04-26 09:20:01.047 31097 31097 I SDPCore : Provider 'OpenGLESDataPlugin' listening for options @ tcp://*:6519
 

  • Up0
  • Down0
Re: DSP monitoring in Snapdragon 835
annemaelle.b
Join Date: 12 Mar 18
Posts: 6
Posted: Wed, 2018-04-25 19:00
Top

I realized that I was on Android 7, after updating the phone I am now able to find DSP measurements. Thank you very much for your help

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