-
The
But still haven't gotten it to work due to some misaligned ')' characters. Any ideas on what else I need to do to have the license launching at startup? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Not sure if the is the right forum to troubleshoot Libero issues here |
Beta Was this translation helpful? Give feedback.
-
Part of the problem is that the formatting of the script in the documentation is a mess (in particular, missing line breaks causing lines to be incorrectly concatenated, missing indentation etc.) so that if you copy and paste it from the document it will almost certainly not work without reformatting, and maybe other changes. For example: Just to be clear, I'm referring to the document titled "How to Set Up Your Linux Environment for Libero SoC v12.0" accessible using this URL: from this page: Also here: The various references to different Libero versions (v12.0, v2021.2, v2022.2) are another unnecessary cause for confusion, but, presumably, the information in this document is supposed to also apply to the latest Libero SoC release. If you're running Libero SoC and the license daemon co-located on the same host then it might be simpler to take the sort of approach outlined in this link: In this case a simple script is used to run the license daemon "on demand" before running Libero, thus obviating the need for running the former as a "service" daemon. And the license daemon is terminated when you're finished with Libero. That also means that the license daemon isn't hogging resources when not needed. However it may mean that Libero SoC startup is slightly slower because the license daemon has to be started first. However this approach is no use if you need to configure the license daemon on a shared server accessed remotely by other hosts. |
Beta Was this translation helpful? Give feedback.
Not sure if the is the right forum to troubleshoot Libero issues here