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: 
Adventurer
Adventurer
2,046 Views
Registered: ‎11-06-2017

Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

Dear All, 

Anyone does know why does the "Abnormal program termination (11)" occur during routing phase 15 (Leaf Clock Prog Delay Opt) of Vivado 2016.3 running on Linux 64 bit LTE? 

The vivado does not show any messages or warnings related to this fault and is crashed! Implementation process aborts and fails without any message reports. I read about the Abnormal program termination (11) but all reports are taken place in other conditions. 

I cannot provide you the design file but any log file you need I can provide you. Could anyone please help me what is the reason of this strange abortion of Vivado? Since my design had already generated bitstream without any problem! I have just added some PL parts working with a new Pl fabrication Clock ( generated by PS ) and now this fail happens! 

Regards,
Farnam

0 Kudos
1 Solution

Accepted Solutions
Moderator
Moderator
3,378 Views
Registered: ‎01-16-2013

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

@fkhalili,

 

Is it possible for you to test the same in latest Vivado 2017.3 release?

 

Can you please provide:

1. Vivado.log

2. crash log files.  Check this AR to know the crash log files: https://www.xilinx.com/support/answers/55854.html

3. Can you please run the following TCL command from Vivado TCL console and share the generated output file (system_info.txt)?

  • report_environment -file sytem_info.txt

After running the command just type “pwd” this will show you the path where the system_info.txt file is generated. You can browse to that path and find the file.

 

--Syed

---------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.

Did you check our new quick reference timing closure guide (UG1292)?
---------------------------------------------------------------------------------------------
8 Replies
Adventurer
Adventurer
2,042 Views
Registered: ‎11-06-2017

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution
I forgot to add that the phase 4 of routing ( global iteration ) would last about 2 hours starting with about 18K nodes with overlaps in 6 sub-phases (i.e. phase 4.1 to phase 4.6) .
0 Kudos
Moderator
Moderator
2,003 Views
Registered: ‎03-16-2017

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

Hi @fkhalili,

 

1. Provide Vivado.log from your project directory. 

2. Install Vivado 2017.3 and try to run this project with it, it may possible that this crash has been resolved in this latest version.

3.  Run time of global iteration phase is high and node overlaps value is 18k due to these multiple reasons:

          Factors which determines node overlap values are

               1. Routing Congestion in your design

               2. Proper Floor planning of your design

               3.  Clock planning/networking

  • Node overlaps means that you have multiple nets fighting for the same routing resource. If that number is high, this indicates some overall congestion problem, and there may be further clues in the Placer log.  If you have the placed checkpoint, you can view the congestion map (estimated based on placement) from Window -> Metrics -> Vertical/Horizontal routing congestion. That may indicate which regions are giving problems and it may help develop a floorplan.
  • The router provides helpful messages when it struggles to meet timing goals due to congestion or excessive hold violation fixing. The router commonly exhibits these symptoms when it struggles: one of it is – Large number of overlaps reported, in the hundreds or thousands.
  • Make proper floorplannig on your design to reduce the values of number of nodes with overlaps.

 

Regards,

hemangd

Regards,
hemangd

Don't forget to give kudos and mark it as accepted solution if your issue gets resolved.
Moderator
Moderator
3,379 Views
Registered: ‎01-16-2013

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

@fkhalili,

 

Is it possible for you to test the same in latest Vivado 2017.3 release?

 

Can you please provide:

1. Vivado.log

2. crash log files.  Check this AR to know the crash log files: https://www.xilinx.com/support/answers/55854.html

3. Can you please run the following TCL command from Vivado TCL console and share the generated output file (system_info.txt)?

  • report_environment -file sytem_info.txt

After running the command just type “pwd” this will show you the path where the system_info.txt file is generated. You can browse to that path and find the file.

 

--Syed

---------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.

Did you check our new quick reference timing closure guide (UG1292)?
---------------------------------------------------------------------------------------------
Adventurer
Adventurer
1,983 Views
Registered: ‎11-06-2017

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

@syedz @hemangd

Dears,

The problem has been solved! There were some syntax error inside one of the IPs which were invisible from eye of the top the vivado! (It would be better if the tool could also indicate and notify syntax errors of the codes inside the IPs! ) 

Thank you. 


0 Kudos
Moderator
Moderator
1,969 Views
Registered: ‎01-16-2013

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

@fkhalili,

 

Can you please share more detail here? Syntax error in Xilinx IP or Custom IP? 

I dont think it will be Xilinx IP. Can you please share the snapshots and the syntax error which you have resolved?

 

--Syed

---------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.

Did you check our new quick reference timing closure guide (UG1292)?
---------------------------------------------------------------------------------------------
Adventurer
Adventurer
1,956 Views
Registered: ‎11-06-2017

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

Hi @syedz,

Of course one of our Custom IP. Please see the line below. 

SIGNAL Status : STD_LOGIC_VECTOR (7 DOWNTO 0); �

The syntax error was appeared due to the weird symbol (i.e.  ) which I do not why is there! 

Thank you.

0 Kudos
Moderator
Moderator
1,953 Views
Registered: ‎01-16-2013

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

@fkhalili,

 

You must have copied that line from pdf which will have such invisible characters, 

It is not recommended to copy text from pdf file for RTL file in Vivado or ISE.

 

--Syed

---------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.

Did you check our new quick reference timing closure guide (UG1292)?
---------------------------------------------------------------------------------------------
Adventurer
Adventurer
1,410 Views
Registered: ‎11-06-2017

Re: Vivado 2016.3 Linux 64 bit 14 Abnormal program termination (11)

Jump to solution

Hi @syedz

After removing the syntax errors, the problem seemed to be fixed! but now, I have modified some part of my design and tried to regenerate output product files and re-wrapped the top module. Currently, the same abnormal termination appears at the same routing phase (i.e. phase 15 clock leaf ... ). This issue seems to be a random issue since sometimes happens and sometimes not! this has made me confused since I cannot find the source of this problem. If you want I can provide you the log files all you needed. 

Thank you, 
Farnam

0 Kudos