The "Kernel Unit Tests" build is failing here due to an unrelated problem, which I've raised as #1274.

I have opened PR #1275 to fix the build issue, If we can get that approved, we can check it fixes the build, then merge it to get main green before proceeding with this one. Thanks!

Instead of keeping the symboic links, I was thinking of using Eclipse's linked folder and resource filters to filter the files in those folders. Please try the following patch and let me know what you think about it - 0001-Update-CORTEX_R4_RM48_TMS570_CCS5-project.patch.

Note that I used CCS v12.

Instead of keeping the symboic links, I was thinking of using Eclipse's linked folder and resource filters ...

Ah okay. I've updated the PR to use this approach. There were a few problems with your patch that I've fixed up:

• The patch imported the FreeRTOS folder as "FreeRTOS-Kernel", but that path wasn't updated in the include paths for three of the four build configurations. So that broke the build for the TMS570 target I was testing. I restored the resource link to the previous name of just "FreeRTOS", since it means fewer changes and the directory also includes some non-kernel stuff nested under as well.
• The filtering included all the Demo/Common/Minimal/*.c files, which caused quite a few compilation errors for me. I updated the filter to just include the files which were copied by the previous script.
• Likewise, there was no filtering on the kernel *.c files, so I added filters for just the files needed.
• The patch didn't delete the old batch file, which is no longer needed.

Testing note: I found that Eclipse retains some state for linked resources even after the resource is removed from the .project file and the CCS project is closed and reopened. In my case, I had to manually remove the FreeRTOS-Kernel link after it was renamed to just FreeRTOS. Perhaps a restart of CCS would have fixed it; I didn't try that.

Please try the following patch and let me know what you think about it …

After playing around with it, I think this approach relies on a lot of IDE magic and obscure settings screens. So I would probably find the symlinks easier to grok coming at the project fresh. But it's your project, so happy to go with your recommendation.

Note that I used CCS v12.

I'm also using CCS 12. Perhaps we should remove the "_CCS5" suffix from the demo project and path name? I don't think preserving compatibility with an old, unsupported IDE version should be a goal for this demo. I'd suggest doing that as a separate ticket+PR however, so we don't delay this work with further changes.

I also tested this on real TMS570 hardware today (using the symlinked version), and it worked fine.

Updates complete - please re-review when you get a chance, thanks @aggarg @jasonpcarroll.

There were a few problems with your patch that I've fixed up:

Thank you for addressing these problems. I guess I made these changes for only one target and did not realize that there were 3 more.

When I built the project with the current changes, I needed to update the "Runtime support library" to automatic so that CSS builds the library when the project is used first time after installation - 0001-Set-library-management-to-autometic.patch.

Please take a look at this and let me know what you think. Thank you for your contribution!

@mryall-mawson Did you get a chance to look at the change above?

That sounds like a handy fix. I had to work out how to do that manually with mklib, which was quite a pain.

Unfortunately I haven’t had time to review or test it yet. I’m at a conference next week as well, so it may be two weeks until I get a chance.

We could potentially split this into a separate issue and PR if you want?

Thank you for confirming. Lets do it this way. And thank you for your contribution!