AM2634: SYSCONFIG Manual Output Mode Breaks 'Build Project'

Kier

Part Number: AM2634
Other Parts Discussed in Thread: SYSCONFIG, CCSTUDIO

Tool/software:

Hello,

I'm using CCSTUDIO 12.7.1. When I change the location of the SYSCONFIG output to a directory of my choice, the build can fail.

Here's the default 'automatic' location:

I change it to a another location:

A 'Clean Project' followed by a 'Build Project', builds just fine.

However, the usual workflow is to edit a file then then hit 'Build Project'. In this case, several redefined errors are reported in the linker script:

A quick search reveals there is only one definition:

This should be reproducible with the SDK example empty project.

Please can you allow SYSCONFIG manual mode and 'Build Project' to coexist.

over 1 year ago

0 Sudeshna Chaudhuri over 1 year ago

TI__Intellectual 830 points

Hello Kier,

I tried replicating your steps at my end on the same ccs version and latest sdk installer but wasn't able to reproduce the issue on both release and debug mode. For me, the build project went through successfully.

I'm not sure why you see that issue, but can you check/ show the content of the Release/syscfg folder? I want to know where else is the linker.cmd. Because, this usually happens when projects have linker.cmd other than the one generated from syscfg.

0 Kier over 1 year ago in reply to Sudeshna Chaudhuri

Mastermind 9110 points

Hi Sudeshna,

Thanks for looking into this. I attach my project so that we are using exactly the same files. Can you try with my project please?

syscfg_manual_ws.zip

Here's a video of the steps I take to produce the error:

0 Sudeshna Chaudhuri over 1 year ago in reply to Kier

TI__Intellectual 830 points

Hello Kier,

Thanks for sending the workspace.
I got issue related to the path of some header files but none related to the linker. After fixing those, I could run it properly.

Also, this is the variable that I'm using. Can you please try the zip and let me know?

6082.syscfg_manual_ws.zip

If this works, then it may have got something to do with the variable type.

0 Kier over 1 year ago in reply to Sudeshna Chaudhuri

Mastermind 9110 points

Thank you. I get the same error with your project and workspace.

Please can you confirm you are following this sequence to reproduce the error:

- Right click 'empty_am263x-cc_r5fss0-0_freertos_ti-arm-clang' and 'Clean Project'.

- Right click 'empty_am263x-cc_r5fss0-0_freertos_ti-arm-clang' and 'Build Project'. Build should be OK.

- Open 'empty.c'.

- Edit 'empty.c'.

- Save ' empty.c'.

- Right click 'empty_am263x-cc_r5fss0-0_freertos_ti-arm-clang' and 'Build Project'. Build should now have errors.

0 Kier over 1 year ago in reply to Sudeshna Chaudhuri

Mastermind 9110 points

I can see why the problem happens in the build logs.

In the OK scenario: Clean Project -> Build Project, the linker invocation points to the linker script only.

In the NG scenario: Edit File -> Build Project, the linker invocation points to the linker script but incorrectly includes 'linker.cmd' with the object file list. This is why there is a redefined error:

0 Sudeshna Chaudhuri over 1 year ago in reply to Kier

TI__Intellectual 830 points

Yes, I could now see that error scenario. I was always cleaning before building and that's why it was working.

This is a good observation and this doesn't happen with automatic mode. I'll check this issue with the concerned team and get back.

0 Kier over 1 year ago in reply to Sudeshna Chaudhuri

Mastermind 9110 points

How's progress please? This problem is a pain.

0 Baltasar Belyavsky over 1 year ago in reply to Kier

TI__Genius 9345 points

Hi Kier,

Sorry for the delay.

Normally, intermediate build artifacts are generated inside the build-directory (e.g. <project>/Debug/), and that is how CCS is able to tell apart these generated artifacts from user source code. Since you are redirecting your intermediate build artifacts to the root of the project, CCS mistakes them for user source code during subsequent builds. To get around this issue, you need to exclude the <project>/syscfg/ folder from build - right-click on that folder, and select Exclude from Build.

Baltasar

0 Kier over 1 year ago in reply to Baltasar Belyavsky

Mastermind 9110 points

Hi Baltasar,

Thank you very much for the hint. I took this a step further and only excluded linker.cmd from the build and this seems to work just as well. I'm reluctant to Exclude from build the entire syscfg directory because that is misleading for CCS Eclipse user. It makes it appear that they aren't part of the project which is untrue.

The cause seems to be that linker.cmd is treated as an object file to be linked in some circumstances, as per my screenshot above. Excluding just that file fixes it. This shows that the source code (*.c/*.h) generated by sysconfig is generally handled just fine by CCS, with the exception is the linker.cmd file.

This seems to be a problem that should be fixed in CCS when using manual generation mode.