RM48L952: Is the new THEIA development environment going to support the RM48 Hercules Class of Microcontrollers?

Anybody else needs to know this?

Hi Kip,

CCS Theia currently does not support Hercules devices. Please use CCS Eclipse. The latest version of CCS Eclipse is CCS 12.7.1.

--
Thanks & regards,
Jagadish.

This seems to be unclear. I use a CCS 12.8.1 from the good old CCS with Hercules support. Now it seems to give a CCS v20 with Hercules and based on the documentation Theia. But in parallel a CCS Theia v1.5 without Hercules. Unclear, what are the next steps of TI.

Thanks

Steffen

CCS Theia 1.x was a parallel series of releases that we did while we are migrating from Eclipse to Theia.  Now that we have completed that migration CCSv20 is our standard CCS release and is based on Theia.

CCSv20 has support for RM48 devices. The support is someone limited in that the software package for RM48 doesn;t have project templates in it so the project wizard will not show any content.  You would need to use the import function.

Regards,

John

I imported into CCS 20.0.0  a project file which was previously built under CCS 12.8.1 with MCU target Hercules RM48L952.  CCS 20.0.0 opens the project but

• All the project settings for cpu, compiler and linker are blank and some are initialized for default configs. 
  • (Big work to re-input all these settings manually).

Does anyone know, if I configure CCS 20.0.0 for RM48L952 with clang compiler, will this actually build?  I need to compile C/C++ software from the following sources:

• 'C' code generated from TI's HAL      code generator for Hercules MCU's (RM48 class)
• 'C' code generated from TI's N2HET code generator for Hercules MCU's  (RM48 class)
• TI's Run-Time-Environment (RTE) for Hercules MCU's (RM48 class)
• TI's custom build process for Hercules Run-Time Support Library, which supports floating point and other AEABI-compliant switches.
• Standard TI/ARM core DSPlib provided for Hercules class MCU's (RM48 class)
• functional safety library code from TI for RM48 class MCUs.

In addition, when I invoked the Clang compiler in CCS 20.0.0 to perform a build, the application performed an automatic migration process on the project.  See included screen grab. 

The Theia IDE looks like it is not functional when importing old projects.  Can someone at TI comment?  It's OK with me if I need to re-initialize about 200 project settings.  I just don't want to do all this if, in the end, the project won't build because CCS Theia for Hercules targets isn't supported "fully" yet -- by "fully" I mean I need to have ANY METHOD to setup all the compiler settings I used for TI LTS series of compilers.  If all the previous code objects CANNOT be successfully generated with CCS/Theia, I should just stop this work and use the old CCC 12.8.1 tool chain built on Eclipse.

Also, I ABSOLUTELY NEED the AEABI interface capabilities of LTS compiler chain included in CCS/Eclipse, since my final software object includes an ABI-compatible binary of  the threadx RTOS, built using ARM FuSa Gold tool chain for embedded targets, version 6.16.2. 

All of the interlinking currently WORKS OK, using the two compiler tools chains, ARM (ARM Clang, ARM FuSA, 6.16.2) and Texas Instruments (CCS 12.8.1 with 20.2.7 LTS compiler tools) to compile the various modules listed above. 

Kip,

I would like to figure out what went on with the import at that should have worked pretty cleanly.  Looping in someone to help with that.

For the Clang support with RM48 software question I will need to leave that to the Hercules team.

Regards,

John

Here's the real-time migration error which occurred when I attempted to build the project.

------------------------------------------------------------------------------------------------------------------------
!TASK: Migrating from source-tool 'Arm Compiler' (com.ti.ccstudio.buildDefinitions.TMS470_20.2.exe.compilerDebug.101266361) ... [Wed Dec 11 17:31:42 EST 2024]

	!CONFIGURATION: 'Debug' (com.ti.ccstudio.buildDefinitions.TMS470.Debug.47038874)

		!TOOL: 'Arm Compiler' (com.ti.ccstudio.buildDefinitions.TMS470_TICLANG_4.0.exe.compilerDebug.1855658165)

			!ERROR: java.io.IOException: Cannot run program "" (in directory "C:\Users\Kip_Leitner\workspace_ccstheia\IslandDER\Debug"): CreateProcess error=87, The parameter is incorrect
				at java.base/java.lang.ProcessBuilder.start(Unknown Source)
				at java.base/java.lang.ProcessBuilder.start(Unknown Source)
				at java.base/java.lang.Runtime.exec(Unknown Source)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.getCanonicalizedToolSettings(ConfigurationInitializer.java:2134)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.migrateBuildOptions(ConfigurationInitializer.java:1659)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.doCopyBuildOptions(ConfigurationInitializer.java:1305)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.copyBuildOptions(ConfigurationInitializer.java:430)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.internalCopyBuildOptions(ConfigurationInitializer.java:1228)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.internalInitializeBuildOptions(ConfigurationInitializer.java:887)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.initializeFromExisting(ConfigurationInitializer.java:286)
				at com.ti.ccs.project.services.ProjectModifier$1.run(ProjectModifier.java:1237)
				at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2315)
				at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2340)
				at com.ti.ccs.project.services.ProjectModifier.modifyCCSProject(ProjectModifier.java:1199)
				at com.ti.ccs.project.services.ProjectModifier.modifyCCSProject(ProjectModifier.java:1157)
				at com.ti.ccs.server.handlers.ProjectPropertiesHandler.cmd_modifyProjectProperties_end(ProjectPropertiesHandler.java:1480)
				at com.ti.ccs.server.handlers.ProjectPropertiesHandler$11.handle(ProjectPropertiesHandler.java:614)
				at com.ti.ccs.server.events.IServerRequestHandler$Impl.handle(IServerRequestHandler.java:34)
				at com.ti.ccs.server.CCSServer$RequestHandlerJob.run(CCSServer.java:175)
				at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
			Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect
				at java.base/java.lang.ProcessImpl.create(Native Method)
				at java.base/java.lang.ProcessImpl.<init>(Unknown Source)
				at java.base/java.lang.ProcessImpl.start(Unknown Source)
				... 20 more
			

!END_TASK: [Wed Dec 11 17:31:42 EST 2024]


------------------------------------------------------------------------------------------------------------------------
!TASK: Migrating from source-tool 'Arm Compiler' (com.ti.ccstudio.buildDefinitions.TMS470_20.2.exe.compilerDebug.7758444) ... [Wed Dec 11 17:31:42 EST 2024]

	!CONFIGURATION: 'Debug' (com.ti.ccstudio.buildDefinitions.TMS470.Debug.47038874)

		!TOOL: 'Arm Compiler' (com.ti.ccstudio.buildDefinitions.TMS470_TICLANG_4.0.exe.compilerDebug.1855658165.2133672699)

			!ERROR: java.io.IOException: Cannot run program "" (in directory "C:\Users\Kip_Leitner\workspace_ccstheia\IslandDER\Debug"): CreateProcess error=87, The parameter is incorrect
				at java.base/java.lang.ProcessBuilder.start(Unknown Source)
				at java.base/java.lang.ProcessBuilder.start(Unknown Source)
				at java.base/java.lang.Runtime.exec(Unknown Source)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.getCanonicalizedToolSettings(ConfigurationInitializer.java:2134)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.migrateBuildOptions(ConfigurationInitializer.java:1659)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.doCopyBuildOptions(ConfigurationInitializer.java:1305)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.doCopyBuildOptions(ConfigurationInitializer.java:1265)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.copyBuildOptions(ConfigurationInitializer.java:444)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.internalCopyBuildOptions(ConfigurationInitializer.java:1228)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.internalInitializeBuildOptions(ConfigurationInitializer.java:887)
				at com.ti.ccs.project.initializer.ConfigurationInitializer.initializeFromExisting(ConfigurationInitializer.java:286)
				at com.ti.ccs.project.services.ProjectModifier$1.run(ProjectModifier.java:1237)
				at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2315)
				at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2340)
				at com.ti.ccs.project.services.ProjectModifier.modifyCCSProject(ProjectModifier.java:1199)
				at com.ti.ccs.project.services.ProjectModifier.modifyCCSProject(ProjectModifier.java:1157)
				at com.ti.ccs.server.handlers.ProjectPropertiesHandler.cmd_modifyProjectProperties_end(ProjectPropertiesHandler.java:1480)
				at com.ti.ccs.server.handlers.ProjectPropertiesHandler$11.handle(ProjectPropertiesHandler.java:614)
				at com.ti.ccs.server.events.IServerRequestHandler$Impl.handle(IServerRequestHandler.java:34)
				at com.ti.ccs.server.CCSServer$RequestHandlerJob.run(CCSServer.java:175)
				at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
			Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect
				at java.base/java.lang.ProcessImpl.create(Native Method)
				at java.base/java.lang.ProcessImpl.<init>(Unknown Source)
				at java.base/java.lang.ProcessImpl.start(Unknown Source)
				... 21 more
			

