Quartus Simulation Error: Formal port ".." has OPEN or no actual associated with - Page 1
Forum section: electronics / general

author: RedLion
author_rank: Regular Contributor
timestamp: August 26, 2020, 12:21:07 pm
content: Hello all,I'm trying to simulate a piece of a project in Intel Quartus Lite 19.1 using the University Program .vwf.It's somewhat of a large project, so I only wanted to simulate the block that's causing issues right now.However I'm getting the following error messages that I'm not sure how to interprete. I have no nets or pins in my project by these names, but some of them sound vaguely JTAGesque? Google didn't spit out anything helpful so far.# ** Error: Lauflicht.vho(7513): (vcom-1035) Formal port "tdoutap" has OPEN or no actual associated with it.# ** Error: Lauflicht.vho(7513): (vcom-1035) Formal port "tmscore" has OPEN or no actual associated with it.# ** Error: Lauflicht.vho(7513): (vcom-1035) Formal port "tckcore" has OPEN or no actual associated with it.# ** Error: Lauflicht.vho(7513): (vcom-1035) Formal port "tdicore" has OPEN or no actual associated with it.# ** Error: Lauflicht.vho(7513): (vcom-1035) Formal port "corectl" has OPEN or no actual associated with it.# ** Error: Lauflicht.vho(7513): (vcom-1035) Formal port "ntdopinena" has OPEN or no actual associated with it.# ** Error: Lauflicht.vho(24545): VHDL Compiler exiting# End time: 13:56:50 on Aug 26,2020, Elapsed time: 0:00:00# Errors: 7, Warnings: 0# ** Error: c:/intelfpga_lite/19.1/modelsim_ase/win32aloem/vcom failed.# Executing ONERROR command at macro ./Lauflicht.do line 3Error.Also, is there a clever way to put code in a post that I haven't seen? Seems strange to just paste it in the post like thatThanks

author: mfro
author_rank: Regular Contributor
timestamp: August 26, 2020, 01:58:18 pm
content: are you on a MAX 10 by chance?

author: RedLion
author_rank: Regular Contributor
timestamp: August 26, 2020, 10:45:40 pm
content: Quote from: mfro on August 26, 2020, 01:58:18 pmDammit, forgot to specify that.Yup, I am. 10M50DAF484C7G to be exact.Good guess or something I should have known but didn't?

author: mfro
author_rank: Regular Contributor
timestamp: August 27, 2020, 06:45:36 am
content: Quote from: RedLion on August 26, 2020, 10:45:40 pmNot really. Just remember struggling with something similar on my MAX10 as well (although I can't remember what I did to remedy).The ports you appear to have problems with are part of the MAX10 secure mode feature (seehttps://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/hb/max-10/ug_m10_config.pdfandhttps://www.intel.com/content/dam/altera-www/global/en_US/uploads/5/5f/MAX10_JTAG_Secure_Unlock_UG.pdf)Did you, by any chance, enable "Verify protect" in the MAX 10 device options?

author: Bassman59
author_rank: Super Contributor
timestamp: August 27, 2020, 03:36:42 pm
content: In general this error means that you've instantiated an entity but did not include all of the ports on that entity in your instance. A port declared as an output should throw a warning if not connected in the instance (you should use OPEN to indicate that the port has no connection) but all input ports must have something driving them.Now if this is something automatically instantiated by Intel's tools ... I got nothin', other than to say you should still look at the instance.

author: RedLion
author_rank: Regular Contributor
timestamp: September 13, 2020, 07:30:41 pm
content: Update: I am a massive idiot.The entire problem was that I had pins for a 7-Seg-Display, named 7segA, 7segB etc...When programming, that is not an issue. But when those are in a testbench, they end up as signals in an HDL file.And, signal names starting with a number is, as we all know, a Big No No. One could have known that.Hence, massive idiot.It took me deleting the .vwf file and retrying, then I got a different error message, something with "no separator between string" something something, pointing to a .vwf.vht file. Once I opened that, sure enough, all my pins were reinterpreted as integers.Now was that the original fault? I don't know. Possibly.Was itafault? Sure as hell was.What did we learn? "Turning it off and on again", not just for confusers! Oh and stick to the bloody coding conventions.