CCS: Resource Explorer on CCS - version 8.3.1.00004

Hello Saleh.

We have made several updates to Resource Explorer (both on client and server side) so it could be that this is the issue. Can you first try the suggestion from the troubleshooting guide regarding clearing the cache?

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_troubleshooting.html#clear-the-resource-explorer-cache

If that does not help, can you provide the log in: .\ti\tirex-localserver-3.7.0\.logs

Also, do you have many packages installed?

Thanks

ki

Hi Ki,

Really appreciate the reply. I have tried both options under 9.5

Resource Explorer: deletion of folder tirex-localserver-3.7.0

under 9.5.1.3, and cleared the cache under 9.5.1.4 ...

That didn't resolve the problem. Actually have tried that

few times to no avail.

Looks like the .log file you requested is a bit long.

I'm attaching a copy. I hope that would be ok. If not then

I'll try to do cut-&-paste here... Would rather not to since it is

quite long but let me know.

Many thanks,

Saleh

tirex-2020-11-18.log

Saleh,

I can reproduce the issue on one of my PCs while the other works. Do you have a lot (i mean like at least 10, but more like 20+) of packages installed? The PC with the issue has many packages installed and I think that may be contributing to the issue.

Hi Ki,

Thanks for checking and your help.

Yes, looks like number of packages @  /cygdrive/c/ti
is large.

Not quite sure though which would be needed and which would

need to go. Looks like a number of those packages are from

a couple years ago.

-Saleh

More recent versions of CCS can better handle the large number of packages but I assume you need to stay with this older version.

If you can try uninstalling some of the packages in the same directory that are no longer needed, that would help. The package size also has an impact.

Not quite sure that I really have to stick with this old

version. I mean probably depends on the software

packages etc...  We have software that got deleveloped

under this old version but I assume would work under

any subsequent newer version of CCS, no?

I suppose I could install a newer version under

a different workspace? Would that interfere with any

of the old version components, or you think would be

better to just delete the old version and its associated

components in order to get the new version working

properly?

In regard to packages I might move all those dated

2018 to a temp folder under C:/ti and see what

happens... Do you maybe recommend doing that?

-Saleh

Saleh Elmohamed said:

  We have software that got deleveloped

under this old version but I assume would work under

any subsequent newer version of CCS, no?

Usually the key things are to make sure the same version of the build tools (compiler) and dependent SW packages (TI-RTOS, XDCtools, SDK, etc) are used with the newer version of CCS. This is usually enough though it really depends on how strict your company is about these things

Saleh Elmohamed said:

I suppose I could install a newer version under

a different workspace? Would that interfere with any

of the old version components, or you think would be

better to just delete the old version and its associated

components in order to get the new version working

properly?

You can have multiple versions of CCS installed (and run) without issue. Just make sure they are installed in different directories and use completely different workspace folders. They can both use the various software packages installed in C:/ti.

Saleh Elmohamed said:

In regard to packages I might move all those dated

2018 to a temp folder under C:/ti and see what

happens... Do you maybe recommend doing that?

I believe Resource Explorer will look inside subfolders of C:/ti. Hence if you want to back things up to a location where Resource Explorer will not look in, it may need to be outside the C:/ti folder completely. 

Moved all of those dated 2018 to ti-archive-packages folder

outside c:/ti

Looks like now RE uploads and appears on CCS. As updates get

uploaded and size starts to increase that probably would create a similar

problem. I guess at some point we really would need to get the most

recent CCS version in order to totally avoid this package-size problem.

We probably would do that soon so that we don't keep running into

the same problem again and again.

I really appreciate your thoughts and help on this. Quite likely

would have more questions once we get ready to get the new CCS

version. Again, many many thanks for your help.

--Saleh

Looks like most of our code will not build. Probably

due to moving a big chunk of those old packages outside the

c:/ti folder. Maybe time for a new version of CCS that

hopefully would help rebuild this.

Updating the current set of packages with more packages

would likely just take us back to the previous same RE problem.

--Saleh

Hi Ki,

Thanks for the suggestion. We will go ahead and install the

new version. Hope that goes well. Also hope you don't mind

us asking questions in case we get stuck and can't resolve

an issue(s) arising around the newer CCS version.

Again, really appreciate your guidance and assistance on

this matter. Many thanks.

Best,

Saleh

Saleh Elmohamed said:

Also hope you don't mind

us asking questions in case we get stuck and can't resolve

an issue(s) arising around the newer CCS version.

Yes of course. Feel free to post any questions you have on this forum. I suggest starting a new thread for each new unrelated topic.

Thanks and good luck!

ki