Hello, when I design a project, there are many modules in this project, in one of the modules (not the top module) I mark the wrong io type (for example: input tag to output), and in the module This...
Hi, perhaps I didn't yet understand the example. I believe you'll get compilation errors in most cases.
Connecting an output port to a signal that is expected to drive an input will give a multiple driver error, because the signal is already driven. The reverse situation won't cause an error in the upper hierarchhy level, just leave an undriven signal. But in the lower hierarchy (module implementation) level, you can't drive the erroneously defined input without causing an error.
So you are apparently talking about a consistently designed module that is connected erroneously in the upper hierarchy. I think confusing in- and output ports is only one of many possible wrong connections and no particular case.
You'll want some kind of verification, e.g. with a simulator. It an easily mark undriven signals.
First of all thanks for your reply, I'll give you an example to describe the problem I'm having.
You can see the Main_Seq module, PWRGD_a is the input, but I marked it as output. The final result b_EN will become high during simulation, which is also successful in quartus sythesize, but b_EN will not become high in the actual synthesis circuit.
Do you know how to verify this problem or use some settings in sythesize to avoid this problem?