Forum Discussion
Altera_Forum
Honored Contributor
18 years agoThanks for both of you...
Yes, it's overconstraining. But it isn't the root reason led to the result. I have found the reason, it's hard to decribe, but I will try: My IP has 360 channel of sub-module, they are the same module which has two 32-bit registers. After compilation, custom IP allocate over 80% of FPGA resource which mean that custom IP's registers distribute all over the FPGA. NiosII CPU need read value of register's of selected channel indexed by address bus. So there exist because address register and slavedata register. As above described, slavedata registers distribute all over the FPGA, so the critical path showed above is reasonable and can't be eliminated. I think What I should do is the following two steps: 1. In SOPC Builder component editor, configurate suitable setup time and wait time for my custom IP 2. In QuartusII, set multicycle constraint for the path from address register to slavedata register Am I right? m1_address[10]" and destination register "FreqMeasure_NiosII:inst|freqmeasure_avaloninterface_inst:the_freqmeasure_avaloninterface_inst|freqmeasure_wholesystem:the_freqmeasure_wholesystem|avs_freqmeasure_slave_readdata[18]