MPC5744P & Autosar (MPC574XP_MCAL4_0_RTM_2_0_2)

[MElGreatly]

Hello experts,

I installed the AUTOSAR MCAL package MPC574XP_MCAL4_0_RTM_2_0_2, but it fails to work on the MPC5744P. To isolate the issue, I commented out all application code in main() and replaced it with a minimal test case:

BoardInit(); GPIOInit(); CANInit();

This test code (with hardcoded register values, where only register addresses are initialized) is trusted—it has worked in multiple MPC5744P S32 projects. However, in the AUTOSAR project, while the debugger confirms registers are set correctly, the CAN peripheral remains non-functional.

Questions:

Could the MPC574XP_MCAL package be incompatible with the MPC5744P despite shared branding?

Why might the test code fail in the AUTOSAR context despite working elsewhere?

Could the AUTOSAR startup code (e.g., clock initialization, MPU configuration, or exception handling) conflict with the MCAL or hardware?


Thanks in advance.

[MElGreatly]

Thank you Peter for your answer,

First:  My development Board is https://www.nxp.com/design/design-center/development-boards-and-designs/DEVKIT-MPC5744P

I downloaded these packages: Autosar Version 4.0.3

Second: I need to test the CAN task which uses CAN0, it didn't work, so I used EB tresos to generate another configuration file;
Look at this part of the generated configuration: Can_PBcfg.c file: 
Configuration of FlexCan controller

the CTRL1 register was not affected by changing the configuration,
the case in screenshot  - for example -
PSEG1 =2
PSEG2 =2
PROPSEG =5
RJW =2
but the values in the CTRL1 register are ones ( after Can_Init function -in Can.c - return ) 


Ones filled after this part in Can_FlexCan_ChangeBaudrate function - in Can_Flexcan.c - which called in Can_Init function.

Are there any bugs at this peripheral ?

Are there any solutions to operate the CAN peripheral using these package ?

Thanks in advance.

[petervlna]

Hello,

Here is the feedback from SW team:

Follow the release note, please make sure that the diab version was supported for this release is:

Can you read Can_ControllerStatuses and show value of all elements in this structure at some points as below:

like this:

Some bits in CTRL1 just can be write in Freeze mode as RM mentioned:

So, please make sure that CAN controller is in Freeze mode before setting CTRL1 value, you can check this through the register MCR

This setting and checking is in the function Can_FlexCan_ChangeBaudrate() 

Best regards,

Peter

[MElGreatly]

Hello,

 Diab version is:

 Can_ControllerStatuses value at Can_FlexCan_InitVariables function:

 Can_ControllerStatuses value at Can_FlexCan_ChangeBaudrate function:

The same value for Can_ControllerStatuses before setting CTRL1 value

Thanks

[petervlna]

Hello,

there is no restriction on access to CTRL1 register:

Switch to assembly debug to check the instruction execution on core to see if the register is really going to be modified. Also try direct write via debugger.

I am sure there is no issue in HW here.

Either the peripheral is not clocked and you trying to write or the SW is simply not performing writes to the register address.

Are there any bugs at this peripheral ?

All issues are described in errata sheets. But I do not expect the issue is in uC. I suspect your SW.

Simply try write via debugger to the register..

Best regards,

Peter

[MElGreatly]

I tried direct write; worked , and I noticed that the problem is the global array of struct named "Can_ControllerStatuses[CAN_MAXCTRL_CONFIGURED]" was not affected with direct write of any member of this struct that should holding current status/run-time configuration of individual FlexCAN controllers, 

At Can_FlexCan_InitVariables function in Can_Flexcan.c that initializes all global variables/statuses for all controllers, 

this screenshot shows the 1111 values after write 0 to this member of the struct ! 
why is this happen ? I use diab compiler and S32 , this is my project attached, if you could help for any solutions.

Thanks for advance.

 

[petervlna]

Hello,

I have forwarded your issue to the SW team as I am not familiar with CAN driver.

Once I have answer I will update you.

Best regards,

Peter

[petervlna]

Hello,

Could the MPC574XP_MCAL package be incompatible with the MPC5744P despite shared branding?

No. It is fully compatible and tested on MPC574xP device.

Could the AUTOSAR startup code (e.g., clock initialization, MPU configuration, or exception handling) conflict with the MCAL or hardware?

No. As the MCAL is AUTOSAR compliant. (developed according the autosar standard).

Why might the test code fail in the AUTOSAR context despite working elsewhere?

Not sure. Example code should work right after import.

Could the MPC574XP_MCAL package be incompatible with the MPC5744P despite shared branding?

Always refer to release notes of the SW packages.

So maybe you have autosar other then 4.0.

Best regards,

Peter