You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Already discussed here running 8.StressTest/LUTRAM_Stress_test causes the router to fail at approximately 10% CPE utilization. Recognizing the challenge posed by the wide output multiplexer routing, I modified the test to focus solely on memory capacity—using the 8.StressTest/LUTRAM_adjusted_stress_test, where outputs are condensed to a single bit. Even with this adjustment, we haven't exceeded 58% utilization.
I'm trying to determine which aspect of the design is causing the constriction, but I'm struggling to find the crucial information. Specifically, I have two questions regarding the debugging process:
How to extract information about the routing fails tracing it to the source from messages such as: FATAL ERROR: 106 not routed! or CPE_OUTMUX congestion at Component 333 with 353
Already discussed here running
8.StressTest/LUTRAM_Stress_test
causes the router to fail at approximately 10% CPE utilization. Recognizing the challenge posed by the wide output multiplexer routing, I modified the test to focus solely on memory capacity—using the8.StressTest/LUTRAM_adjusted_stress_test
, where outputs are condensed to a single bit. Even with this adjustment, we haven't exceeded 58% utilization.I'm trying to determine which aspect of the design is causing the constriction, but I'm struggling to find the crucial information. Specifically, I have two questions regarding the debugging process:
FATAL ERROR: 106 not routed!
orCPE_OUTMUX congestion at Component 333 with 353
The text was updated successfully, but these errors were encountered: