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: 
Highlighted
Explorer
Explorer
9,470 Views
Registered: ‎11-25-2014

Windows path name length problem

Jump to solution

Dear Xilinx -

 

Is there a solution in the works for this problem? Is it even being discussed internally? I'm going to post this question every few months as the Vivado quarterly releases tick by with no fix and no viable workaround.

0 Kudos
1 Solution

Accepted Solutions
Xilinx Employee
Xilinx Employee
18,026 Views
Registered: ‎10-24-2013

Re: Windows path name length problem

Jump to solution

Hi @rjsefton

 

This is Windows OS limitation.

 

Please check the following AR where some suggestions are given to workaround this.

http://www.xilinx.com/support/answers/52787.html

Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

View solution in original post

8 Replies
Xilinx Employee
Xilinx Employee
18,027 Views
Registered: ‎10-24-2013

Re: Windows path name length problem

Jump to solution

Hi @rjsefton

 

This is Windows OS limitation.

 

Please check the following AR where some suggestions are given to workaround this.

http://www.xilinx.com/support/answers/52787.html

Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

View solution in original post

Explorer
Explorer
9,446 Views
Registered: ‎11-25-2014

Re: Windows path name length problem

Jump to solution

Quoting from the AR you linked:

 

"The error is most often seen when generating IP cores and archiving, due to the deep hierarchical structure of some of the IP ..."

 

Question: Who or what creates that "deep hierarchical structure" in the IP, and in the Vivado project structure?

 

Answer: Vivado does!

 

This is not an OS problem. It's a Xilinx problem for not designing Vivado to work within the limits of the OS. It should not be the user's responsibility/burden to work around this oversight by Xilinx.

 

I've been doing this stuff for a very long time and I have never encountered the Windows path name length limit under any circumstances with any other EDA tool. I didn't even know the limit existed, and clearly neither did Xilinx. Please don't try to paint this as a Windows problem. It's on you guys to do something about it. Flatten the project hierarchy and the problem is solved.

 

To repeat my original question: Is this even being discussed within Xilinx, or is AR 52787 the official non-solution?

0 Kudos
Moderator
Moderator
9,435 Views
Registered: ‎01-16-2013

Re: Windows path name length problem

Jump to solution

Hi @rjsefton,

 

I haven't come across any of your earlier post regarding same issue.

I took this post further and already started discussion internally. I will keep you updated on progress.

 

Thanks,
Yash

 

Explorer
Explorer
9,419 Views
Registered: ‎11-25-2014

Re: Windows path name length problem

Jump to solution

Thanks, Yash. By the way, I have posted about this before:

 

https://forums.xilinx.com/t5/Design-Tools-Others/Windows-path-name-length-issue-and-the-subst-command/m-p/649255#M8515

 

It's a nasty problem to have to fix after the fact, but something has to be done about it.

 

Bob S.

0 Kudos
Xilinx Employee
Xilinx Employee
9,397 Views
Registered: ‎10-24-2013

Re: Windows path name length problem

Jump to solution

Hi @rjsefton

I meant that the limitation is coming from Windows OS.

 

There are multiple CRs around this and the development team is working on finding real time solution. Till then, please use the workaround give in that AR.

 

Thanks,Vijay
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
Explorer
Explorer
9,361 Views
Registered: ‎11-25-2014

Re: Windows path name length problem

Jump to solution

I received an email nag this morning from Xilinx asking me to mark this thread as resolved. It isn't, but I'll mark it anyway. Keeping my fingers crossed that Xilinx finds a way to fix this in Vivado.

0 Kudos
Xilinx Employee
Xilinx Employee
9,352 Views
Registered: ‎04-17-2013

Re: Windows path name length problem

Jump to solution

There is a new feature to Vivado called "Core Container" which is an option available for IP. This feature is documented in UG896 Design with IP.  Basically it is the zipping up of the IP directory into a binary which Vivado directly access during synthesis and implementation. On Windows using the core container should address many of the path length issues that are hit with the Xilinx IP and directory path lenghts. Since Vivado directly access the binary (i.e. does not extract to a temporary area on disk) the "paths" can be longer than the length supported in Windows.

 

Please give core container a try.

 

Regards,

 

Cyrus

0 Kudos
293 Views
Registered: ‎05-08-2019

Re: Windows path name length problem

Jump to solution

Got the same problem. Solved it with longpathtool.
Please, write if it works for you too.

0 Kudos