Newbie here - please be gentle :-)
I'm using OpenCore Plus to evaluate an Altera megafunction, and getting the expected limitations with either having to be tethered or timed out. When tethered, after configuring the FPGA there is a message box that grabs focus warning me of the limitations - which if I cancel, stops my application. This stops me getting to SignalTap to debug and verify my design - which seems counter productive to the whole process. In my view the message box warning is valid, but it should allow me to cancel it, or move to a different window, without killing the app. I can work around the issue by either unplugging the USB Blaster from the target before cancelling the warning, then reconnecting and firing up SignalTap; or by running SignalTap in another instance of Quartus. But its a pain. Am I missing something, are there other workarounds, or is this a standard issue irritance? simonsseLink Copied
the easiest way to get around this is to open 2 quartus windows. One for programming the FPGA, and the other for signaltap.
--dalonyeah i faced the same issue..but seems like its normal practice to do what dalon mentioned..
But i do agree that its unintuitive to new usersFor more complete information about compiler optimizations, see our Optimization Notice.