TMS570LS20216: ARM Cortex-R4f MCUs (160 MHz Micro controller unit TMS570LS)

Hi Stavan Dave,

Apologies for delay in our response.

We started working on your thread now and will provide an update ASAP.

Hi Stavan,

 TI changed the filename of hex utilities from hex470 to armhex in later compiler version.

https://downloads.ti.com/docs/esd/SPNU118N/Content/SPNU118N_HTML/hex_conversion_utility_description.html

Hi Jagadish,

The solution provided by you is working fine. 

Our H/W product is IEC 61508 SIL3 safety compliance and the software we build is also SIL2 safety compliance. Our H/W product is build based on the Safe CPU is TI’s TMS570LS series high performance automotive grade microcontroller (TMS570LS20216-ZWT), integrates the ARM® Cortex-R4F Floating Point CPU and has configurations which can run up to 160 MHz.

And as per my last query, recently we updated our safety software local build environment from TI Arm7 compiler tool version 5.0.4 to version 5.2.9 and CCS version 4.2.5.0005 to version 5.5.0.0, which seems working ok.

 Now we want to update our local build environment, with combination of latest possible version of TI Arm7 compiler (i.e., greater than version 5.2.9) and CCS. A combination which can adapt our current build configuration/environment with no changes in source code and can build our safety software.

Please suggest us which combination of TI Arm7 compiler tool and CCS version we should try for.

Hi Jagadish,
Thanks for your last response.
As per your last response, we tried to compile our product code, still we had some queries and hurdles we are facing and need your support.
    1) By when the TI is planning to obsolete the Arm® code generation tool version 5.2.9.
    2) As per your last reply we tried to compile our safety product code using CCS version 12.0.0.00009 and Arm® code generation tool version 20.2.7 LTS, the error we are getting while importing our project is “This project was created for a device not currently recognized - Cortex R.TMS570LS20216SZWT”.
        a) With CCS version 5.5.0.00077(Processor support – Safety MCUs) + Arm® code generation tool version 5.2.9, our safety code is working fine.
        b) The processor used in our product is TI’s Safe CPU TMS570LS series (TMS570LS20216-ZWT). Can you please help us which processor support we need to select for CCS version 12.0.0.00009.
    3) As described in “coverage_testing_instructions.pdf” from ARM-CQKIT for Arm® code generation tool version 5.2.9, we added “COVFILELIST” in CCS version 5.5.0.00077 IDE and also followed other steps as well. After compiling the project, no coverage files get generated and getting below mentioned error messages; Can you please help us with this:
    BullseyeCoverage 8.13.22 error 15: Cannot find C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9. COVFILE is not set, errno=2. Executable is C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9\bin\armlnk.exe
    BullseyeCoverage 8.13.22 error 15: Cannot find C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9. COVFILE is not set, errno=2. Executable is C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9\bin\armcl.exe

Please reply with your suggestions.

TI has no plans release additional bug fixes for the ARM 5.2.x compiler.  Version 5.2.9 is the last release for that branch.

I have no suggestions for how to address the CCS issues with changing compiler version to 20.2.7.LTS for above issue with "device not recognized". 
I would however recommend using ARM 20.2.7.LTS with a more recent version of CCS 

Regarding coverage data collection, above errors indicate that you have not properly set COVFILELIST. Please send details for how you set COVFILELIST including the actual setting you used.

Stavan Dave said:

“This project was created for a device not currently recognized - Cortex R.TMS570LS20216SZWT”.

This device is supported with current CCS 12.x versions. I was able to create a new project for it in CCS 12.4 with compiler 20.2.7.

Please provide your project so I can try it locally. I really just need the three .*project files in the project folder.

Thanks

ki

Hi Ki,

As you requested, I added .*project files, for the project which i was trying to import. Please help us with your valuable suggestion.

<?xml version="1.0" encoding="UTF-8"?>
<?ccsproject version="1.0"?>

