UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Scholar drjohnsmith
Scholar
5,816 Views
Registered: ‎07-09-2009

Vivado 2015.3, IP files to save have changed , to what . problems with source control

Moved over to Vivado 2015.3 from 2015.2.

 

There seems to have been a change in the way IP cores are stored , and what files are needed to re create them.

 

Upgraded all the cores in a design from 2015.2 to 2015.3 , and design completes.

 

re check in the files, and do a test check out, and re build.

 

The IP's are now complaining that theu have no <ip name>.v files checked in ....

 

Previsouly under ISe and Vivado up to now, we have checked in the <ip name>.xci and <ip name>.dcp, and then the tool has recreated all it needs.

 

Now that is not enough it seems , what has changed please.

 

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
2 Replies
Xilinx Employee
Xilinx Employee
5,794 Views
Registered: ‎09-20-2012

Re: Vivado 2015.3, IP files to save have changed , to what . problems with source control

Hi @drjohnsmith

 

Refer to page-18 to 21 in http://www.xilinx.com/support/documentation/sw_manuals/xilinx2015_3/ug896-vivado-ip.pdf

 

Thanks,

Deepika.

Thanks,
Deepika.
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (the star on the left)
0 Kudos
Scholar drjohnsmith
Scholar
5,784 Views
Registered: ‎07-09-2009

Re: Vivado 2015.3, IP files to save have changed , to what . problems with source control

Thanks 

 

not really an answer to the question though.

 

reading on page 18, abotu the new containers in 2015.3

 

"This optional feature" 

 

i.e not required. 

 

But it seems that containers are required. 

  where as once we had to only check in the small files,

        we now have to change our source control scripts to check in different files, and loose the old files, 

              and so loose the audit trail.

 

Great negative step.

 

Also these containers are bigger than the few filoes we needed to check in, and binary, so version control can only tell us that a file some where in the zip has changed !

  

  bang goes audit trail again. 

 

And to top it off, 

   what we used to check in and worked just fine for the last few years, is now no longer sufficient, 

      

thats the question my client needs answered, 

   which files do we now need to add to the check in so we can keep the audit trail.

       Go on say all of them ..... ! 

 

Its the fact that Xilixn have broken the old system that sis anoying, 

    luckily this client of mine found out after a few weeks work, but that could have been desasterous..

 

 

<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos