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: 
Participant maharjanmilan
Participant
8,080 Views
Registered: ‎07-11-2009

ERROR:Xst:2369 - Empty project file "C:\drivef\driver_top\driver_top.prj"

Hi,

      I'm using xilinx ISe 10.1 . I got some hdl netlists generated from system generator and instantiated in xilinx ISE top level module. As I tried to synthesize the code I'm receiving the error,

ERROR:Xst:2369 - Empty project file "C:\drivef\driver_top\driver_top.prj"

   I used to get this error previously also and I already posted this in xilinx forum also. As per the repsonse I got from the forum, I used to start again from scratch and synthesize it. It used to do the trick previously but it's not helping anymore. Can anyone help me figure out this problem?

I've attached the synthesis report along  this mail.

Milan

0 Kudos
3 Replies
Visitor pozzisa
Visitor
7,536 Views
Registered: ‎05-19-2010

Re: ERROR:Xst:2369 - Empty project file "C:\drivef\driver_top\driver_top.prj"

I have been getting this error at random, for no apparent reason, when I'm compiling my 11.2 Xilinx projects as well. I've found if I quit Xilinx and re-open it, the project will compile. Also sometimes, if I shutdown and reboot the computer, Xilinx compiles without giving this error.

0 Kudos
Scholar embedded
Scholar
5,556 Views
Registered: ‎06-09-2011

Re: ERROR:Xst:2369 - Empty project file "C:\drivef\driver_top\driver_top.prj"

Hi, I could workaround the issue just by closing the ISE and reopening it. I had this problem in ISE12.4 Thanks to pozzisa.
0 Kudos
Scholar embedded
Scholar
5,555 Views
Registered: ‎06-09-2011

Re: ERROR:Xst:2369 - Empty project file "C:\drivef\driver_top\driver_top.prj"

Hi, I could workaround the issue just by closing the ISE and reopening it. I had this problem in ISE12.4
0 Kudos