Installing Libero IDE 9.1 under Ubuntu 12.04 x64

TLDR: fearing an uphill battle, I gave up and went with the Windows version

Install user guide: http://www.microsemi.com/document-portal/doc_download/131602-libero-ide-and-software-installation-and-licensing-guide

How to setup your Linux environment for Libero: http://www.microsemi.com/document-portal/doc_details/132361-how-to-set-up-your-linux-environment-for-libero

It likes to install here: /usr/local/actel/Libero_v9.1

I would have preferred an install under /opt

If you get this error:

localhost:/usr/local/actel/Libero_v9.1/Libero/bin$ ./libero
Error: Could not locate the X libraries in LD_LIBRARY_PATH

Included libraries don't help:

localhost:/usr/local/actel/Libero_v9.1/Libero/bin$ LD_LIBRARY_PATH=../lib ./libero
Error: Could not locate the X libraries in LD_LIBRARY_PATH

UG says:

Note that currently, Libero Linux tools expect to see the libXm.so.3 package of the Motif Library. Different
versions of OPEN Motif could potentially install libXm.so.4 or others that are not compatible with Libero.
Please ensure that the version of OPEN Motif used installs libXm.so.3. One example version which
provides libXm.so.3 is openmotif v2.2.3.
===== Headline =====
Furthermore, since Libero is a 32-bit application, the 32-bit Motif Library must be used even if the
computer is running a 64-bit Operating System

“Starting in 2014 Libero SoC will be supported only on 64-bit OS.” Which is odd since Libero IDE doesn't support 32 bit

Tried to checkout openmotif but couldn't get it to build

Why are they even using Motif anyway? Xilinx for example only uses Motif for a few dying apps like fpga_editor, seems like Actel is starting off on the wrong Linux foot. The Mentor tools use Qt though

Installing Libero IDE 9.1 under Windows

Gold (free) license is node locked and requires annoying things like disk ID. It even says that it won't allow you to use it remote desktopped. If its free why does it need that much protection?

Licensing

I had to manually add environment variable: LM_LICENSE_FILE: c:\flexlm\license.dat

Install user guide also says: “The following environment variables are optionaland take precedent over LM_LICENSE_FILE:

  • SNPSLMD_LICENSE_FILE is for Synopsys tools released in September 2010 and later (2010.09).
  • SYNPLCTYD_LICENSE_FILE is used by earlier releases of Synplify Pro ME and Identify ME.”

Past experience

I used tools briefly on Windows around 2012. The workflow was certainly not as smooth as the Xilinx tools as I had to switch between three windows (Mentor Graphics synthesis, project flow, and programming). I didn't have much HDL experience at the time so didn't have much to say on actual tool quality

05/11/2014: using tools again after getting some FPGA experience. Notes:

  • Using Libero 9.1, newer software exists. Take this with a grain of salt
  • Seems to do a better idea than Xiilnx at automatically using dedicated clock routing
  • I mostly work with antifuse FPGAs which have a sort of clunky workflow. I also used the SmartFusion which all around seemed more polished

MultiView Navigatior (MVN): I/O Attribute Editor

Edits are made to the .adb file

My experience with this tool varied drastically from using an SX-A to a SmartFusion. In particular, for the SX-A you can only supply constraints in .pin format. However, we require a pin to be held low during the power up phase. This can be specified using the I/O attribute editor BUT every time you re-synthesize the design, the .pin file gets re-imported and *every* pin constraint (locations, power up state) gets wiped out. Maybe you can selectively re-import .edn but not .pin? Probably should talk to an FAE.

For the SmartFusion using instead .pdc constraints, the Locked column can be one of the following:

  • Checked w/ white background: supplied by MVN, not specified in .pdc. Can be changed
  • Checked w/ gray background: supplied by PDC. Cannot be changed
  • Unchecked

Thus for the SmartFusion workflow for each pin you can specify in one of two ways:

  • Specify in MVN
  • Specify in .pdc. Note the MSS will supply at least some .pdc constraints

Unlike the SX-A workflow, MVN edits seem to be correctly preserved/merged across a re-import.

 
actel/libero.txt · Last modified: 2014/05/13 17:25 by mcmaster-guest
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki