• Locked Locked
  • Replies 3 replies
  • Subscribers 121 subscribers
  • Views 4190 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem Updating from ARM C/C++ Compiler RVCT4.0 [Build 436] to RVCT4.0 [Build 821]

Jaime F
Offline
Note: This was originally posted on 7th September 2010 at http://forums.arm.com

I'm trying to update the arm compiler to a new Build version. I followed the installation instructions (overwrite the executable's folder) but now it gives me a license error. I've checked my license.dat is for RVCT4.0, and if I downgrade to Build 436 it works perfectly. I have a floating license.
Does anyone had this problem when updating? Or maybe do I need a new license for different builds in the same release?
Here's the output:

======================================
C:\>armcc
ARM C/C++ Compiler, RVCT4.0 [Build 821]
Error: C9932E: Cannot obtain license for Compiler (feature compiler) with license version >= 4.0
License server system does not support this feature.
Feature:       compiler
License path:  C:\Archivos de programa\ARM\Licenses\license.dat;27000@10.64.206.16;
FLEXnet Licensing error:-18,147
For further information, refer to the FLEXnet Licensing documentation, available at "www.acresso.com".
Cannot obtain license for Compiler (feature bsp_compiler) with license version >= 4.0
License server system does not support this feature.
Feature:       bsp_compiler
License path:  C:\Archivos de programa\ARM\Licenses\license.dat;27000@10.64.206.16;
FLEXnet Licensing error:-18,147
For further information, refer to the FLEXnet Licensing documentation, available at "www.acresso.com".

===============================

Thanks in advanced

Jaime
Parents
  • Offline
    Note: This was originally posted on 7th September 2010 at http://forums.arm.com

    Try doing a test compile with this additional argument to the compiler "--licensing=flex", that could get rid of the bit out the bsp_compiler.  There is a FAQ some where which describes what the bsp_????? bit means, and what the flag does.

    After that, take a look at the license server's log file.  This usually gives a clearer view of why you weren't able to check the license out.
Reply
  • Offline
    Note: This was originally posted on 7th September 2010 at http://forums.arm.com

    Try doing a test compile with this additional argument to the compiler "--licensing=flex", that could get rid of the bit out the bsp_compiler.  There is a FAQ some where which describes what the bsp_????? bit means, and what the flag does.

    After that, take a look at the license server's log file.  This usually gives a clearer view of why you weren't able to check the license out.
Children
No data