CCS/TMS320F28377D: powerSUITE projects not displaying CFG pages

Manish,

I tried this with CCS 7.1 and there are a few things going on here.

In CCS 7.1 a change was made to open all RTSC configuration files in the text editor by default. You can still manually tell it to open in the graphical editor by right-clicking on the file and selecting Open With -> XGCONF, mentioned here.

Having said that, when I tried to open the main.cfg in PowerSuite projects using XGCONF I got an error related to xdctools path. I suspect that the config file specifically needs a 3.31.xx version of XDCtools because once I had CCS discover a XDCtools v3.3.1 (in my case it was 3.31.02.38) the config file opened up fine with XGCONF.

There is also another known issue related to config files and the editor. If a .cfg file is opened with XGCONF, and XGCONF editor is the active view when CCS is closed, then when CCS is restarted the view will show an INVALID_CODEGEN_LOCATION error. Workarounds are to either switch to a different file in the editor before closing CCS, or after CCS is restarted close and reopen the .cfg file. This issue is being tracked in XDCTOOLS-150.

Let me know if this helps explain and gets things going for you.

Aarti,

Thanks for your quick reply,

This small little change actually destroys our powerSUITE infrastructure as-is, but at least i am able to open it...

Thanks for updating me with the INVALID_CODEGEN_ERROR issue, i had seen this starting to happen but because opening and closing resolved it did not worry about it too much, but it would definitely help to get it fixed from a user perspective.

However i am not sure about the XDC tool dependency, the only dependency we have is that it should be version 3.31 or later ,

I just changed the XDC version to 3.50 in the CCS for this project and it works still... so i am unsure about your reported error of XDC tool dependency.. is there some way you could re-verify your report of this issue?

Manish Bhardwaj said:

I just changed the XDC version to 3.50 in the CCS for this project and it works still... so i am unsure about your reported error of XDC tool dependency.. is there some way you could re-verify your report of this issue?

Manish,

In CCS 7.1.0.0015 when I import ILPFC into a new workspace, it defaults to using XDCtools version 3.32.1.22 (if an earlier version of XDCtools like 3.31.xx is not installed). Then I get this error when I open main.cfg.

If I set XDCtools to 3.50.1.12, the error goes away and the file opens fine.

Maybe there is an issue with that specific version of XDCtools. Or if you do not see the same issue it could be that something messed up in my environment ( I have been importing the project many times, in some cases without copying to workspace so perhaps something inadvertently got modified in the example project itself).

The odd thing is that if I do the same procedure with CCS 7.0.0 with same version of XDCtools 3.32.1.22, I don't see the error when opening the file.

Aarti,

Thanks for checking this on your end,

Behavior is definitely odd, but i am glad changing to the latest XDC tool at least works, so we have a work-around.

I will file this thread as something to be aware of when checking newer releases..

regards
Manish