Thanks for the tip! I think I should use comment/uncomment of code lines
tips.
On Mon, Apr 25, 2022 at 10:32 PM Wade Fife wrote:
> If there's no error message, that usually means Vivado crashed. The last
> time I saw this happen, it was because Vivado ran out of memory, which it
> does not handl
If there's no error message, that usually means Vivado crashed. The last
time I saw this happen, it was because Vivado ran out of memory, which it
does not handle gracefully. I've also seen this happen because of a mistake
in the code that Vivado doesn't expect (something like double driving a
sign
