Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
12 years ago

OpenCL License Issues

It would seem I may be having issues with my OpenCL License.

All of the features in the license file show up as valid in Quartus EXCEPT openCL, but

lmutil reports the OpenCL license as valid on the current machine "TS_OK".

However when I run "aoc myKernel.cl" I get the error:

"Could not acquire OpenCL SDK license"

Any suggestions?

Should the OpenCL Feature get reported in the Quartus "License Setup" Dialog?

7 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Have you set the LM_LICENSE_FILE environment variable as directed in the documentation?

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Yes, it is set to the correct license file.

    Quartus is set to use the variable and sees all of the other features.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    64 Bit RHEL 5.8, node locked (though I did try and get lmgrd to pick up the license to see if that helped, it did not).

    Does the OpenCL feature show up in your quartus license dialog?
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Do you have multiple ethernet interfaces? Which interface is the license bound to? Quartus has no knowledge of OpenCL or its licensing system. The only way OpenCL licenses are set up is using the FlexLM system and making sure the LM_LICENSE_FILE variable is set. This should be described in the documentation:

    http://www.altera.com/literature/lit-opencl-sdk.jsp
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    I have multiple interfaces. It is bound to the second eth1 (second ethernet port).

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    You have to use the primary Ethernet interface (eth0) on Linux due to how the licensing system works. This is a known issue and hopefully there will be a solution at some point.