Forum Discussion
Altera_Forum
Honored Contributor
9 years agoIt's not a weird problem, it is expected behavior. The SIGNAL TAP logic analyzer function needs memory to store the captured data, and it uses BLOCK RAM. So when you enable SIGNAL TAP, it will use up some BLOCK RAM.
So, as suggested above, either subset your design, and cut out other BLOCK RAM intensive portions temporarily, or possibly fine tune your SIGNAL TAP debug logic. Reduce the number of captured signals; reduce the depth of the capture. Both of these will reduce the BLOCK RAM requirements. Your usage with SIGNAL TAP is 187/182, and 148/182 without, so your SIGNAL TAP configuration is using 39 BLOCK RAMs for storage. Halve this number and you should be OK.