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.

F29H85X-MCAL-SDK: Ability to run the CDD drivers on CPU3

Part Number: F29H85X-MCAL-SDK

Hello,

The F29 MCAL drivers have to be run on CPU1. However, the CDDs are outside of the Autosar specification, so my customer wonder if they could use these CDDs on CPU3. This would enabled them reusing drivers of higher quality than those that are part of the SDK.

Could you please tell what it would take for the customer to port some CDDs to CPU3, or do we expect some big challenges in the process?

The CDD candidates are Cdd_Adc and Cdd_Pwm, though there could be more later on.

Thank you.


Best regards,
François.

  • Hi François, 

    Within the C29 architectures there are a few registers which can only be written into by CPU1. Regardless of the SW stack being SDK, MCAL or CDD, this applies to all of them. Most modules have some registers which work in this fashion. Hence we recommend running MCAL and CDD on CPU1. However if the features you want to use from these modules don't make use of such registers, the you can run them on CPU3.
    The effort depends completely on which module you are trying to use and the feature within the selected module. 

    You can refer to the F29x TRM, this has information on which registers have restricted access by CPU1 and decide if its feasible to run this on CPU3. 

    Regards, 
    Pranav Siddappa

  • Hi Pranav,

    Thank you. For the sake of completeness,  Table 7-28. Peripheral Registers Memory Map in the device datasheet lists which peripherals are accessible to CPU1/2/3.


    Best regards,
    François.