!END_TASK: [Wed Dec 11 17:31:42 EST 2024]

Hi Kip,

I see you are trying to migrate you project to use the clang compiler. It is typically not as simple as switching the compiler. There is typically some other additional configuration involved.

I'd first like to see if you can build your project using the original compiler. CCS 20 does not come with it but you can obtain from: https://www.ti.com/tool/download/ARM-CGT

Then use the steps in this video to make sure it is discovered by CCS 20: https://www.youtube.com/watch?v=1jkpPGcbxxA&list=PL3NIKJ0FKtw75d_K8G0JBJHB9zIm8_YQL

If you already have the compiler installed on your system, then you don't need to download/install it but use the steps in the video to point CCS 20 to the location of it.

Thanks

ki

@Ki -- I like your idea.  I am going to do it and will report the results here.  Because my project uses a complex link of many binary sub-objects, It will take me a day to configure all the compiler settings under CCS 20 and rebuild everything.  I will let you know the results of this test.  This will be a good stress on the 20 platform. 

I notice already -- support for MISRA in the "advanced settings" seems to be broken.

Missing Features:

• "project" main page is blank, so missing ALL features, but really need . . .
  • Stop on first error

@Ki -- I am able, using CCS 20, to assemble, compile, link, flash and debug my project using the old 20.2.7 LTS compiler.  So that is good.

However, this ticket is about the items I list I need to compile from the message:

--> December 11th, 10:57 p.m.

As you can see, those items include AEABI tags, LTS #PRAGMA statements and other switches from the LTS compiler.  Not sure if any of the HAL code can be easily ported to the TI Arm-Clang compiler.  What do you think about this from my message (?) :

--> December 11th, 10:57 p.m.

Kip Leitner said:

@Ki -- I am able, using CCS 20, to assemble, compile, link, flash and debug my project using the old 20.2.7 LTS compiler.  So that is good.

That is good to hear. The project format still remains (mostly) the same between CCS 12.x and CCS 20 so this is expected.

Kip Leitner said:

As you can see, those items include AEABI tags, LTS #PRAGMA statements and other switches from the LTS compiler.  Not sure if any of the HAL code can be easily ported to the TI Arm-Clang compiler.  What do you think about this from my message (?) :

I'll bring this thread to the attention of the compiler experts.

Thanks

ki

Kip Leitner said:

Not sure if any of the HAL code can be easily ported to the TI Arm-Clang compiler.

I'm pretty sure the information in this forum post is still accurate.

Thanks and regards,

-George

You are welcome to reject a reply I marked resolved.  But before I can reply further, I need to know why you rejected it.

Thanks and regards,

-George

Hi George,

The reason I rejected the answer is because I don't want to accept a "pretty sure" answer.  I need a 100% sure answer. 

Hi Kip,

The HALCoGen generated code, SDL (safety diagnostic library, CSP test cases) are not fully supported by TI-Clang. 

This is the reason we always recommend customer to use TI ARMCL compiler (or TI LTS Compiler) for Hercules controllers. You can find the issues faced in below threads.

(+) LAUNCHXL2-TMS57012: New project development recomendation - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

(+) RM48L952: Is it possible to compile certain TI Source codes on ARM FuSa Compiler and then debug with TI Tool chain ? - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

(+) TMS570LS1224: Halcogen and SafeTI Certification with TI ARM Clang - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

--
Thanks & regards,
Jagadish.