• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 2967 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Configure flexlm license from command line on client machine (MDK 5.39)

NoobCoder1337

Hello,

I want to automatically configure a flexLM license (<port>@<host_id>) via command line. (essential edition flexlm)

I edited the TOOLS.ini, but this doesn't work. I already tried to search AppData folder and registry, but couldnt find anything remotely relevant.

Especially weird: If I open uVision and open license managment, it tells me that the FlexLM-license is set up and I can borrow it, return it, etc. But when I want to compile I get: 

.\build\linker\some.sct: error: L6047U: The size of this image (34944 bytes) exceeds the maximum allowed for this version of the linker

Same thing if I call the compiler / linker from command line (tells me something "lite").

Please help!

Best regards

Parents
  • 0 in reply to Hans Schneebauer

    Hello Hans,

    your tipp pointed me in a good direction. Currently we use uVision in batchmode, because we have not set up our own buildsystem yet (cmake/ninja is planned) 

    The tools.ini has a separate item for uVision config. So, for anyone who might also want to create a portable package, you need to update the following items in tools.ini when deploying the package (for example using Python configparser library). Replace <> accordingly.

    • Section "UV2"
      • ORGANIZATION=<your company>
      • NAME="<LastName>", "<FirstName>"
      • EMAIL=<user mail>
      • ARMSEL=1
      • USERTE=1
      • TOOL_VARIANT=mdk_cm_std_flex (standard with FlexLM, change accordingly)
      • RTEPATH=<Path where your CMSIS packs are handled by CMSIS manager>
      • CPACKGETPATH=<package base path>\ARM\cmsis-toolbox\bin
      • FLEX=<port>@<license server host name>
      • FLEX_USE=1
      • FLEX_VARIANT=mdk_cm_std (change accordingly)
    • Section "ARM"
      • PATH=<package base path>\ARM
    • Section "ARMADS" <--- I forgot this one
      • PATH=<package base path>\ARM

    The rest should stay as the default. (my impression)

Reply
  • 0 in reply to Hans Schneebauer

    Hello Hans,

    your tipp pointed me in a good direction. Currently we use uVision in batchmode, because we have not set up our own buildsystem yet (cmake/ninja is planned) 

    The tools.ini has a separate item for uVision config. So, for anyone who might also want to create a portable package, you need to update the following items in tools.ini when deploying the package (for example using Python configparser library). Replace <> accordingly.

    • Section "UV2"
      • ORGANIZATION=<your company>
      • NAME="<LastName>", "<FirstName>"
      • EMAIL=<user mail>
      • ARMSEL=1
      • USERTE=1
      • TOOL_VARIANT=mdk_cm_std_flex (standard with FlexLM, change accordingly)
      • RTEPATH=<Path where your CMSIS packs are handled by CMSIS manager>
      • CPACKGETPATH=<package base path>\ARM\cmsis-toolbox\bin
      • FLEX=<port>@<license server host name>
      • FLEX_USE=1
      • FLEX_VARIANT=mdk_cm_std (change accordingly)
    • Section "ARM"
      • PATH=<package base path>\ARM
    • Section "ARMADS" <--- I forgot this one
      • PATH=<package base path>\ARM

    The rest should stay as the default. (my impression)

Children
No data