Hi,
This issue is reported from my customer, they use ADC1_P[9] (PD[5]) and ADC1_S[15] (PM[14]) in same group with same setting. They find that ADC1_P[9] channel work properly, but ADC1_S[15] channel can’t get target value.
As checked, we find SIUL2_MSCR[53] (PD[5]) is 0x00400000, but SIUL2_MSCR[206] (PM[14]) is 0x00000002.
The Port configuration for these to channel are same:
We also check the EB generated code, it looks OK.
============================================================
/*Mscr ID, Mscr Value, Output Level, Direction, IsGpio, Direction Configurable, Mode Changeable, Is Imcr Available, Imcr Id */
{(Port_InternalPinIdType)53, (uint32)0x00400000, (uint8)2, (uint8)0, (boolean)FALSE, (boolean)FALSE, (boolean)FALSE, (boolean)TRUE, (uint16)0.0},
/*Mscr ID, Mscr Value, Output Level, Direction, IsGpio, Direction Configurable, Mode Changeable, Is Imcr Available, Imcr Id */
{(Port_InternalPinIdType)206, (uint32)0x00400000, (uint8)2, (uint8)0, (boolean)FALSE, (boolean)FALSE, (boolean)FALSE, (boolean)TRUE, (uint16)0.0},
============================================================
If we insert a code to configure the SIUL2_MSCR[206] register later to 0x00400000. The ADC can work properly.
Could anyone share you experience to me, whether this is EB bug or something I missed.
Customer MCAL version is Autosar 4.3.1 RTM1.0.2. Enclosed is the EB port configuration file and code.
Best regards,
Hornby
Hi,
We can’t put breakpoint at line 543, the return message is: Line not found
BR,
Hornby
Hi @hongpingxu-b364 ,
From driver I understand that driver just write value generated by configuration into MSCR and this value is correct. So, please send me the information as below:
I want to find where can change this value.
Best regards,
Nhi
Hi,
We found the code of PM14 operation inside the Port_Siul2_Init function. We wonder whether any impact on ADC configuration?
