Forums - failed with using opencl ml extension sdk

4 posts / 0 new
or Register
Last post
failed with using opencl ml extension sdk
chennan
Join Date: 30 Aug 20
Posts: 2
Posted: Sun, 2020-08-30 20:30
Top

Hi, I want to use opencl ml extension sdk to test mobilenet performance on snapdragon 865(adreno 650).

But I met some errors with interface 'clQueryMLInterfaceVersionsQCOM'.

Error Code is -30 (CL_INVALID_VALUE).

 

enviroment:

0) test case: clml/examples/mobilenet

    I also tested two versions: 2019-12version, 2020-06version. both failed.

1)platform: 865 (8250)

2)ndk version: 20

3)python version: 3.5

4)compile commands: python3.5 build_sample.py android ~/android-ndk-r20/ libOpenCL.so -c Debug -p 32

 

And I checked the libOpenCL.so. It did have 'clQueryMLInterfaceVersionsQCOM' interface in the library. (use dlsym to load interfaces, dlsym no errors). Sorry, I don't know how to upload images.

 

I aslo checked the called interfaces return value. The interfaces as followed returned CL_SUCCESS:

 

clGetPlatformIDs, clGetDeviceIDs, clCreateContext, clCreateCommandQueue.
 
But when the program reached line 298, 'clQueryMLInterfaceVersionsQCOM, assert(ret == CL_SUCCESS);' failed.
ret = -30 (CL_INVALID_VALUE)

 

  • Up0
  • Down0
Re: failed with using opencl ml extension sdk
chennan
Join Date: 30 Aug 20
Posts: 2
Posted: Mon, 2020-09-07 23:16
Top

anyone can help

  • Up0
  • Down0
Re: failed with using opencl ml extension sdk
dqliu
Join Date: 27 Mar 18
Posts: 1
Posted: Wed, 2021-10-06 00:27
Top

I got another error,  calling of clQueryMLInterfaceVersionsQCOM return -6(CL_OUT_OF_HOST_MEMORY)

  • Up0
  • Down0
Re: failed with using opencl ml extension sdk
DuBo
Join Date: 9 Dec 13
Posts: 72
Posted: Fri, 2022-02-11 07:38
Top

865 platform commerial device is too old, which need special GFX adreno sba libs from Qualcomm to support clml extension.
Recommend you to use most recent 888 platform or newer 8Gen1 commerial device to test.

Thanks
Bob Du

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