RM48L952: misra compliance for halcogen code

Hi Jen Lee,

The code generated from HALCoGen for Hercules device (RM48) is comply with the MISRA-C 2004 coding guidelines only.

SAFETI-HALCOGEN-CSP IDE, configuration, compiler or debugger | TI.com

You can download the test reports related to the MISRA-C 2004 from above CSP link.

--

Thanks & regards,
Jagadish.

Hi Jagadish,

My problem is many violations from HalcoGen created code during static analysis for MISRA-2004.

I read some questions related my problem in this forum and I realized that I need TI's MISRA polish that says which option should be excluded.

If you have such document please share to me...

I tried to find out something in the link you sent but I couldn't..

I will very appreciate for your help.

Thanks and regards,

Jin Lee

Hi Jin Lee,

Can you please share your build log?

So that i can verify what kind of errors you are getting.

--
Thanks & regards,
Jagadish.

Hi, thanks.

What do you mean with build log?

Do you mean CCS compile log??

There is no error or warning during compilation.

I share the  LDRA code review report.

In this report, there are many violations of my code and HalcoGen code, I am working on violations of my code.

I think you can identify the violations of HalcoGen created code from this report.

Thanks and regards,

Jin Lee

Sorry, I failed to upload my file... I don't know how do I do.

Below is a sample of violation fro MISRA-2004.

I 

Hi Jin,

Here are the build options:

Compiler Options: -mv7R4 --code_state=32 --float_support=VFPv3D16 --abi=eabi -g --define=_BIG_ENDIAN --diag_warning=261 --diag_warning=118 --diag_warning=225 --diag_error=189 --diag_error=994 --diag_error=551 --display_error_number --enum_type=packed
Linker Options: --reread_libs --warn_sections --rom_model --be32
Run time Library: rtsv7R4_T_be_v3D16_eabi.lib
CG Tool Root Path: C:\ti\ccsv8\tools\compiler\arm_5.1.6
DependencyLibraryStart:
"C:\ti\Hercules\F021 Flash API\02.01.01\F021_API_CortexR4_BE_L2FMC.lib"
DependencyLibraryEnd
IncludePathStart:
C:\ti\Hercules\F021 Flash API\02.01.01\include
IncludePathEnd
SourcePathStart:
"C:\ti\Hercules\F021 Flash API\02.01.01\source"
SourcePathEnd

Can you try with above settings?

--
Thanks & regards,
Jagadish.

Hi Jagadish,

Thank you for your reply, and I will try with your advice.

But, I can't understand about your advice...

I said that I have violations during STATIC test for MISRA-C 2004.

This means the problem is in SOURCE code generated by HalcoGen, not in object.

Does the compiler build option will help this problem?

Thanks and regards,

Jin Lee

Hi Jin,

Just do the static analysis by changing build options and see and also please note the following things:

Few things to note about MISRA check
1) Some MISRA check tool difference, HALCoGen code MISRA rule checks were performed by LDRA tool.
2) We do have MisraC2004 Policy documentation across our team which we adhere to, the document contains the list of rules we follow mandatory and rules for which we have justification for the violations. Policy documentations are provided to customers through CSP, also on top of the line where MISRA violation is we have provided the justifications, which got approved after going through code review.
3) we cannot simply enable all rules and expect 100% adherence.

--

Thanks & regards,
Jagadish.

Dear Jagadish,

I couldn't make the static analysis until now because I don't have the LDRA tool by myself.

I am working with a consulting entity in Korea and they have the LDRA tool and do the test, I need some time to arrange new test.

I will do the test as you said.

By the way, I need the police that states which rules should be excluded or modified.

You said it is provided through CSP...

Do you mean that I have to purchase the CSP license?

Is there any other way to get the document for me?

Thanks,

Jin Lee

Hi Jin,

Apologies for the delay in my response.

I too don't have hands on experience with LDRA tool and CSP. I just forwarded to QJ, who have great experience with this, hopefully he will provide response soon.

--
Thanks & regards,
Jagadish.