cancel
Showing results for 
Search instead for 
Did you mean: 
Voyager
Voyager
1,047 Views
Registered: ‎07-28-2008

Custom IP packing existing code doesn't seem to work for me (Vivado 2018.2)

Jump to solution

My IP has some AXIS and AXI interfaces, it passed synthesis and implementation.

I'd like it to be packed as if I create a new AXI IP through wizard.

 

I started with Create new AXI IP, but since I don't like the way files are named ("_v1.0.v"); I went for my own file naming, and deleted ip generated xml and gui folder.

myip_top.v
myip_S_AXI.v
myip_S_AXIS.v
...

 When I'm ready to pack, pack existing folder or pack current project (Packaging IP in the project, Include .xci files), none seem to work for me.

 

Please comment,

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
943 Views
Registered: ‎09-15-2016

Re: Custom IP packing existing code doesn't seem to work for me (Vivado 2018.2)

Jump to solution

Hi @legendbb,

 

Can you please elaborate your requirement? If you choose to create a new AXI4 peripheral, the display name can be changed but why the xgui and .xml is to be deleted?

 

If already IP is present, you can try overwrite existing and check?

 

Capture3.PNG

 

Can you please help reproduce the problem?

 

Thanks

Prathik

-----------------------------------------------------------------------------------

Don't forget to reply, kudo, and mark the appropriate post as 'accept as solution'.

-----------------------------------------------------------------------------------

View solution in original post

0 Kudos
2 Replies
Highlighted
Voyager
Voyager
1,018 Views
Registered: ‎07-28-2008

Re: Custom IP packing existing code doesn't seem to work for me (Vivado 2018.2)

Jump to solution

Just to update, I've tried 2017.1 2017.3 all the same symptom on Windows 10

On Ubuntu 16.02, 2017.1 gives error message instead of getting stuck.

WARNING: [IP_Flow 19-3331] Invalid parameters found in dependency constraints of 'PORT_VECTOR_LEFT.MY_PARAM' 

My mistake to have a port declared as [$clog2(1-1)-1:0] error_port. Interesting Synthesis didn't report on this.

 

0 Kudos
Highlighted
Moderator
Moderator
944 Views
Registered: ‎09-15-2016

Re: Custom IP packing existing code doesn't seem to work for me (Vivado 2018.2)

Jump to solution

Hi @legendbb,

 

Can you please elaborate your requirement? If you choose to create a new AXI4 peripheral, the display name can be changed but why the xgui and .xml is to be deleted?

 

If already IP is present, you can try overwrite existing and check?

 

Capture3.PNG

 

Can you please help reproduce the problem?

 

Thanks

Prathik

-----------------------------------------------------------------------------------

Don't forget to reply, kudo, and mark the appropriate post as 'accept as solution'.

-----------------------------------------------------------------------------------

View solution in original post

0 Kudos