Access Official Technical PDF

Share Summary:LinkedInEmail

SmartDesign FPGA design in Microsemi Libero SoC uses a visual canvas to assemble, configure, and connect the building blocks of an FPGA project. For engineers and integrators, this provides a way to view relationships among IP cores, HDL modules, reusable blocks, and other design components before generating the top-level HDL. The canvas is a design-entry tool—not a substitute for verifying the intended logic and connectivity—but it can make a complex component hierarchy easier to inspect and manage.

What SmartDesign contributes to an FPGA workflow

SmartDesign acts as a graphical environment for integrating Microsemi IP, user-generated or third-party IP, HDL files, basic macros, reusable design blocks, and other SmartDesign components. The resulting design may represent an entire FPGA design or a subsystem intended for use within a larger project.

Rather than treating each module as an isolated source file, the canvas presents components as instances with pins and nets between them. Designers can configure supported components, connect their interfaces, expose top-level ports, and review the structure of the design. SmartDesign then generates a synthesis-ready HDL representation when the design passes its design-rule checks.

SmartDesign FPGA design: from components to generated HDL

A practical workflow has four main stages. First, create a top-level SmartDesign component and instantiate the required building blocks. Components can be added from the project hierarchy or catalog, and some IP cores must be configured before they can be placed on the canvas. HDL files can be instantiated directly; HDL+ cores, which are generated from HDL with parameters or generics, can be configured within the design.

  1. Instantiate components. Add the required IP cores, HDL modules, macros, reusable design blocks, or lower-level SmartDesign components.
  2. Connect bus interfaces where applicable. Components with predefined bus interfaces can support interface-based connectivity. This stage is optional; connections can instead be made manually.
  3. Connect pins and ports. Make the required signal connections, handle unused inputs and outputs, and add or modify top-level ports.
  4. Check and generate. Run design-rule checking, address reported issues, and generate the top-level component and its HDL.

The generated component can be used by downstream processes such as synthesis and simulation, or instantiated within another SmartDesign. This makes the canvas useful for both top-level integration and construction of reusable subsystems.

Managing nets, buses, and component connections

SmartDesign provides several ways to create connections. QuickConnect presents design pins in a dialog to help connect selected items, while Connection Mode lets a user draw a connection from one pin to another. The canvas also supports selecting design objects and connecting them through context-menu actions. These methods help accommodate both direct signal wiring and bus-oriented integration.

When a connection is incomplete or difficult to trace, net highlighting can show the connected pins and ports, including connections through hierarchy. The Go to Driver action centers the view on a net’s driver at the current hierarchy level. It does not traverse into other levels, so designers may need to expand or open components to follow a signal through the full design.

Bus handling includes options to expand or collapse a bus, create slices, define custom slices, and change bit order. These controls can help when a design connects only part of a bus or when signal presentation needs to be clearer. Pin order can also be adjusted on an instance to improve the readability of the canvas, particularly when two components exchange multiple signals. These are presentation and connection-management features; they do not remove the need to confirm that the resulting signal mapping matches the design intent.

Use hierarchy to inspect and reuse design blocks

SmartDesign components can be expanded in place to reveal lower levels of hierarchy, or folded back to show a more compact top-level view. This supports navigation across designs that combine multiple modules and reusable blocks. An expanded in-place view is for inspection; changes to lower-level components must be made by opening the relevant component directly.

Other useful maintenance actions include configuring an instance, replacing a component or version, updating a component when its port list changes, and removing connections. Because changing a component can affect its pins and existing wiring, review any warnings and verify affected connections after an update or replacement.

Design-rule checks are part of generation

Design-rule checking (DRC) evaluates the design’s connectivity and reports issues such as undriven or floating ports. A DRC can be run independently to review the design without generating HDL. Generating the component also invokes DRC automatically. If errors prevent generation, they must be corrected before the design flow can proceed.

For a dependable review, treat DRC as a checkpoint rather than a complete validation of system behavior. The source guide describes DRC as a check of design connectivity; it does not establish that a passing report proves functional correctness. Engineers still need to verify that component configuration, interface connections, top-level ports, and signal assignments reflect the requirements of the design.

Practical implications for engineering teams

SmartDesign offers a structured way to integrate FPGA building blocks while retaining a visual view of their relationships. Its most useful workflow habits are straightforward:

  • Organize components and hierarchy so the canvas remains understandable.
  • Use interface connections where they are available, and verify manual connections carefully.
  • Trace unclear nets with highlighting and driver navigation.
  • Review component changes for altered or lost connections.
  • Run DRC and resolve errors before generating the top-level HDL.

For industrial automation teams developing FPGA-based hardware, the practical value is in clearer integration and a repeatable path from component assembly to generated HDL. SmartDesign brings configuration, connectivity, hierarchy navigation, and design-rule checking into one design-entry workflow. Careful review of the actual signal relationships remains essential before moving the generated component into downstream synthesis or simulation.

Access Official Technical PDF

About The Author