This article is a summary of my study. If there are copyright or knowledge errors or problems, please contact me directly. Please leave a message
PS: Based on the principle of knowledge sharing, this blog can be reproduced, but please indicate the source!
catalogue
1. Problem description
2. Cause analysis:
3. Problem solving:
1. Problem description
When I debug the project, in order to capture the signal value to observe the timing, I added ILA, and then encountered vivado error when generating bitstream. The warning is as follows:
The specific error contents are as follows:
[DRC LUTLP-1] Combinatorial Loop Alert: 2 LUT cells form a combinatorial loop.
This can create a race condition. Timing analysis may not be accurate. The preferred resolution is to modify the design to remove combinatorial logic loops. If the loop is known and understood, this DRC can be bypassed by acknowledging the condition and setting the following XDC constraint on any one of the nets in the loop: 'set_property ALLOW_COMBINATORIAL_LOOPS TRUE [get_nets <myHier/myNet>]'. One net in the loop is u_DdrRdData/NxtRdState[0]. Please evaluate your design. The cells in the loop are: u_DdrRdData/NxtRdState_inferred_i_3, and u_DdrRdData/NxtRdState_inferred_i_8.
2. Cause analysis:
As shown in the code segment below, the combinational loop is combinational logic, which feeds back to itself without registers. The simplest example is an inverter whose output is fed back to the input to produce an oscillator.
Therefore, the combined logic signal nxtrdstate for the state machine cannot be used for ILA grabbing!!!
At the same time, the error can be prompted in the warning message of vivado tool:
This warning is described in ug901 as follows:
3. Problem solving:
Do not use ILA to grab the signal value assigned in the combinatorial logic of the state machine!!!
Read More:
- [DRC nstd-1] problem solving of vivado error problem
- Python’s importerror: DLL load failed: the specified module was not found and the problem was solved
- Ntpdate reported an error when updating the clock, and the problem of no server suitable for synchronization found was solved
- Successfully solved the problem that visual studio code could not go to the definition, and there was no mouse prompt
- no target device found problem solved
- Configuration problem of pcl1.9.1 under Windows 10 vs2017 (solved)
- node.js Error: write epipe problem solved!
- The problem of error reporting in Ranger connection hive is solved
- Solved – problem cannot find module ‘webpack / bin / config yargs’
- Solve the problem that the connection between ADB and nocturnal God cannot be solved
- An error was reported when idea compiles Java: no symbol was found_ How to solve this problem
- Solved! The new version of statsmodels has the problem of importerror: cannot import name ‘factorial’
- pom.xml Depending on the error report, the problem of missing artifact XXX is solved
- emulator: ERROR: x86 emulation currently requires hardware acceleration! Abnormal problem solved
- The error problem of loading autoware maptool function package by utiny is solved
- There was a problem with the editor ‘vi’
- -1: error: fatal error: no input files problem solved
- R language-Error in file(out, “wt”): Unable to open the link problem solved
- Virtualbox failed to attach usb, VERR_PDM_NO_USB_PORTS problem solved
- Failed to open \EFI\BOOT\mmx64.efi problem solved