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.

Handle violations of MISRA C regulations in CCS system files

Other Parts Discussed in Thread: RM48L952, HALCOGEN

Hello, I'm YPP In Byung Ho.

We are developing using TI CPU (RM48L952).

The system environment is as follows.

  1. a) CPU : RM48L952
  2. b) CCS : ver12.1.0.00007
  3. c) Compiler Version: TI v20.2.7.TLS

 

Our company is preparing for SIL (IEC61508) certification.

Therefore, the MISRA C (2012) standard is applied.

 

A warning message appears when applying the MISRA C standard.

Example)

1) MISRA_C_2012_11_04 Violation

- Conversion between volatile uint32 * pointer type and unsigned int type is performed.

- sys_selftest.c file.

- void errata_PBIST_4(void) Function.

 

2) MISRA_C_2012_11_08 Violation

- A conversion was performed to explicitly remove the volatile of the config INSTRUCTION_t

- A conversion was performed to explicitly remove the volatile from the volatile structure 1RamBase

- het.c

- void hetInit(void) Function

 

 

All violations must be handled by applying the MISRA C standard.

1) How to handle the above violation sources (process according to MISRA C standard)

2) The MISRA C rule is said to have been <APPROVED> in the above violation comment, but the evidence for exception handling

 

There are many violations as examples.

Please let me know how to handle the violation.

 

thanks