CCS: Error reading repository when checking for updates in CCS 9.3

Hi Chris,

Thanks for reporting this. Interestingly, I only see this when on the TI network. When I am off the TI network, I can't reproduce this. Still under investigation...

Thanks

ki

It is neither fixed nor resolved as of two minutes ago, hence this comment.

A ">" is missing in the end of last line of that xml:

<child location='downloads.ti.com/.../

Maxim, it may be a caching issue on your PC.

Could you try reloading your local cache (Window > Preferences > Install/Update >  Available Software Sites), Select the "Code Composer Studio v9 Updates" site (disable and then re-enable) and select Reload)?

Did that, with no apparent effect:

1. Did as you said, but the "Reload" button remained disabled (grey).

2. On the latest attempt to update, CCS went through the list of sites, and reported that no new updates are available. Note that prior update attempts failed because of the ">" issue..

3. Also, after prior attempts and before writing here, I added the missing ">" manually to the xml file, then attempted an update again. In anticipation that CCS would write over it, I set the file read-only attribute. CCS downloaded and wrote over it, hence it is unlikely to be a cache issue, though that remains inconclusive.

Now I have manually erased all files in "C:\TI\CCS\ccs\eclipse\p2\org.eclipse.equinox.p2.repository\cache" folder. There is another cache folder, "C:\TI\CCS\ccs\eclipse\p2\org.eclipse.equinox.p2.core\cache\binary", but I did not erase anything there, as some of those files are much older, and some are a few days old. After that, CCS has downloaded lots of files into "C:\TI\CCS\ccs\eclipse\p2\org.eclipse.equinox.p2.repository\cache", and then reported that no new updates are available. It did not throw any error, but it did not request CCS restart either, though it did after prior updates.

p.s. The "...7024.xml" file is now correct, with ">" in place where it was missing before.

Maxim Mikhalsky said:

CCS downloaded and wrote over it, hence it is unlikely to be a cache issue, though that remains inconclusive.

What is the date of the file that was downloaded? It should be January 6.