Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
10 years ago

Edit an existing custom Megafunction

Hi everybody,

I am having a small problem. I am using the Altera Quartus Subscription edition 15. To interface with my DE4 board I wanted to use the Xillybus driver.

Therefor I wanted to compile the demo version.

In the description I can find these lines:

'Before compiling the design, create a local copy of the IP compiler for

PCI Express core: Launch the MegaWizard Plug-In Manager from within

Quartus II from the Tools menu. Choose Edit an existing custom megafunction

variation, and pick the pcie_s4_4x.v file in the pcie_core directory.

When the wizard for IP Compiler for PCI Express opens, just click Finish

to generate the core's files, and click Exit when the process finishes.'

This demo was developed for Quartus 12. But I really can't find the possibility to edit an megafunction. Can somebody please point me in the right direction? i think in the last versions there was a bigger change in the megafunction section.

Thanks for reading :)

8 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    In later versions of Quartus (14.0 and later, I think), megawizard was renamed to IP Catalog. Megafunctions were renamed to IP Components. So it sounds like you'll want to create an existing custom IP component, and there's a nice tutorial on Youtube here: https://www.youtube.com/watch?v=v6rhbvablo8

    Hope this helps! :)

    -January
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    The "Latest" version of Quartus II is not smart enough to recognize an IP MegaWizard component based only on its Verilog or VHDL file. I found that I had to go back to a version that still had the MegaWizard tool, open the .v file, generate the output files, including the .qip file, and then use Quartus 15.0 to open that IP.

    Very annoying really ...

    Cheers,

    Dave
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Hi,

    If you have the QAR of the design created with older Quartus II version, by default, if you un-archive it with the latest Quartus II 15.0, it should help to perform auto-upgrade of all the IP that you have included in the design. You can try to see if this works for you.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    You may try to open up your project in Quartus II 15.0, then use the File -> Open to point to the PCIe module .v files to see if Quartus II can recognize and open it up in IP Parameter Editor?

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Thanks for everyone.

    I tried everything you mentioned, but the only "solution" for me was to install an additional old version of Quartus...
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    I believe somehow the latest Quartus II version is unable to auto-upgrade some of the IPs. Another alternative to using older Quartus II version, you might want to re-instantiate the affected IP in the new Quartus II version. However, you would need to find out the affected IP and its corresponding newer version IPs.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    I have been doing a Q15 migration, and I have had to regenerate certain cores in Q15 (PCIe. Seriallite, SRIO) without being able to auto upgrade. But I also noticed that only the version they were generated with is able to open them. because we have cores generated in Q 11 and Q12.

    Also annoying, Q15 IP catalogue no longer has a GUI to configure your transceivers - the settings have to be put manually into the QSF file, or you need to hand edit the generated verilog. Never a good idea.!
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    10 years ago

    Agree with Tricky. I believe version 15 vs version 12 might be a bit far and this might lead to failure to perform auto-upgrade. In addition, from 13.1 to 14.0, there is a significant switch from Megawizard to IP Parameter Editor which might cause the older Megawizard generated files unable to be recognized.