Forum Discussion

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

NIOS Custom peripherals

Folks,

I got a simple PIO avalon peripheral set up and working in no time. Now I'm stuck on the next step, having an avalon peripheral that has connections inside the same design that the NIOS is in. For instance. I have a cyclone design with its top-level VHDL file containing a few components. One of these components is a NIOS-16. The NIOS has a custom peripheral that has signals that also connect to one of the components at the top-level of the design. If I instantiate the custom peripheral in the top-level VHDL file, the avalon connections go unconnected and give me an error. The SOPC builder accepted the custom peripheral no sweat. What is the correct strategy for this?

If you quote any docs, please name the doc and the page number.

Thanks

1 Reply

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

    Folks,

    I discovered the answer in AN-333 page 13. To make your custom peripheral a stand-alone, just dont import the design files. When the NIOS is built, it will define new (very verbose) signal names as I/O of the NIOS component. Works great.