CCSTUDIO: CCS10.4 Can't launch workspace

Hi,

What device are you using CCS on?

Hello,

Do you mean what OS I am using ?

If so, I use windows 10 with 64bit.

BR,

No, I meant what is the TI device which you connect CCS to.

I did not connect any device, because I just want to build project.

I understand you don't connect to any device at the moment. But what TI device your CCS project is built for? I need this information to route your query to the right team to provide support.

Hello,

 But what TI device your CCS project is built for? I need this information to route your query to the right team to provide support.

I'm not sure why you need device information of build.
Because, as I said, even though I deleted directory, I continue to see this error when I point this deleted directory.
So, I believe that this issue is related to CCS itself or eclipse.

BR,

As I mentioned,  I need to know the part number to route your query to the right team to provide support. Not every team or engineer in TI uses CCS.

At first, I will try to build PGA970.

Thanks. I am routing your query to the team supporting PGA970 device.

Hello Machida-san,

  Looks like you were routed to the High Speed Amplifier group. I am unsure why this is as well, I am routing you to our CCS/complier group. They will help you with this problem shorty. Sorry about the delay in support on your issue. 

Thank you,
Sima

Machida-san

Ryuuichi machida said:

* Can't launch specific workspace. And continue to see following error even though I deleted directory.

This is unusual. You would get that error when that workspace is in use. Or specifically if the <WORKSPACE FOLDER>\.metadata\.lock file is in use by a running instance of CCS. 

I don't know how the .lock file would be "locked" if the file does not exist. 

Are you able to specify another workspace location?

Thank you

ki

Hello Ki

>You would get that error when that workspace is in use. Or specifically if the <WORKSPACE FOLDER>\.metadata\.lock file is in use by a running instance of CCS.

Yes, I also have same understanding. I saw workaround such kind of this issue, just I remove .lock file from directory. So in my case, I removed whole directory which is included .lock file. Therefore, I thought I do not have this issue after that...

> Are you able to specify another workspace location?
Current workaround, as you said, I use another workspace. But directory name which have issue is default name, so I thought I would like to fix this issue for the feature.

BR,

Ryuuichi machida said:

So in my case, I removed whole directory which is included .lock file. Therefore, I thought I do not have this issue after that...

Yes that is my expectation also. I'm quite confused that didn't work. Did you try rebooting your PC?