Forum Discussion

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

Build Megawizard/QSYS Systems from command-line (for build environment)

Hi.

I want to build my Quartus projects (huge Arria II GX and Arria V setups) automatically on a remote build server.

But there's one major problem: My project contains multiple Megawizard and QSYS Components.

Currently, I only store .qip and .vhd files in our CVS system. This works great if you open the Quartus GUI, double-click the Component and click generate to create the underlying compents like altgx_reconfig, altgx_pll, etc.

But when using the command-line, the command

quartus_sh --ip_upgrade -variation_files %path_to%\altgx_transceiver.qip %project%

simply does nothing. The command line states a successful execution, but no files are created.

Is it possible to fully create PCIE Compiler IPs, Transceiver Setups, etc. from pure .vhd/.qsys files?

Do I have to somehow parse the qip settings file to create new components? Can anybody sent an example how to do this?

Best regards,

_X_

2 Replies

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

    Hello _X_,

    the "qsys-generate" command builds your qsys system from a .qsys file: 

    
qsys-generate --synthesis=VERILOG soc.qsys

    "qmegawiz" to build your megawizard component: 

    
qmegawiz -silent OPTIONAL_FILES=NONE pll.v

    These commands can be used from a console or called from a .tcl script.

    There is no need to store the .qip file in the repository as this and the .sip files are generated with above commands from your <module>.v (or .vhd).

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

    Thank you very much.

    I previously used commands like 

    
qmegawiz ../Subcomponents/SystemPLL/SystemPLL.vhd
qmegawiz module=altpll ../Subcomponents/SystemPLL/SystemPLL.vhd

    The first opened the gui, the second show some text about missing options. But 

    -silent OPTIONAL_FILES=NONE
    fixed this.

    I read several documentations, but couldn't find anything.

    So thanks a lot...

    Best regards,

    Dirk :-)