Forums - Adreno Profiler Support for IFC6540

5 posts / 0 new
Last post
Adreno Profiler Support for IFC6540
kannanaj
Join Date: 25 Sep 14
Location: Toronto
Posts: 3
Posted: Thu, 2014-10-30 15:56

Hi, 

Our university recently purchased the IFC6540 (Snapdragon 805) SBC with the aim of measuring power and performance characterstics of OpenCL applications but we seem to having some trouble with this. It seems that the Trepn profiler does not support reading the power rails of the Snapdragon 805 on this board. Meanwhile, the adreno profiler doesn't seem to start on the device. It installs just fine and shows up under Settings->Apps but it does not show in the app drawer. The profiler itself says that it does not detect a supported device. 

Is there any way to rectify this issue? Or are the required binaries for the Snapdragon 805 available for end-users? 

Thanks and regards, 
Ajay

  • Up0
  • Down0
Dave Astle
Profile picture
Join Date: 19 Oct 12
Location: San Diego, CA
Posts: 101
Posted: Fri, 2014-10-31 09:29

Hi Ajay,

Although we haven't really spent any time testing on the Dragonboard, we work with Snapdragon 805 extensively, so Profiler should work with it. The situation you describe is strange. If Profiler is installing its apk, then it can definitely see the device, so the problem is likely that it can't detect the application.

To check the obvious, I assume you've confirmed that OpenCL is enabled on the device? (i.e. the application that you're trying to profile executes)

OpenCL profiling requires root access. I'm assuming that's the default state with the Dragonboard, but if not, you'll need to root it to profile.

If you're not able to get OpenCL applications to show up when you run them, can you check to see if you can profile OpenGL ES applications?

Posting your logcat logs can help us determine where it's failing.

  • Up0
  • Down0
kannanaj
Join Date: 25 Sep 14
Location: Toronto
Posts: 3
Posted: Fri, 2014-10-31 13:15

Hi Dave, 

Thanks for the reply. 

I have tested the OpenCL samples from the Adreno SDK and they pass all the tests for OpenCL and I do see the libOpenCL.so in the system folder (which I had to pull to compile the demo applications). I have root access but I'm not sure if applications have root access. On adb, I can su in the shell but can't do so, for example, in a terminal emulator. Could that be the problem? If so, how would I go about in getting application root access? 

I'm not sure if a logcat would help or at which point I would take a logcat as I see no crashes on the device side. Should I remove the application and take a logcat when Adreno Profiler tries to install it? On the PC side, all I see is that it can't see the profiler and in the terminal, I can see the application using adb to send the apk over and installing it. I took a logcat while installing the apk (manually) and then trying to connect to it using the PC side application.
https://dl.dropboxusercontent.com/u/83674441/logcat_log1.txt

 

Thanks, 
Ajay

  • Up0
  • Down0
kannanaj
Join Date: 25 Sep 14
Location: Toronto
Posts: 3
Posted: Fri, 2014-10-31 13:18

Hey Dave, 

I just tried something different this time. I hadn't tried opening the application I was trying to profile and then trying to connect. When I do that, the PC application detects the device. My fault comletely for not reading the manual. 

Sorry! Thanks again for your help! 

Cheers, 
Ajay

  • Up0
  • Down0
Dave Astle
Profile picture
Join Date: 19 Oct 12
Location: San Diego, CA
Posts: 101
Posted: Fri, 2014-10-31 13:33

I was wondering if that was the issue. It's not completely obvious that when you connect, you're connecting to the application you're trying to profile, so if no CL or GL enabled application is running, you won't see anything.

We'll be changing that in the future, but I'm glad you've been able to get it to work.

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