This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS: CCS Update Error: unable to find valid certification path to requested target

Guru 329335 points

Replies: 0

Views: 2053

Tool/software: Code Composer Studio

There have been several instances of failures when attempting to check for available CCS updates via the CCS update manager.

The error messages looks similar to the one below:

Unable to read repository at PKIX path building failed: unable to find valid certification path to requested target

This issue is under investigation, but unfortunately there is no solution as of now. The root cause has yet to be determined and investigations are impeded due to the fact that we are unable to reproduce the issue. It seems likely specific to the user's environment - likely security software and network security settings.

The issue appears to occur mostly with CCSv8+ and it has been reported by several people that the issue does not manifest in older versions of CCS (v6.x, v7.x). This is still being confirmed.

The issue does not seem to impact all update sites, just a select few. However, the impacted sites can vary depending on the user. Some people report issues issues with the compiler sites, while others report issues with DVT sites

One user felt it was a certificate issue and successfully worked around it. However, this workaround did not apply to everyone.

As for other workarounds, if the issue is with the compiler updates, you can bypass the CCS update manager and do a manual download and installation.

As for other updates, there is no proven workaround at the time. You can remove the offending sites form the update check via 'Help -> Install New Software', then pressing the 'Manage' button to open the list of update sites. From there, you can pick the sites you wish to disable via the update check.

We are very sorry for the inconvenience. Once we have more information (and a solution), we will update this thread.

UPDATE: One user was able to resolve his issue by adjusting his Eclipse proxy settings:




Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

Having CCS problems? Check out the CCS Troubleshooting Guide

Looking for CCS Training/Documentation? Check out the CCS Resources page

Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