Forum Discussion
Custom IP from a verilog code
- 3 years ago
The component editor mis-identified your component as an agent instead of a streaming source, so that's why the errors appeared. You fixed the errors by defining the interfaces and signal roles so you are good to go. To avoid this from happening in the future, in your code use the 3-part naming scheme for interface signals discussed in the Platform Designer user guide: <interface type>_<interface name>_<defined signal role>. This automates how Component Editor identifies the signals in your design.
The component editor mis-identified your component as an agent instead of a streaming source, so that's why the errors appeared. You fixed the errors by defining the interfaces and signal roles so you are good to go. To avoid this from happening in the future, in your code use the 3-part naming scheme for interface signals discussed in the Platform Designer user guide: <interface type>_<interface name>_<defined signal role>. This automates how Component Editor identifies the signals in your design.