This repository has been archived on 2026-08-21. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
ciciec2026/fpga/vivado_reports_nodsp/methodology.rpt
2026-07-08 03:48:37 +08:00

543 lines
22 KiB
Plaintext

Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.
------------------------------------------------------------------------------------------------
| Tool Version : Vivado v.2019.2 (lin64) Build 2708876 Wed Nov 6 21:39:14 MST 2019
| Date : Wed Jul 8 03:34:05 2026
| Host : fedora running 64-bit unknown
| Command : report_methodology -file /home/fallensigh/vivado_reports_nodsp/methodology.rpt
| Design : soc_top
| Device : xc7a200tfbg676-1
| Speed File : -1
| Design State : Fully Routed
------------------------------------------------------------------------------------------------
Report Methodology
Table of Contents
-----------------
1. REPORT SUMMARY
2. REPORT DETAILS
1. REPORT SUMMARY
-----------------
Netlist: netlist
Floorplan: impl_1
Design limits: <entire design considered>
Max violations: <unlimited>
Violations found: 99
+-----------+----------+-------------------------------------------------------------------+------------+
| Rule | Severity | Description | Violations |
+-----------+----------+-------------------------------------------------------------------+------------+
| LUTAR-1 | Warning | LUT drives async reset alert | 1 |
| SYNTH-5 | Warning | Mapped onto distributed RAM because of timing constraints | 8 |
| SYNTH-6 | Warning | Timing of a block RAM might be sub-optimal | 1 |
| SYNTH-16 | Warning | Address collision | 8 |
| TIMING-10 | Warning | Missing property on synchronizer | 1 |
| TIMING-18 | Warning | Missing input or output delay | 76 |
| TIMING-47 | Warning | False path or asynchronous clock group between synchronous clocks | 2 |
| XDCC-1 | Warning | Scoped Clock constraint overwritten with the same name | 1 |
| XDCC-7 | Warning | Scoped Clock constraint overwritten on the same source | 1 |
+-----------+----------+-------------------------------------------------------------------+------------+
2. REPORT DETAILS
-----------------
LUTAR-1#1 Warning
LUT drives async reset alert
LUT cell u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_ek_bram/p_s1[23]_i_9, with 2 or more inputs, drives asynchronous preset/clear pin(s) u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_busy_reg/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_i_reg[0]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_i_reg[1]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_i_reg[2]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_j_reg[0]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_j_reg[1]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_j_reg[2]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_pair_reg[0]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_pair_reg[1]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_pair_reg[2]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_pair_reg[3]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_pair_reg[4]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_widx_reg[0]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_widx_reg[1]/CLR, u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/a_widx_reg[2]/CLR (the first 15 of 24584 listed). The LUT may glitch and trigger an unexpected reset, even if it is a properly timed path.
Related violations: <none>
SYNTH-5#1 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r1_0_127_0_0 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#2 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r1_0_127_1_1 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#3 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r1_128_255_0_0 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#4 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r1_128_255_1_1 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#5 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r2_0_127_0_0 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#6 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r2_0_127_1_1 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#7 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r2_128_255_0_0 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-5#8 Warning
Mapped onto distributed RAM because of timing constraints
The instance u_cpu/dcache/way_d_reg_reg_r2_128_255_1_1 is implemented as distributed LUT RAM for the following reason: The timing constraints suggest that the chosen mapping will yield a better timing.
Related violations: <none>
SYNTH-6#1 Warning
Timing of a block RAM might be sub-optimal
The timing for the instance u_snix_axil_cdma_mux_8ch/u_core_engine/axis_fifo_u0/u_fifo/mem_reg, implemented as a block RAM, might be sub-optimal as no output register was merged into the block
Related violations: <none>
SYNTH-16#1 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_bank_a/mem_reg_0 may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#2 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_bank_a/mem_reg_1 may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#3 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_bank_se/mem_reg may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#4 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_bank_t/mem_reg may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#5 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_c_in_bram/mem_reg may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#6 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_ct_bram/mem_reg may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#7 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_dkp_bram/mem_reg may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
SYNTH-16#8 Warning
Address collision
Block RAM u_fft_mlkem_axi_slave/u_mlkem_axi_slave/u_mlkem/u_ek_bram/mem_reg may get memory collision error if read and write address collide. Use of address collision resolution circuitry is recommended.
Related violations: <none>
TIMING-10#1 Warning
Missing property on synchronizer
One or more logic synchronizer has been detected between 2 clock domains but the synchronizer does not have the property ASYNC_REG defined on one or both registers. It is recommended to run report_cdc for a complete and detailed CDC coverage
Related violations: <none>
TIMING-18#1 Warning
Missing input or output delay
An input delay is missing on UART_RX relative to clock(s) clk
Related violations: <none>
TIMING-18#2 Warning
Missing input or output delay
An input delay is missing on UART_TX relative to clock(s) clk
Related violations: <none>
TIMING-18#3 Warning
Missing input or output delay
An input delay is missing on dip_sw[0] relative to clock(s) clk
Related violations: <none>
TIMING-18#4 Warning
Missing input or output delay
An input delay is missing on dip_sw[10] relative to clock(s) clk
Related violations: <none>
TIMING-18#5 Warning
Missing input or output delay
An input delay is missing on dip_sw[11] relative to clock(s) clk
Related violations: <none>
TIMING-18#6 Warning
Missing input or output delay
An input delay is missing on dip_sw[12] relative to clock(s) clk
Related violations: <none>
TIMING-18#7 Warning
Missing input or output delay
An input delay is missing on dip_sw[13] relative to clock(s) clk
Related violations: <none>
TIMING-18#8 Warning
Missing input or output delay
An input delay is missing on dip_sw[14] relative to clock(s) clk
Related violations: <none>
TIMING-18#9 Warning
Missing input or output delay
An input delay is missing on dip_sw[15] relative to clock(s) clk
Related violations: <none>
TIMING-18#10 Warning
Missing input or output delay
An input delay is missing on dip_sw[16] relative to clock(s) clk
Related violations: <none>
TIMING-18#11 Warning
Missing input or output delay
An input delay is missing on dip_sw[17] relative to clock(s) clk
Related violations: <none>
TIMING-18#12 Warning
Missing input or output delay
An input delay is missing on dip_sw[18] relative to clock(s) clk
Related violations: <none>
TIMING-18#13 Warning
Missing input or output delay
An input delay is missing on dip_sw[19] relative to clock(s) clk
Related violations: <none>
TIMING-18#14 Warning
Missing input or output delay
An input delay is missing on dip_sw[1] relative to clock(s) clk
Related violations: <none>
TIMING-18#15 Warning
Missing input or output delay
An input delay is missing on dip_sw[20] relative to clock(s) clk
Related violations: <none>
TIMING-18#16 Warning
Missing input or output delay
An input delay is missing on dip_sw[21] relative to clock(s) clk
Related violations: <none>
TIMING-18#17 Warning
Missing input or output delay
An input delay is missing on dip_sw[22] relative to clock(s) clk
Related violations: <none>
TIMING-18#18 Warning
Missing input or output delay
An input delay is missing on dip_sw[23] relative to clock(s) clk
Related violations: <none>
TIMING-18#19 Warning
Missing input or output delay
An input delay is missing on dip_sw[24] relative to clock(s) clk
Related violations: <none>
TIMING-18#20 Warning
Missing input or output delay
An input delay is missing on dip_sw[25] relative to clock(s) clk
Related violations: <none>
TIMING-18#21 Warning
Missing input or output delay
An input delay is missing on dip_sw[26] relative to clock(s) clk
Related violations: <none>
TIMING-18#22 Warning
Missing input or output delay
An input delay is missing on dip_sw[27] relative to clock(s) clk
Related violations: <none>
TIMING-18#23 Warning
Missing input or output delay
An input delay is missing on dip_sw[28] relative to clock(s) clk
Related violations: <none>
TIMING-18#24 Warning
Missing input or output delay
An input delay is missing on dip_sw[29] relative to clock(s) clk
Related violations: <none>
TIMING-18#25 Warning
Missing input or output delay
An input delay is missing on dip_sw[2] relative to clock(s) clk
Related violations: <none>
TIMING-18#26 Warning
Missing input or output delay
An input delay is missing on dip_sw[30] relative to clock(s) clk
Related violations: <none>
TIMING-18#27 Warning
Missing input or output delay
An input delay is missing on dip_sw[31] relative to clock(s) clk
Related violations: <none>
TIMING-18#28 Warning
Missing input or output delay
An input delay is missing on dip_sw[3] relative to clock(s) clk
Related violations: <none>
TIMING-18#29 Warning
Missing input or output delay
An input delay is missing on dip_sw[4] relative to clock(s) clk
Related violations: <none>
TIMING-18#30 Warning
Missing input or output delay
An input delay is missing on dip_sw[5] relative to clock(s) clk
Related violations: <none>
TIMING-18#31 Warning
Missing input or output delay
An input delay is missing on dip_sw[6] relative to clock(s) clk
Related violations: <none>
TIMING-18#32 Warning
Missing input or output delay
An input delay is missing on dip_sw[7] relative to clock(s) clk
Related violations: <none>
TIMING-18#33 Warning
Missing input or output delay
An input delay is missing on dip_sw[8] relative to clock(s) clk
Related violations: <none>
TIMING-18#34 Warning
Missing input or output delay
An input delay is missing on dip_sw[9] relative to clock(s) clk
Related violations: <none>
TIMING-18#35 Warning
Missing input or output delay
An input delay is missing on touch_btn[0] relative to clock(s) clk
Related violations: <none>
TIMING-18#36 Warning
Missing input or output delay
An input delay is missing on touch_btn[1] relative to clock(s) clk
Related violations: <none>
TIMING-18#37 Warning
Missing input or output delay
An input delay is missing on touch_btn[2] relative to clock(s) clk
Related violations: <none>
TIMING-18#38 Warning
Missing input or output delay
An input delay is missing on touch_btn[3] relative to clock(s) clk
Related violations: <none>
TIMING-18#39 Warning
Missing input or output delay
An output delay is missing on dpy0[0] relative to clock(s) clk
Related violations: <none>
TIMING-18#40 Warning
Missing input or output delay
An output delay is missing on dpy0[1] relative to clock(s) clk
Related violations: <none>
TIMING-18#41 Warning
Missing input or output delay
An output delay is missing on dpy0[2] relative to clock(s) clk
Related violations: <none>
TIMING-18#42 Warning
Missing input or output delay
An output delay is missing on dpy0[3] relative to clock(s) clk
Related violations: <none>
TIMING-18#43 Warning
Missing input or output delay
An output delay is missing on dpy0[4] relative to clock(s) clk
Related violations: <none>
TIMING-18#44 Warning
Missing input or output delay
An output delay is missing on dpy0[5] relative to clock(s) clk
Related violations: <none>
TIMING-18#45 Warning
Missing input or output delay
An output delay is missing on dpy0[6] relative to clock(s) clk
Related violations: <none>
TIMING-18#46 Warning
Missing input or output delay
An output delay is missing on dpy0[7] relative to clock(s) clk
Related violations: <none>
TIMING-18#47 Warning
Missing input or output delay
An output delay is missing on dpy1[0] relative to clock(s) clk
Related violations: <none>
TIMING-18#48 Warning
Missing input or output delay
An output delay is missing on dpy1[1] relative to clock(s) clk
Related violations: <none>
TIMING-18#49 Warning
Missing input or output delay
An output delay is missing on dpy1[2] relative to clock(s) clk
Related violations: <none>
TIMING-18#50 Warning
Missing input or output delay
An output delay is missing on dpy1[3] relative to clock(s) clk
Related violations: <none>
TIMING-18#51 Warning
Missing input or output delay
An output delay is missing on dpy1[4] relative to clock(s) clk
Related violations: <none>
TIMING-18#52 Warning
Missing input or output delay
An output delay is missing on dpy1[5] relative to clock(s) clk
Related violations: <none>
TIMING-18#53 Warning
Missing input or output delay
An output delay is missing on dpy1[6] relative to clock(s) clk
Related violations: <none>
TIMING-18#54 Warning
Missing input or output delay
An output delay is missing on dpy1[7] relative to clock(s) clk
Related violations: <none>
TIMING-18#55 Warning
Missing input or output delay
An output delay is missing on leds[0] relative to clock(s) clk
Related violations: <none>
TIMING-18#56 Warning
Missing input or output delay
An output delay is missing on leds[10] relative to clock(s) clk
Related violations: <none>
TIMING-18#57 Warning
Missing input or output delay
An output delay is missing on leds[11] relative to clock(s) clk
Related violations: <none>
TIMING-18#58 Warning
Missing input or output delay
An output delay is missing on leds[12] relative to clock(s) clk
Related violations: <none>
TIMING-18#59 Warning
Missing input or output delay
An output delay is missing on leds[13] relative to clock(s) clk
Related violations: <none>
TIMING-18#60 Warning
Missing input or output delay
An output delay is missing on leds[14] relative to clock(s) clk
Related violations: <none>
TIMING-18#61 Warning
Missing input or output delay
An output delay is missing on leds[15] relative to clock(s) clk
Related violations: <none>
TIMING-18#62 Warning
Missing input or output delay
An output delay is missing on leds[1] relative to clock(s) clk
Related violations: <none>
TIMING-18#63 Warning
Missing input or output delay
An output delay is missing on leds[2] relative to clock(s) clk
Related violations: <none>
TIMING-18#64 Warning
Missing input or output delay
An output delay is missing on leds[3] relative to clock(s) clk
Related violations: <none>
TIMING-18#65 Warning
Missing input or output delay
An output delay is missing on leds[4] relative to clock(s) clk
Related violations: <none>
TIMING-18#66 Warning
Missing input or output delay
An output delay is missing on leds[5] relative to clock(s) clk
Related violations: <none>
TIMING-18#67 Warning
Missing input or output delay
An output delay is missing on leds[6] relative to clock(s) clk
Related violations: <none>
TIMING-18#68 Warning
Missing input or output delay
An output delay is missing on leds[7] relative to clock(s) clk
Related violations: <none>
TIMING-18#69 Warning
Missing input or output delay
An output delay is missing on leds[8] relative to clock(s) clk
Related violations: <none>
TIMING-18#70 Warning
Missing input or output delay
An output delay is missing on leds[9] relative to clock(s) clk
Related violations: <none>
TIMING-18#71 Warning
Missing input or output delay
An output delay is missing on video_de relative to clock(s) clk
Related violations: <none>
TIMING-18#72 Warning
Missing input or output delay
An output delay is missing on video_hsync relative to clock(s) clk
Related violations: <none>
TIMING-18#73 Warning
Missing input or output delay
An output delay is missing on video_red[0] relative to clock(s) clk
Related violations: <none>
TIMING-18#74 Warning
Missing input or output delay
An output delay is missing on video_red[1] relative to clock(s) clk
Related violations: <none>
TIMING-18#75 Warning
Missing input or output delay
An output delay is missing on video_red[2] relative to clock(s) clk
Related violations: <none>
TIMING-18#76 Warning
Missing input or output delay
An output delay is missing on video_vsync relative to clock(s) clk
Related violations: <none>
TIMING-47#1 Warning
False path or asynchronous clock group between synchronous clocks
A Clock Group timing constraint is set between synchronous clocks cpu_clk and sys_clk (see constraint position 6 in the Timing Constraint window in Vivado IDE). It is not recommended to cover synchronous clock domains with constraints that prevent timing analysis as the design could fail in hardware.
Related violations: <none>
TIMING-47#2 Warning
False path or asynchronous clock group between synchronous clocks
A Clock Group timing constraint is set between synchronous clocks sys_clk and cpu_clk (see constraint position 6 in the Timing Constraint window in Vivado IDE). It is not recommended to cover synchronous clock domains with constraints that prevent timing analysis as the design could fail in hardware.
Related violations: <none>
XDCC-1#1 Warning
Scoped Clock constraint overwritten with the same name
A new clock constraint create_clock overrides a previous scoped clock constraint with the same name. It is not recommended to override a scoped (typically an IP) clock constraint and could result in unexpected behaviors.
New: create_clock -period 20.000 -name clk -waveform {0.000 10.000} [get_ports clk] (Source: /home/fallensigh/Dev/ciciec2026_loongson_regional/fpga/constraints/soc.xdc (Line: 4))
Previous: create_clock -period 20.000 [get_ports clk] (Source: /home/fallensigh/Dev/ciciec2026_loongson_regional/fpga/project/ipgen/clk_pll/clk_pll.xdc (Line: 56))
Related violations: <none>
XDCC-7#1 Warning
Scoped Clock constraint overwritten on the same source
A new clock constraint create_clock overrides a previous scoped clock constraint defined on the same source. It is not recommended to override a scoped (typically an IP) clock constraint and could result in unexpected behaviors.
New: create_clock -period 20.000 -name clk -waveform {0.000 10.000} [get_ports clk] (Source: /home/fallensigh/Dev/ciciec2026_loongson_regional/fpga/constraints/soc.xdc (Line: 4))
Previous: create_clock -period 20.000 [get_ports clk] (Source: /home/fallensigh/Dev/ciciec2026_loongson_regional/fpga/project/ipgen/clk_pll/clk_pll.xdc (Line: 56))
Related violations: <none>