cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
michelcharette
Observer
Observer
1,814 Views
Registered: ‎06-07-2012

Did latest Java update break Xilinx SDK 2016.4?

Jump to solution

Last Friday morning I was using Xilinx SDK 2016.4 without a glitch, then I installed the latest Java update (version 8 update 151).  Now whenever I start a debugging session I get a popup window with the error message:

"

Unepected error while launching program: Error in Resetting Target

Could not stop the processor after reset

"

 

And the SDK Log window contains:

"

11:05:49 INFO : Successfully done setting XSCT server connection channel
11:05:49 INFO : Successfully done setting SDK workspace
11:07:09 ERROR : Unexpected error while launching program.
java.lang.RuntimeException: Error in Resetting Target

Could not stop the processor after reset


at com.xilinx.sdk.targetmanager.internal.TM.doSystemReset(TM.java:988)
at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.runTargetSetup(XilinxAppLaunchConfigurationDelegate.java:469)
at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.debugApplication(XilinxAppLaunchConfigurationDelegate.java:701)
at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.launch(XilinxAppLaunchConfigurationDelegate.java:311)
at com.xilinx.sdk.debug.ui.XilinxAppLaunchDelegateWrapper.launch(XilinxAppLaunchDelegateWrapper.java:31)
11:28:38 ERROR : Unexpected error while launching program.
java.lang.RuntimeException: Error in Resetting Target

Could not stop the processor after reset

"

 

Is is possible that this is due to the Java update?

0 Kudos
1 Solution

Accepted Solutions
michelcharette
Observer
Observer
2,375 Views
Registered: ‎06-07-2012

I'm not sure how I can roll-back the latest Java update.  Instead, I installed 2017.2 and it does work correctly.  

View solution in original post

0 Kudos
2 Replies
syedz
Moderator
Moderator
1,813 Views
Registered: ‎01-16-2013

@michelcharette,

 

Yes, based on the error message I suspect the issue is due to Java update only. Can you try reverting back the java update and confirm on this?

 

--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)?
---------------------------------------------------------------------------------------------
0 Kudos
michelcharette
Observer
Observer
2,376 Views
Registered: ‎06-07-2012

I'm not sure how I can roll-back the latest Java update.  Instead, I installed 2017.2 and it does work correctly.  

View solution in original post

0 Kudos