Forum Discussion
Altera_Forum
Honored Contributor
10 years agoI have seen similar warnings when using altsyncram. I traced it to the tri0 and tri1 signal types of the signals in the altera module.
I had a wr_clock_en and a wr_en in the port list of the altera ram module. If I used the same signal (a wire) to drive both ports then further down in the hierarchy of the altera module wr_clock_en was defined as tri0 and wr_en was defined as a tri1. This is presumably to set these ports to a set value if nothing is connected to them. Since the driving signal is essentially connecting these two signals together and is a 'wire', it could potentially have a Z value. If the driving signal was Z then tri0 and tri1 are trying to drive the same line and competing against each other causing the modelsim warning. This is a just a simulation problem To workaround it you can split the driving signal in to two wires by using assign sig2 = sig1; This appears to fix. Although I haven't tried it, I also suspect if you are using systemverilog and you used the 'bit' data type to drive both port signals instead of a 'wire' then this should fix it as well. C