<projectOptions>
<deviceVariant value="Cortex R.TMS570LS20216SZWT"/>
<deviceEndianness value="big (BE32)"/>
<codegenToolVersion value="4.6.1"/>
<isElfFormat value="true"/>
<rts value="libc.a"/>
<defaultAssemblyOnly value="false"/>
</projectOptions>

<?xml version="1.0" encoding="UTF-8"?>
<?eclipse-cdt version="2.0"?>

<cdtproject id="org.eclipse.cdt.managedbuilder.core.managedMake">
<extension id="org.eclipse.cdt.managedbuilder.core.ManagedBuildManager" point="org.eclipse.cdt.core.ScannerInfoProvider"/>
<extension id="com.ti.ccstudio.binaryparser.CoffParser" point="org.eclipse.cdt.core.BinaryParser"/>
<data>
<item id="org.eclipse.cdt.core.pathentry">
<pathentry kind="src" path=""/>
<pathentry kind="out" path=""/>
<pathentry kind="con" path="org.eclipse.cdt.managedbuilder.MANAGED_CONTAINER"/>
<pathentry kind="con" path="com.ti.ccstudio.managedbuild.core.CCS_CONTAINER"/>
</item>
</data>
</cdtproject>

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>safety_inspector</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.genmakebuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.cdt.core.cnature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.managedBuildNature</nature>
		<nature>org.eclipse.cdt.core.ccnature</nature>
		<nature>com.ti.ccstudio.managedbuild.core.ccsNature</nature>
	</natures>
	<linkedResources>
		<link>
			<name>sources</name>
			<type>2</type>
			<locationURI>SVN_ROOT_PATH/tcngw/tcngws/wtb-fw-s/safety_inspector/trunk/sourcecode</locationURI>
		</link>
		<link>
			<name>lib_ext</name>
			<type>2</type>
			<locationURI>SVN_ROOT_PATH/tcngw/tcngws/wtb-fw-s/safety_inspector/trunk/bld/lib/proprietary-tcngws-tms470</locationURI>
		</link>
		<link>
			<name>include_ext</name>
			<type>2</type>
			<locationURI>SVN_ROOT_PATH/tcngw/tcngws/wtb-fw-s/safety_inspector/trunk/bld/include</locationURI>
		</link>
	</linkedResources>
</projectDescription>

Hi GregM,

Below is the steps I performed to add COVFILELIST for CCS version 5.5.0.00077 + code generation tool version 5.2.9; please correct steps mentioned below:

1) Unzip the “bincov” folder into a temporary location.
2) Rename the original compiler installation folder from "bin" to "bin_old".
     --> From: C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9\bin
               To: C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9\bin_old
3) Created a new "bin" folder within compiler installation folder and copy in the executables and *.cov coverage files from the "bincov" folder.
     --> copide "bincov" folder to newly created new folder: C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9\bin
4) Open project in CCS 5.5.0,
     - Open “Project properties”
     - Click on “CSS Build”
     - Click on tab for “Environment”
     - Click on “Add” and add
        Name: COVFILELIST
        Value: C:\ti\CCS5_5_0_00077\ccsv5\tools\compiler\ti-cgt-arm_5.2.9
5) Rebuild the project. Got error as mentioned in previous query.

Also one more question, is TI has any plan by when the branch for code generation tool version 5.2.9 will get obsolete.

COVFILELIST needs to include all *.cov files in a comma separated list. See pdf for example. Above input is not correct

Stavan Dave said:

As you requested, I added .*project files, for the project which i was trying to import. Please help us with your valuable suggestion.

What type of project are you working with? Is this a standard Eclipse managed make project instead of a full CCS project?

Hi Ki,
Type of project we are working with is standard Eclipse managed make project.

Hi GregM

Thanks for your suggestion.

Aso one more question, is TI has any plan by when the branch for code generation tool version 5.2.9 will get obsolete?

TI has no plans release additional bug fixes for the ARM 5.2.x compiler.  Version 5.2.9 is the last release for that branch.