Forum Discussion

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

Qsys 14.0 how to export conduit signals from my component to pins

I created a component (john.v) that runs a lot of off-chip periferal parts.

I control it with an avalon lw slave port from hps.

I want to export ca 100 pins from my component directly to pins.

Inputs, outputs, bidir.

In Qsys 13.1.4 Component Editor, the signals all have Interface=conduit

and Signal Type= export. (Width and Direction are as set in john.v.)

john_hw.tcl gets created and later, the fitter uses my "user" pin

assignments from top.qsf and assigns them correctly.

In Qsys14.0, Component Editor, the signals all have Interface=conduit

and Signal Type= export. (Width and Direction are as set in john.v.)

Now I get the error:

"Error: conduit_end: There are multiple signals with role "export".

Components using hw.tcl package 14.0 and greater must specify

unique signal roles."

When I set Signal Type= export1,export2,etc or fclkp,fclkn,etc

the component john_hw.tcl gets created but later, the fitter ignores

my pin assignments made in top.qsf and assigns them randomly.

Searching Quartus manual and Knowledge Base for "signal role" I find

nothing.

With Q14, How do I export signals from my component directly to pins?

Thanks in advance,

John

3 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    OK, thanks to Choon Hee/support, I've figured it out.

    Qsys creates gth31a.v (the project name) as the top file of the project.

    When Qsys 14.0 creates a _hw.tcl component from john.v, I now have to map

    each (uppercase) conduit signal "Name" to a new name in the column "Signal

    Type". To reduce confusion, I chose the same signal name but in lowercase.

    (Uppercase "Signal Types" are not allowed.)

    In Q13.1.4, all my conduit signals had the same "Signal Type" i.e.

    "export" and the (uppercase) names from john.v were migrated up to gth31a.v

    and to the pins.

    Not so with Q14.0.0.

    Alteras idea with conduits was to create a way to pass non-Avalon,

    non-Altera signals. I think it's odd that Qsys 14.0 should require a new

    unique name for these signals.

    Live and learn.

    Case closed.

    -j
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Hello dear jofu

    Can you help me to create new Qsys component in Qsys14.1 with two exported port input and output ? if you have example please email it to me

    Thanks a alot.

    ahmadm at chmail.ir