This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Cannot (Re)build System Project After Assigning Project To Core : Nothing To Be Done

Other Parts Discussed in Thread: MCU-PLUS-SDK-AM263X

Hello,

I think this is a CCS problem rather than an SDK problem.

I'm using MCU-PLUS-SDK-AM263X, CCS 12.1 and imported the following example: C:\ti\mcu_plus_sdk_am263x_08_05_00_24\examples\drivers\ipc\ipc_notify_echo\am263x-cc\system_freertos_nortos

I can build and rebuild at will until I assign the projects to the core in the System Settings:

Rebuild results in "Nothing to be done".

Clean does nothing also.

If I remove the assignment with the 'Remove' button everything works as it should.

  • Hi Kier,

    What did you set for the "Build Configuration"? If you set it for <match>, try using <active> instead:

    Thanks

    ki

  • Thanks Ki.

    There's no difference in behaviour when using Active. If any single core has an associated .out file, the System Project Clean/Rebuild does not work.

    The example cited should be enough to replicate but I attach my project in case it is a local issue.

    ipc_notify_echo_am263x-cc_system_freertos_nortos.zip

  • I imported the projects from my SDK install and I can reproduce the issue.

    The system project is interesting (to me). Despite the Systems Settings view not showing any project configuration, The Source view has the information of the four projects and can build them. Then want you try to manually associate a core to a particular project, it causes a conflict which causes the build to fail.

    Go to the Source view and clear out everything between the <system></system> tags. Then try manually associating the project to the core again in the Systems Settings view. Then try building the system project.

  • Ah. Yes the clear out fixes the problem. Thank you very much!

  • Glad to hear it worked.

    This functionality that we ran in to is not clearly documented. We'll need to update it.