CCSv5.3 changing target controller

Patrick56061

Other Parts Discussed in Thread: MSP430F5438, MSP430F5438A

Hello,

I've got a new problem with CCSv5.3. If I change the target controller for my project and than change back to the old controller the project can't compile because of "unresolved symbols".

The source code remain the same. If I delete the project and workspace files of eclipse/ccs and create a new project everything's ok till I change and change back the controller (e.g. MSP430F5438 <-> MSP430F5438A).

The only unusual behaviour I found is that the *.cmd files in the "project explorer" are greyed out.

I need to change the controller because loading the same firmware to different hardware settings.

over 13 years ago

0 Lisa TI over 13 years ago

TI__Guru*** 130875 points

Hi Patrick,

I am going to try and reproduce this and will get back to you.

Best Regards,
Lisa

0 Lisa TI over 13 years ago in reply to Lisa TI

TI__Guru*** 130875 points

Hi Patrick,

I will need a few details as I was not able to reproduce this. I did the following in v5.3

- pulled in a F5438 BIOS example. I built this and had no issues

- I switched the target in project ->properties->general and clicked ok. It built no problems.

It is normal and expected a new .cfg file is needed as these are two different targets. I saw after switching targets I had an active .cfg and the old one for the F5438 was greyed out. CCS had done this automatically for me. THis is the expected behaviour.

Does this help explain?

Best Regards,
Lisa

0 Patrick56061 over 13 years ago in reply to Lisa TI

Prodigy 220 points

Yes that's right. The first time I change to a new target everthing works fine and I've get the same behaviour.

Please try to change back to the first controller (I think the F5438 in your example) after this both files are greyed out.

Where do you see the *.cfg file? I had only seen the *.cmd files in the "Projekt Explorer".

regards

0 Lisa TI over 13 years ago in reply to Patrick56061

TI__Guru*** 130875 points

Hi Patrick,

ok, I see this as well and did a non bios project this time ...

The work around appears to be - right click on the .cmd file you need, select properties and in the build tab there is an exclude from build which should still be selected. You can deselect this and then should be able to build.

I am going to try and see if this is something you should be able to do/what implications (if any there might be) I will post further feedback when I can.

Best Regards,

Lisa

0 Lisa TI over 13 years ago in reply to Lisa TI

TI__Guru*** 130875 points

Hi Patrick,

I have filed this as a bug. Sorry for any inconvenience. I hope the work around manually reincluding the files will be good in your case.

The bug ID is SDSCM00045953 and it can be externally tracked here

https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&username=readonly&password=readonly

Best Regards,
Lisa

0 Patrick56061 over 13 years ago in reply to Lisa TI

Prodigy 220 points

Thank you for your help.

I also make a downgrade to CCSv5.2 so I can't test your work around.

best regards

patrick

Code Composer Studio™︎

Code Composer Studio forum

CCSv5.3 changing target controller