- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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. ThanksLink Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page