Skip to main content
BJohn.6
Associate II
May 3, 2021
Question

I am using STMCubeIDE. I have tried to move the workspace to a different (physical, not network) drive, but STMCubeIDE apparently cannot handle that. It reports "Unable to access" type problems. Any thoughts?,

  • May 3, 2021
  • 3 replies
  • 3897 views

..

This topic has been closed for replies.

3 replies

_Saurabh Nishad_old
Visitor II
May 3, 2021

Hi @BJohn.6​ it may be because you don't the write access on that drive.

Try right click on the go to properties and general tab untick the Read-only attribute and click apply and ok.

May, be this resolve your issue. Or you can provide more detail about your issue by taking the snapshot of error.

Saurabh

BJohn.6
BJohn.6Author
Associate II
May 3, 2021

This is my personal computer, not an employers. There are no read-only drives. I have tried two different drives, including the D: drive where I am doing the project development (not in the workspace). I have no problem with the actual development, It is just when I close Cube, it complains about not being able to update the workspace, (but not if it is in the C drive mess). I basically want nothing on the C drive, because I don't want to churn the SSD. The Cube complaint is apparently bogus, because I can update the tree manually. In fact, I copied it from the C: drive before I switched to it.

Pavel A.
Super User
May 3, 2021

Try to create a new workspace on D: and import the project into that.

Not sure if moving the .metadata to a different drive is warranted to work.

Of course, ensure that there are no spaces or funny characters in the path.

Paul1
Senior III
May 3, 2021

Does the project have any "absolute paths" to includes, etc?

Change these to relative paths before moving project.

If uncertain, create a new project in new location, and look at its "includes" paths, etc.

(Backup/Zip the working project before doing anything else)

Paul

BJohn.6
BJohn.6Author
Associate II
May 3, 2021

No. It is a simple test build anyway, and as I said before, the builld directory is not inside the repository anyway. I never do that. There is no problem with doing a build, the only problem is just Cube trying to update something in the repository. Personally, I despise the workspace concept, because it seriously complicates archival purposes to have a project split between two areas.

Paul1
Senior III
May 4, 2021
Error while parsing Rich Text Content
BJohn.6
BJohn.6Author
Associate II
May 4, 2021

OK. I have discovered the answer now. The procedure is:

  1. Close and delete the project from Cube (presumably without deleting the content).
  2. Switch the Repository in Cube [File | Switch] (includes possibly creating a new one).
  3. Cube will close and reopen.
  4. Open the project(s).

After this it is all good.