MISRA Discussion Forums - 6.1 Environment

Rule 1.2 Problem wih array parameter

Tue, 26 Mar 2013 15:17:22 +0000

I'm using lint to check my code is MISRA Compliant. I have one funtion with buffer definition. This buffer (8 uint8) is passed by parameter to another function to manage it. I receive this message in "CAN_Get_DCDC_SUP_Status(aux_Can);"
"Note 934: Taking address of near auto variable 'aux_Can' (arg. no. 1) [MISRA 2004 Rule 1.2]"

I have following sippet code:

T_u16 CanId = (T_u16)0;
T_u8 aux_Can[8]={0U,0U,0U,0U,0U,0U,0U,0U};

CanId = ((T_u16)((T_u16)CAN0RIDR0 > 5U));

switch (CanId)
{
case ID_DCDC_SUP_Status:

aux_Can[0] = CAN0RDSR0;
aux_Can[1] = CAN0RDSR1;
aux_Can[2] = CAN0RDSR2;
aux_Can[3] = CAN0RDSR3;
aux_Can[4] = CAN0RDSR4;
aux_Can[5] = CAN0RDSR5;
aux_Can[6] = CAN0RDSR6;
aux_Can[7] = CAN0RDSR7;

CAN_Get_DCDC_SUP_Status(aux_Can);
(....)

The funciton is

void CAN_Get_DCDC_SUP_Status(T_u8 *aux_Can)
{
T_u16 temp=0;

/*Byte 0*/
aux_Can[0]=aux_Can[0]>>1;
SetU2_DCDC_SUP_HVBatt_OC(aux_Can[0] & 0x03);
aux_Can[0]=aux_Can[0]>>2;
SetB_DCDC_SUP_DRV1_Fault(aux_Can[0] & 0x1);
(...)

with prototype (in header file):

void CAN_Get_DCDC_SUP_Status(T_u8 *aux_Can);

Does anyone has explanation/solution?

Best Regards

MIRCA 2004 Rule 1.1

Tue, 04 Jul 2006 08:23:13 +0000

Hi,

MISRAC 2004 Rule 1.1 refers to the environment limits specified in section 5.2.4 of the ISO 9899:1990 standard.

According to this rule, should all the limits specified by this section be STRICTLY followed, or only the one limit on internal and extrenal identifier length be strictly followed (Rule 5.1). Is a piece of code having 128 nesting levels of blocks MISRAC compliant?

Also there is a mention of the need to have certain compiler extentions in the code. Is a piece of code, having certain compiler extentions MISRA compliant? Or is it upto the organisation to decide that?

Best Regards
Vkmet

Rule 1.1 and Number of characters for Header File name

Tue, 21 Feb 2006 17:12:02 +0000

The rule 1.1 deals with limits defined in chapter 5.2.4 of ISO-9899:1990 norm.

But for the #include preprocessing directive, the 9899:1999 (and so, I suspect that the C90 is more restrictive) specify in chapter 6.10.2 some restriction (limits) about the sequence placed between the \" \" or < > delimiters:

The implementation shall provide unique mappings for sequences consisting of:
- one or more digits (no case sensitive)
- followed by a period
- followed by a single letter.
- The mapping is restricting to eight significant characters before the period.

So if the sequence between \" and < > delimiters is specified, then the header file names are impacted.

I would like to know if it is MISRA compliant to have a header file name with more than 8 characters before the period ?
(Example: FooComponent_Api.h)

Thanks in advance for your answer.