"Interface to User Logic" vs "User Component"

Altera_Forum · ‎01-06-2006

Have been building User Components for specific HDL design until met On-Chip MEM Bus mapping problem.

I understand one of our Nios God (BadOman) mentioned, all the LEGACYs are for old designs. But the instantiation option "Export Bus Ports" in "interface to User Logic" seems to essential for me and this option is not presented in "User Logic"

Does any one have detail idea about the difference between using "Legacy Components --> Interface to User Logic" & "User Logic --> ***(User Component)"

I've searched around Quartus II handbook, Nios Peripheral Handbook, SOPC datasheet, no useful help.

Thanks a lot!

Altera_Forum · ‎01-06-2006

--- Quote Start ---

originally posted by legendbb@Jan 6 2006, 08:51 AM

have been building user components for specific hdl design until met on-chip mem bus mapping problem.

i understand one of our nios god (badoman) mentioned, all the legacys are for old designs. but the instantiation option "export bus ports" in "interface to user logic" seems to essential for me and this option is not presented in "user logic"

does any one have detail idea about the difference between using "legacy components --> interface to user logic" & "user logic --> ***(user component)"

i've searched around quartus ii handbook, nios peripheral handbook, sopc datasheet, no useful help.

thanks a lot!

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=12018)

--- quote end ---

--- Quote End ---

If you use the componet editor to create a new componet, you can export the Avalon Interface signals (address, data etc..) directly if you just add your signals names in the signals tab (and have no HDL files added) - the component editor exports the signals automatically. This should work for slave or master interfaces to your component. I found the following app note to be helpful in understanding directly exported Avalon signals (AN397: Interfacing to external processors) -

http://www.altera.com/literature/an/an397.pdf (http://www.altera.com/literature/an/an397.pdf)

Although this app note covers exporting a master interface to outside logic it should also apply to a slave interface. Note this only applies to components with no HDL files, if you have HDL files in your component (for interface logic) then you will have to create the additional signals in your top level HDL that "export" the Avalon signals and do the signal mapping inside your HDL code (i.e. assign the Avalon address bus lines to the exported address bus).

As I understand it, the component editor should be able to do almost everthing that the old interface to user logic does (although the steps to do it are different). The component editor also has some additional features for building advance components such as a multi-interface component that couldn't be done with the old interface to user logic.

I hope this helps.

PS. Also you may want to look at "Building memory subsystems using SOPC Builder" in the Quartus II handbook chapter 8

http://www.altera.com/literature/hb/qts/qts_qii54006.pdf (http://www.altera.com/literature/hb/qts/qts_qii54006.pdf)

The last sections of this chapter has some useful info on the component editor and off-chip memories.

Altera_Forum · ‎01-06-2006

Think of Interface to User Logic being a subset of features present in Component Editor. You don't have anything to gain by using Interface to User Logic (that I can think of anyway) so I would use Component Editor simply for that reason. As for the exporting feature, it is present.

I often build components outside of SOPC Builder top level first so that I can stick to the same SOPC generated system and just modify the component by itself (just a force of habit). Now days in order to do this I click the menu option that creates a generic list of signals that is common in most components making this a one button process (just like what you want to use Interface to User Logic for).

I hope that helps explain why I think most people really don't have a need for Interface to User Logic. Besides if some really great feature comes down the pipe for Component Editor I wouldn't hold your breath to see it in Interface to User Logic.

Altera_Forum · ‎01-09-2006

BadOmen,

I like the legacy user logic, because I used it already from the beginning, as long that I need no more functions than available in this component, I don't think there is a problem.

I think a lot of people can not spend time to try how the new software toys look like everytime it is changing. Most people change only bacause it is necessary for some 'real' new features.

Stefaan