Libero 11 7 Release Notes
Libero 11 7 Release Notes
Libero 11 7 Release Notes
7 Release Notes
Libero System-on-Chip (SoC) is comprehensive and powerful FPGA design and development software
available from Microsemi, providing start-to-finish design flow guidance and support for novice and
experienced users alike. Libero SoC combines Microsemi SoC Products Group tools with such EDA
Contents
Whats New in Libero SoC v11.7
Silicon Features
Software Enhancements
Resolved Issues
Known Limitations, Issues and Workarounds
System Requirements
Synopsys and Mentor Graphics Tools
Download Libero SoC v11.7
AL2, AE1, AE41, and AL40 pins cannot be used with DDR_OUT. Registers cannot be
combined on the output and enable pins.
Tie-off will always be done if the FFDR block is not used, and compile or layout will fail if you try
to use these pins with these features.
Software Enhancements
Unless otherwise noted, Software Enhancements apply to all SmartFusion2, IGLOO2, and RTG4
Devices.
Chip Planner
Libero SoC v11.7 introduces a full overhaul of the Chip Planner floorplanning tool. Chip Planner now
provides a more responsive user interface, with a contemporary look and feel. Significant runtime
enhancements compared to earlier versions of the same tool provide a smoother user experience on
large, high-utilization designs. Navigate through your design with ease using the revamped design
hierarchy browser, with advanced search and filtering support. Chip Planner also introduces usability
enhancements, with easy access to design and resource properties, and a highly customizable display
interface for enhanced productivity. Cross-probing from SmartTime to Chip Planner is also supported in
Libero SoC v11.7
SmartDebug
SmartDebug in Libero SoC v11.7 introduces a redesigned Debug FPGA Array probe management User
Interface. A new netlist hierarchy browser helps you navigate through your design to manage Live
Probes, Active Probes, and Probe Insertion. Active Probes can be also organized using the new Probe
Grouping feature. New for v11.7 are Device Status Report, eNVM Page Status enhancements for
SmartFusion2 and IGLOO2 devices, and SERDES Debug enhancements for SmartFusion2, IGLOO2,
and RTG4 devices. Also included in this release are run time improvements.
Starting in v11.7, SmartDebug can be run in as a standalone tool for SmartFusion2, IGLOO2, and RTG4
devices. SmartDebug in standalone mode is launched outside of the Libero Design Flow. It is intended to
be used in debug environments lab setups, for example where the full Libero SoC tools suite may not
be installed. The SmartDebug standalone tool can be installed using the new Program and Debug Tools
installer, which also contains FlashPRO, FlashPRO Express, and Job Manager.
M2S010 (FG484) and M2S050 (FG896) Simultaneous Switching Noise (SSN) Analysis
New in Libero SoC v11.7 is the Simultaneous Switching Noise Analyzer tool. The SSN Analyzer helps
achieve the desired voltage noise margin for I/Os. It analyzes various parameters (for example,
switching frequency of neighboring I/Os, I/O drive strength, etc.) and estimates the noise margin
available for each I/O in a design.
More designs use multiple clock domains -- including phase-shifted outputs from CCCs -- and
inter-clock timing optimization is a necessary technique for closing timing.
2.
Across the industry, most CAD tools assume that clocks are synchronous to one another unless
otherwise specified.
3.
The "Clock group" constraint, which is introduced in Libero SoC v11.7, can be used to quickly
and easily specify asynchronous relationships between clocks. (The "False Path" constraints
can also be used.)
Users of the "Enhanced Constraint Flow" will need to pay careful attention to the timing constraints in the
"TDPR Scenario". The Layout tools will optimize all launch and latch clocks unless otherwise prohibited.
It is important to note that inter-clock paths often have stricter required times than their base clock
domains. This can render the inter-clock paths more timing-critical. The Layout tools will optimize every
path in the "TDPR Scenario" set of timing constraints. The most critical of these paths will receive the
2.
"False path" constraints can also be used, but they are less efficient than "Clock group"
constraints.
3.
After the first successful Layout, the SmartTime GUI can be opened, the "Inter-clock analysis"
option can be de-selected from within the GUI, the changes Saved, and the Layout re-run, and
both Inter-clock optimization and analysis will be disabled.
Slow MAX: high temperature, low voltage, slow process, max delay timing and violation
reports
Fast MAX: low temperature, high voltage, fast process, max delay timing and violation reports
Slow MIN: high temperature, low voltage, slow process, min delay timing and violation reports
Fast MIN: low temperature, high voltage, fast process, min delay timing and violation reports
Note that enabling multiple types of timing and violation reports may highlight latent issues in your
design, necessitating additional steps to achieve timing closure. You can filter the types of reports
generated using the Verify Timing options dialog.
Clock Groups: Libero SoC v11.7 introduces clock groups, an SDC command to specify related and
unrelated clocks. Typically, clocks from the same source (e.g. Oscillator, CCC) must be in the same
group. Design paths crossing between clocks in the same group are analyzed by SmartTime. Note that
the clock groups command is only valid for SDC files managed as part of the Enhanced Constraint Flow.
SgCore Enhancements
The following SgCores have been updated for Libero SoC v11.7:
Core
Device/Family
Libero SoC
v11.7compatible
version
Changes
Chip Oscillator
SmartFusion2/IGLOO2
2.0.101
SmartFusion2/IGLOO2
1.2.210
M2S/M2GL090T/TS
1.2.212
M2S/M2GL090T/TS
Clock Conditioning
Circuitry
RTG4
1.1.208
Two-Port RAM
RTG4
1.1.105
Microcontroller
Subsystem
SmartFusion
A2F200/500
2.5.200
RTG4
1.1.220
RTG4
RTG4
RTG4
Generic DDR
Memory Simulation
Model
SmartFusion2/IGLOO2/
RTG4
1.0.110
1.0.110
1.0.102
Runtime Improvements
Libero SoC v11.7 includes runtime improvements to Power report generation. In addition, the Project
Manager has been enhanced from a runtime perspective; Design Hierarchy construction is significantly
faster, and other menu interactions have also been sped up.
Resolved Issues
Issues Resolved in Libero v11.7
SAR53964: SERDES EPCS: Proper port width calculation
In earlier releases, SERDES EPCS ports of widths less than 20 needed to be manually tied off. Libero SoC
addresses this issue, always exposing the correct number of ports to the top level.
SAR69162: VERIFY_DIGEST always fails in master file/job when external digest check is restricted
This issue has been resolved in Libero SoC v11.7; the VERIFY_DIGEST action now succeeds in the case
where the external digested check is restricted.
493642-2016646691
493642-2010248422
493642-1893623058,4936421895523156
493642-1963000720
493642-1829929008
493642-1972801421
493642-1827819781
493642-1966630751
493642-1917238998
493642-1958954082
493642-1941178061
493642-1926640908
493642-1982329807
493642-1968324433, 4936421964389284
493642-1885746150
493642-1898026386, 4936421973446060
493642-1808806782 , 4936421821688701, 4936421772302804, 4936421818096627, 4936421865263914, 493642-2027106509
Description
RTG4: "The placer was unable to find a solution which satisfied
architectural placement of global nets."
Unable to change PMA settings directly from GUI
Add BER(bit-error rate) status to SERDES SmartDebug GUI
CCC PREADY signal shows high-z causing APB transaction to hang
RTG4 CCC generated RTL is not showing the correct width of INIT STRING
Missing Min-period timing arcs in the simulation model of UFROM and
UFROMH
Error occurred while generating Programming file after Layout completed
Design with Routing Region constraints after successful "Place and Route"
step fails in "Generate Biststream" with open nets.
Logic cone does not retain logic added to a net
Confusing Error message (SF2 programming failure)
SVF export with customize TCK - FlashPro only
SPPS: Allow user to overwrite security policy in Job Manager
To open Synplify in Linux, setenv LM_LICENSE_FILE should be
port@hostname
eNVM AHB access is cycle inaccurate
CORE AXI simulation fails after 200000(dec) read transactions with message
# MONAXI1: ERROR Non mat
eNVM hard-coded paths don't retain the relative path to the .hex files
Libero won't invalidate the bitstream even eNVM mem content updated
Libero 11.6 crashes with design. Duplicate modules get generated on
second run.
Libero 11.6 crashes when generating Smart Design Component from design
hierarchy
Libero 11.6 prints warning messages on terminal from HDL design but there
is no warning on Libero GUI
In Linux, Libero regenerates the IP RTL files even if the configuration is not
changed
Libero loses track of RTL updates when using HDL+ if Libero was closed
smarttime.exe/Libero.exe is in Processes Tab even after Libero 11.5 is
closed
493642-1722648844
493642-1404235599,4936421946519426
493642-2010248422
493642-1595471765
493642-1964879861
493642-1913483321
493642-1870660106
493642-1857320475
493642-1970291559, 4936421973073993
493642-1772077521
493642-1930722571
493642-1771657311
493642-1987117613
493642-1977246176
493642-1953826240
493642-1887808755
493642-1849382710
493642-1709713206, 4936421782280067
493642-1435744139
493642-1558734186
493642-1662897931,4936421692283632, 493642-1722796823
493642-1637762925
493642-1874702581
493642-2039633013
RTG4
Custom Flow with uPROM: uPROM content must be a single line file
If you are using custom flow and are importing uPROM content using the import_component_data
command, the uPROM memory file must not have any newlines.
Precision Synthesis
IO Advisor
Netlist Viewer
Block Flow
Design Separation Flow using MSVT
Secure IP (IEEE 1735) Flow
Explicit and potential clocks cannot be found for Enhanced Constraint Flow designs started from
EDIF
If you are using the Enhanced Constraint Flow, and you are not running Synthesis (i.e., you import an EDIF
netlist), the Constraints Editor is not able to find the names of explicit and potential clocks in your design.
Multiple-line False Path Constraints are not taken into account by Timing Verification
With false path constraints of the type
set_false_path -ignore_errors -through [ get_nets {
test_sb_0/CORERESETP_0/*sdif*_phr/hot_reset_n
test_sb_0/CORERESETP_0/*sdif*_phr/sdif_core_reset_n_0 } ]
the second false path may be ignored by the Place and Route and Timing Verification tools. To work around
the issue, split up the get_nets directive in separate false path constraints:
set_false_path -ignore_errors -through [ get_nets {
test_sb_0/CORERESETP_0/*sdif*_phr/hot_reset_n ]
set_false_path -ignore_errors -through [ get_nets {
test_sb_0/CORERESETP_0/*sdif*_phr/sdif_core_reset_n_0 } ]
Collect any timing constraints present in the SDC file generated by Synphony and translate these
constraints to the standard SDC format into a new SDC file.
Collect any netlist attributes present in the SDC file generated by Synphony and copy them into a
new FDC file.
Import the new SDC and FDC files into your Libero SoC project using the Manage Constraints User
Interface, and associate these files with the Synthesis step before running Synthesis.
If you have used Identify in Integrated mode on your machine, you may need to readjust the Identify Launch
option. Open the Configure Identify Launch dialog; in the Synplify Pro main window, click Options, then click
Configure Identify Launch. Ensure that the Legacy radio button is selected, then click OK to exit the dialog.
Synthesis
Libero does not directly support SystemVerilog in v11.7.
Workaround: Invoke SynplifyPro in standalone mode, import all HDL files, and run synthesis. The output of
SynplifyPro (*.edn or *.vm) can then be incorporated into the Libero project.
10
Programming
Generate Bitstream crashes in Libero flow for designs in chain mode
For Libero projects which involve a chain of SmartFusion2/IGLOO2/RTG4 and older Flash devices
(SmartFusion, IGLOO, ProASIC3, and Fusion) in which the older Flash device is added using PDB, the
following tools will not work in Libero:
Generate Bitstream
Export Bitstream
Export FlashPro Express Job
Workaround: Use STAPL instead of PDB when adding an older Flash device to a
SmartFusion2/IGLOO2/RTG4 chain.
Generate Bitstream fails when serialization memory file is copied to project directory
For SmartFusion2 and IGLOO2 devices, in the eNVM configurator, do not select the Copy Memory File to
Project Path option on a serialization clients memory file. If you do so, bitstream generation will fail in
Libero SoC v11.7.
Generate Bitstream fails with Contents filled with 0s option
For RTG4 devices, in the uPROM configurator, if the Contents filled with 0s option is selected, bitstream
generation will fail. As a workaround, use a .mem file, filled with 0s.
Job file (.job) created is missing the programming bitstream
When creating a new programming job for the IHP job type, the job file (.job) created is missing the
programming bitstream, This issue will be resolved in 11.7 SP1.
Documentation
Web-based documentation
Starting with Libero SoC v11.7, most Users Guides for SmartFusion2, IGLOO2, and RTG4 will be published
on the Microsemi website. Libero and Programming/Debug tools will include links to the website.
If the machine on which you have installed Libero does not have access to the Internet, you (or a site
administrator) can download all Libero SoC v11.7 Users Guides from Microsemis Libero SoC
documentation site.
System Requirements
Refer to System Requirements on the web for more information regarding operating systems support and
minimum system requirements. A 64-bit OS is required for designing SmartFusion2, IGLOO2 and RTG4
devices.
Setup Instructions for Linux OS can be found on the Libero SoC Documents web page.
OS Support
Supported
Windows 7, Windows 8.1
RHEL 5* and RHEL 6, CentOS 5* and CentOS 6
SuSE 11 SP4 (Libero only; FlashPro Express, SmartDebug, and Job Manager are not supported)
11
Installation Note:
After installation of Libero on Linux, any attempt to run the udev_install script for FlashPro setup will fail.
When running the script, users will see the following:
% ./udev_install
/bin/sh^M: bad interpreter: No such file or directory
Problem:
The script uses Windows CR/LF line termination instead of UNIX/Linux LF only line termination and, as
such, is not a valid shell script.
Workaround:
Users must run dos2unix on the script to convert CR/LF line termination to LF only line termination:
% dos2unix udev_install
% ./udev_install
If dos2unix is not available, users might need to run the following command, and then run dos2unix:
% sudo yum install dos2unix
12
Product Support
Microsemi SoC Products Group backs its products with various support services, including Customer Service, Customer
Technical Support Center, a website, electronic mail, and worldwide sales offices. This appendix contains information
about contacting Microsemi SoC Products Group and using these support services.
Customer Service
Contact Customer Service for non-technical product support, such as product pricing, product upgrades, update
information, order status, and authorization.
From North America, call 800.262.1060
From the rest of the world, call 650.318.4460
Fax, from anywhere in the world 650. 318.8044
Technical Support
For Microsemi SoC Products Support, visit http://www.microsemi.com/products/fpga-soc/design-support/fpga-soc-support.
Website
You can browse a variety of technical and non-technical information on the Microsemi SoC Products Group home page, at
http://www.microsemi.com/soc/.
Email
You can communicate your technical questions to our email address and receive answers back by email, fax, or phone.
Also, if you have design problems, you can email your design files to receive assistance. We constantly monitor the email
account throughout the day. When sending your request to us, please be sure to include your full name, company name,
and your contact information for efficient processing of your request.
The technical support email address is soc_tech@microsemi.com.
My Cases
Microsemi SoC Products Group customers may submit and track technical cases online by going to My Cases.
About Microsemi
Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductor and
system solutions for communications, defense & security, aerospace, and industrial markets.
Products include high-performance and radiation-hardened analog mixed-signal integrated circuits,
FPGAs, SoCs, and ASICs; power management products; timing and synchronization devices and
precise time solutions, setting the world's standard for time; voice processing devices; RF solutions;
discrete components; Enterprise Storage and Communication solutions, security technologies and
scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and midspans; as well
as custom design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif. and
has approximately 4,800 employees globally. Learn more at www.microsemi.com.
Microsemi Corporate Headquarters
One Enterprise, Aliso Viejo,
CA 92656 USA
Within the USA: +1 (800) 713-4113
Outside the USA: +1 (949) 380-6100
Sales: +1 (949) 380-6136
Fax: +1 (949) 215-4996
E-mail: sales.support@microsemi.com
Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or
the suitability of its products and services for any particular purpose, nor does Microsemi assume any
liability whatsoever arising out of the application or use of any product or circuit. The products sold
hereunder and any other products sold by Microsemi have been subject to limited testing and should not
be used in conjunction with mission-critical equipment or applications. Any performance specifications are
believed to be reliable but are not verified, and Buyer must conduct and complete all performance and
other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not
rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer's
responsibility to independently determine suitability of any products and to test and verify the same. The
information provided by Microsemi hereunder is provided "as is, where is" and with all faults, and the
entire risk associated with such information is entirely with the Buyer. Microsemi does not grant, explicitly
or implicitly, to any party any patent rights, licenses, or any other IP rights, whether with regard to such
information itself or anything described by such information. Information provided in this document is
proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this
document or to any products and services at any time without notice.
51300139-2/04.16