Forum Discussion
Hi travisa,
"Also, is there any reason other than improving the IP timing for changing Address unit from SYMBOLS to WORDS "
No other reason than improving timing. If it's not working on your design, then you can still set Address unit with SYMBOLS. If there is some timing violation, later you can get some advice from Timing expert.
" (I really would like to know is there any specific reason you used clock bridge IP to clock FIFO IP, instead of the clock from Clock IP or Clock from Avalon-MM DMA Hard IP?)"
Because the input of the FIFO IP has been exported, the QSYS has recommended that the clock of FIFO IP need to be exported as well. But it's cannot be exported directly.
One of the recommendation here is to export the clock through a clock bridge or a clock source.
You can still connect it with a clock source.
"Would you please remind me why we should change the address specifically to 0x1_0000_0000 or higher?"
The master has connected with the emif and fifo. The address 0 - ffff_ffff has been used for emif. Then the fifo cannot overlap this address which is means it's should be higher than ffff_ffff.
"By changing address to what you suggested removes error messages. Then ran the Generate HDL (as seen in CaptureA9.PNG (do we want to worry about the warning messages as seen in screenshot?) and then successfully compiled the project."
It's good if you can take a look on it because the Quartus cannot perform the auto IP upgrade due to different Quartus edition and instead perform manual upgrade in the QSYS.
Then the Quartus will create another path to store the IP components that have been regenerated.
I have checked the missing parameter and it's actually exist in the code.
If you want to remove the warning messages, you can create another project and mimic the IPs that have been used.
"I there any thing we should be cautious in creating a custom IP that creates bits and feeds to FIFO?"
I'm not an expert on this area but I'm thinking that you should take care the data that will be connected to FIFO.
Regards,
Adzim
Hi Adzim,
Thank you very much for explaining things very well. I have a couple of quick questions too.
What is the real cause of the error "Port mismatch could not be auto resolved. Double click for manual resolution"? I it just merge option by double clicking the error? (Attached screenshot 7.PNG gets after double clicking the port mismatch message ). What is the recommended solution for this and what are the things we must consider in selecting between accept default or accept merge options in the screenshot.
Also, in the last e-mail, you mentioned "you should take care the data that will be connected to FIFO". Could you please elaborate it little bit? What are the specs. of data that I should take care?
Thanks again!