Forum Discussion
Question about Monitor
Hello,
is it possible to synthesize the "monitors" on the altera fpgas'. There are Monitor IPs such as Avalon MM Monitor. Can I synthesize such "Monitors"?117 Replies
- Altera_Forum
Honored Contributor
can please you explain more about conduits? I read the manual did not help much!
Thanks, Adi - Altera_Forum
Honored Contributor
--- Quote Start --- This is what I did: I created a variation of PCI [actually no/very little variation] using Megafunction Wizard. I got a verilog file for that IP that contained variations [since I did not do any variations, I got a .v for that IP] and then I included that file in the component editor. Then the component editor generated the _hw.tcl file. Is this technique alright? --- Quote End --- If the IP has an Avalon interface, then yes, this would work fine. The other way to do it, is to use the component editor to create the Avalon interfaces in an _hw.tcl file that does not include any Verilog/VHDL source. This then sets a flag in the Tcl telling it not to instantiate the IP inside the SOPC system. The top-level SOPC system then has Avalon ports that you can connect your IP to. This would be useful if your Megawizard generated component had conduit ports or port widths that change based on generics, since you could edit the part with the MegaWizard tool, and not have to change anything in SOPC builder. Cheers, Dave - Altera_Forum
Honored Contributor
I think I just did that. This is what I did: I created a variation of PCI [actually no/very little variation] using Megafunction Wizard. I got a verilog file for that IP that contained variations [since I did not do any variations, I got a .v for that IP] and then I included that file in the component editor. Then the component editor generated the _hw.tcl file. Is this technique alright?
I dont know why Qsys is allowing this custom component[nothing but PCI] but not the actual PCI IP from Quartus 9.1 sp1. - Altera_Forum
Honored Contributor
--- Quote Start --- Yes I get what you are saying; so, using megafunctions is same as double clicking on the ip's and changing their parameters in the system contents tab [the place where you interconnect components] right? --- Quote End --- Right. I think Altera has made several components that can be accessed either via the MegaWizard or via Qsys. I suspect that for the components you are interested in, you will have to write your own Qsys wrapper. --- Quote Start --- I am trying to add new ports such as reset etc.. for Mega IPs such as PCI - compiler. I guess, I have to use component editor if I need to create new IP's. --- Quote End --- You will suffer less if you control the code; so just create the MegaWizard IP using the MegaWizard GUI, and then create your own Qsys components and their associated _hw.tcl. Once you get it working for your PCI component, it'll be easy to get it working for anything else. Cheers, Dave - Altera_Forum
Honored Contributor
Yes I get what you are saying; so, using megafunctions is same as double clicking on the ip's and changing their parameters in the system contents tab [the place where you interconnect components] right?
I am trying to add new ports such as reset etc.. for Mega IPs such as PCI - compiler. I guess, I have to use component editor if I need to create new IP's. Thanks, Adi - Altera_Forum
Honored Contributor
--- Quote Start --- when I create a variation of the component using Megafunction. Can I make the new component to show up in the IP list? --- Quote End --- Megafunctions and Qsys are different tools. Not all Megafunctions have Avalon interfaces, so they cannot be used within Qsys without first creating a custom Avalon-MM or ST interface. If you used generics in your Qsys definition of the component interface, you could then pass those down to the Megafunction component. Is that what you were asking? Cheers, Dave - Altera_Forum
Honored Contributor
Okay,I will do that. when I create a variation of the component using Megafunction. Can I make the new component to show up in the IP list?
- Altera_Forum
Honored Contributor
--- Quote Start --- When I try to import an older system into Qsys I get the following errors and doubts: --- Quote End --- I haven't used Qsys to import SOPC Builder projects, so cannot help answer your questions. Try posting a new thread with a title like "Errors when importing SOPC system into Qsys", and see if someone else can offer advice. Cheers, Dave - Altera_Forum
Honored Contributor
Hey Dave,
When I try to import an older system into Qsys I get the following errors and doubts: errors: 1. component xxx must have an associated reset. [i edited the pins and got rid of the error for one of the simple design.]. does qsys create a global reset pin ? [ i get this for all the components] 2. it says asks me to replace pci-compiler with a compatible component. doubts a. Why does it not complain about not finding the PCI-compiler IP in it's IP list? b.Automatically coundits show up in all the components [What are they?(i read the manual, but not satisfied with explanation) and why are they created]. I Igonered the conduits in one of my designs: the simulation worked fine and I could also run the "compile Design without any errors" c. Instead of creating the new system with PCIe, can I use the MegaIP wizard to modify the PCI-compiler and then add it to my Qsys system. [Any component is related with only two files right?; its verilog file and _hw.tcl file] Thanks and have a joyous day, Aditya - Altera_Forum
Honored Contributor
--- Quote Start --- Got it! --- Quote End --- Great! Cheers, Dave