error: cannot find file "./configPkg/linker.cmd"

I am having the same problem - New MSP430 Grace 2.0.1.65 project.  New install CCS Ver 5.3.0.00090.

Hi May may and John,

what directory and OS are you using CCS with/installed CCS to?

Any further details on how you are setting up your project/regarding the error would be helpful.

Best Regards,
Lisa

HI,

just thought I would check for any updates/further information with your enquiry.

Best Regards,
Lisa

Lisa,

I'm having the same error.  I'm trying to build on a 64-bit Windows7 machine.

The file actually exists (configPkg/linker.cmd) but for some reason it was built so that I have neither read nor write access to it.

If I use Windows Explorer to look at the file's properties, I can change my access rights so that the link succeeds.

The frustrating part is that every time I rebuild the project, I have to do the same thing (i.e., let the build fail, manually fix access for the file, then 'rebuild'), because the file is apparently built as part of the build process.

What builds the file, and how can I modify that so the built file is readable by the linker?

Thanks,

Frank

HI Frank,

any permissions settings will be coming from windows/your user account and not ccs.    The program files directory for example can have odd permissions issues.

I would double check these things and hopefully that will allow you to find a path to remove the manual steps you are taking.

Best Regards,

Lisa

It was the build process that created the file - and yet it created it such that it can't subsequently read it?

I've heard of 'read-only', but 'write-only' is useless!

The file is not located in "Program Files".

It is located at C:\zTop\ti\karl\pa_fd_da8xx_100713\pa\f\s19\i4\evmda830\Release\linker.cmd.

I've examined every directory in that path and given myself full access in each directory - to no avail.

Hi Frank,

I am going to see if I can reproduce this as this is something that I have not seen.  Is this a bios generated linker.cmd?  Can you possibly send a test case or steps to see if we are able to see the same permissions behaviour.   We don't encourage anyone to modify the built in or bios generated linker.cmd files, however you should not need to modifiy permissions to work around build errors.  There I fully agree.

Best Regards,

Lisa

Hi Frank,

just thought I would check whether there was any update/further information with your enquiry.

Best Regards,
Lisa

No, it's still broken.

There's no way I can send the items to you that I would need to in order for you to recreate the problem.

Is there someone in Dallas that you could transfer the problem to?

I'm in the Forest Lane site.

Frank

Hi Frank,

no worries, I understand you will be connecting with a team member locally.

All the best.

Lisa

Lisa - I hope you don't mind me jumping into this thread. It is the only one remotely similar to the problem I am encountering. 

This problem starts with a generic code development methodology that I follow. I will make a project template with minimal functionality. Get it to compile, build, and run properly. Then I copy that project to a new project file, where I add more incremental capability. I leave that project frozen in time when it is stable and copy the stable project into yet another new project. And so on. 

I would like to take this sort of approach with CCS. Neither Copy/Paste nor Export/import of a project folder branch accomplish this because neither has a way around the project name clash. I need some way to rename the newest project to a slightly different name - for example project03 might succeed project02.  I have tried a Copy/Rename/Paste and then going in brute force to rectify all references to the project name. It almost works. It fails to build because the folder configPkg, under Debug in the project folder hierarchy, keeps vanishing. So it appears that I need to make a correction to whatever mechanism creates the configPkg folder during a build process.  

Do you know where I should be looking?

Better yet, is there is TI-sanctioned approach to achieving my goal that would avoid the need for manual correction of project name occurrences?

Thanks, 

Tom

Hi TOm,

do you need to use one workspace?  A good option might be importing the project to a new workspace, modift, import to a different workspace, modify ... etc etc.  This would be the easiest way.

Best Regards,
Lisa