when I check the signals it shows two IOCLK as output pin and the others as input pin.I'd normally expect it to be part of the component though, rather than something you add on the schematic. It also looks a bit like a buffer symbol, so it could be just to signify that this one is the line that is buffered by the chip, and not the DIVCLK line. I just updated another picture, it looks weird if it's input, and I confirmed in schematic it's an output pin. I checked the Verilog module didn't find any sign of buffer connected with those pins.I try to add any IP to the schematic but not accept.. After the HDL synthesis phase of the synthesis process, you can display a schematic representation of your synthesized source file.
It turns out that XST has two different VHDL parsers, the newer one seems to be better.
Interestingly when I design a test bench around the functions the results are correct.
When I simulate my design in the project using a combination of generates and functions the hardware is wired correctly.
@The Photon I have no warnings in my synthesis and implementation report, and yet I do not achieve the expected results. Here is the link to my files drive.google.com/…@The Photon I expected to get a debounced output at an FPGA pin, in response to an input at an FPGA pin, but that does not seem to happen, even though the behavioural simulation shows everything working perfectly, and no warnings in the synthesis or the implementation step. Are you sure your real-world stimulus has similar timing to what you tested with in simulation? If you look at the CLB User Guide, you'll see that there are dedicated structures in each slice called "AMUX", "BMUX", "CYMUX", etc.
The name "MMux" may just be to distinguish your inferred mux from any of those muxes.