You're reading the documentation for a development version.
For the latest stable release version, please have a look at master.

Dismiss

Design errors

• Assignment overlap
  • Introduction
  • Example
• Clock crossing violation
  • Introduction
  • Example
    • crossClockDomain tag
    • setSyncronousWith
    • BufferCC
• Combinatorial loop
  • Introduction
  • Example
  • False-positives
• Hierarchy violation
  • Introduction
  • Example
• Io bundle
  • Introduction
  • Example
• Latch detected
  • Introduction
  • Example
• No driver on
  • Introduction
  • Example
• NullPointerException
  • Introduction
  • Example
    • Issue explanation
• Register defined as component input
  • Introduction
  • Example
• Scope violation
  • Introduction
  • Example
• Spinal can’t clone class
  • Introduction
  • Example 1
  • Example 2
• Unassigned register
  • Introduction
  • Example
  • Register with only init
• Unreachable is statement
  • Introduction
  • Example
• Width mismatch
  • Introduction
  • Assignment example
  • Operator example

Introduction

The SpinalHDL compiler will perform many checks on your design to be sure that the generated VHDL/Verilog will be safe for simulation and synthesis. Basically, it should not be possible to generate a broken VHDL/Verilog design. Below is a non-exhaustive list of SpinalHDL checks:

• Assignment overlapping

• Clock crossing

• Hierarchy violation

• Combinatorial loops

• Latches

• Undriven signals

• Width mismatch

• Unreachable switch statements

On each SpinalHDL error report, you will find a stack trace, which can be useful to accurately find out where the design error is. These design checks may look like overkill at first glance, but they becomes invaluable as soon as you start to move away from the traditional way of doing hardware description.