CCS/TMS570LS0232: Some questions about TMS570LS0232

Hello Xinyu,

Xinyu Wang said:

1. If I set some ESM Group1 to interrupt and some errors of Group1 came out, would selftest find these errors?

I'm afraid I do not understand this question. The items included in Group1 are from several different modules and there are multiple ways that a self-test can be achieved. In at least one of these cases, the ESM channel is actually the result of the self test (see ESM group 1 channel 31). In all other cases that I see, the Group1 ESM channels are assigned to faults. In most of these cases you can use SW to insert an error and see the result. In these cases (Fault injection), not only is the fault detection method exercised but also the error notification path so that the ESM flag will also be set. If the associated interrupt is enabled, you will recieve a Group1 error interrupt in response.

Xinyu Wang said:

2. If I configured TMS570LS0232 by HALCoGen, would selftest functions auto run periodically? Or I should design selftest task in main.c?

Halcogen creates drivers only. The main() function is empty. You would need to fill in main according to your application specific needs including any needed periodic testing.

Xinyu Wang said:

3. If I need to consider safety functions on HALCoGen, should I buy SAFETI-HALCOGEN-CSP?

There is no requirement to use the CSP for any of the software provided by TI. The standards do require that you follow the prescribed practices and process defined in the applicable safety standard. If you are using SW that you have not written yourself following a safety compliant process, you will need to qualify that software for use in your project. The CSP offers materials and tools to aid in this qualification process but are not required since you can also adapt your safety SW process to the Halcogen generated code and use that as justification for use within your safety application. Note, if you use your process, the code would need to be tested, documented, inspected, and put under all other scrutiny that you would your own code as part of your Safety SW development process. Evidence of safety compliance would need to be provided to any external assessor for system certification purposes.

Also note that Halcogen only provide support for limited safety diagnostics and it would be highly recommended to investigate use of the safety diagnostic library as well to get a more complete set of diagnostic SW capability or to write the diagnostics on your own.

Xinyu Wang said:

4. How to use F021 Flash API and SafeTI Hercules Diagnostic Library?

There are two parts to this answer. For either library, object files are provided that can be linked into your application using your linker. There is guidance to this in the included documentation for each.

The SafeTI diagnostic library has a second option also available since it is also provided as source code. You could simply include this source in your project as you wold any other source. If you choose this path, you would need to follow the same guidelines I mentioned for the Halcogen generated code above regarding use of the CSP or taking ownership and integrating the code into your process. Note that the installation package of the SafeTI Diagnostic Library include examples of integration of the library into a Halcogen generated project.

Xinyu Wang said:

5. How to use CRC block? Is it necessary for safety function?

CRC is included in several elements as a diagnostic measure. The need and effectiveness of these specific diagnostics are dependent on your system level requirements. Please see the applicable safety manual for the LS0232 for a complete list of the applicable diagnostic measures. The safety manual is available at this link: 

Xinyu Wang said:

6. How to use UniFlash to load HEX file into TMS570LS0232?

First, I would suggest you consider use of the native output from the TI compilers included with CCS which is by default a ".out" file unless you have a compelling reason to use the more generic HEX file. If you use the .out file as noted, it is relatively straight forward and covered by the available documentation for Uniflash. More information can be found on the Uniflash Wiki page located here: