Honored Contributor
Honored ContributorHi Daixiwen,
I'm a little bit confused. . . . I will try to implement my port list as you suggested, but I have to think about it because I can't do it exactly like you suggested. In the meantime, I wonder, why I have to name the second part of the interface name as you suggested. In the Quartus II Handbook Version 9.0 Volume 4: SOPC Builder on page 6-4 it is said that "For any value of <interface_name> the component editor automatically creates an interface by that name. I thought that this is the part of the naming convention, where I can choose my own name for the port (or better pin), which I can bind to the actual function it has. I also don't understand why you suggest something like this: coe_i2c_sda instead of the original coe_sda_export where the first part is the interface type (-> coe, conduit), the second part is the actual interface name that I chose (-> sda) and the last ist the signal type (-> export) which defines that this pin is connected to external logic . . . E.g., I totally miss this "export" in your suggestion. Maik
