• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 111 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

F29H859TU-Q1: MCAL setting question

zhentao gao
Prodigy 50 points

Part Number: F29H859TU-Q1

  1. Regarding F29H85xMCAL-01.04.01.02 MCAL package, the resourceAllocator module cannot generate C code, does it mean that the allocation of peripherals to CPU cores requires manual setting through CDD code?
  2. Is the lockstep of the CPU also manually set through CDD code?
  3. As shown in the figure below, Adc/I2C/PWM module is standard AUTOSAR module, Why are these modules set as complex driving modules? According to the user guide, the functions of these modules comply with the AUTOSAR 4.3.1 standard, but the module interfaces and type definitions do not comply with the AUTOSAR standard;
  1. image.png
  • 0
    TI__Intellectual 2426 points

    Hi Zhentao Gao, 

    zhentao gao said:
    Regarding F29H85xMCAL-01.04.01.02 MCAL package, the resourceAllocator module cannot generate C code, does it mean that the allocation of peripherals to CPU cores requires manual setting through CDD code?

    -> The Resource Allocator module [RA] doesn't generate C code, it simply provides references and meta data to other modules. Other modules' generator files make reference to RA to know limits of the device/variant. 

    zhentao gao said:
    Is the lockstep of the CPU also manually set through CDD code?

    -> In v01.04.01, the device operates in lockstep mode by default. From the next release, user will have the option to select this via RA configurator in EB Tresos. As of now, the user will have to manually disable lockstep mode if not required. 

    zhentao gao said:
    As shown in the figure below, Adc/I2C/PWM module is standard AUTOSAR module, Why are these modules set as complex driving modules?

    -> The decision for the modules to be CDD is based on a few parameters: 

    • The MCAL module doesn't exist in 4.3.1 AUTOSAR [I2C, DMA]
    • The in board IP offers more features than what AUTOSAR prescribes [ADC]
    • The IP doesn't adhere to basic AUTOSAR naming or functional constraints [PWM]
      Because of these, the modules don't qualify as MCAL, hence CDD

    Regards, 
    Pranav Siddappa

  • 0 in reply to Pranav Siddappa
    Prodigy 50 points

    Hi Zhentao Gao, 

    zhentao gao said:
    Regarding F29H85xMCAL-01.04.01.02 MCAL package, the resourceAllocator module cannot generate C code, does it mean that the allocation of peripherals to CPU cores requires manual setting through CDD code?

    -> The Resource Allocator module [RA] doesn't generate C code, it simply provides references and meta data to other modules. Other modules' generator files make reference to RA to know limits of the device/variant. 

    zhentao Reply: does it mean that the allocation of peripherals to CPU cores requires manual setting through CDD code?
    zhentao gao said:
    Is the lockstep of the CPU also manually set through CDD code?

    -> In v01.04.01, the device operates in lockstep mode by default. From the next release, user will have the option to select this via RA configurator in EB Tresos. As of now, the user will have to manually disable lockstep mode if not required. 


    zhentao Reply: Is the default lockstep implemented in CCS project? It's not related to the EB setting, right?

    zhentao gao said:
    As shown in the figure below, Adc/I2C/PWM module is standard AUTOSAR module, Why are these modules set as complex driving modules?

    -> The decision for the modules to be CDD is based on a few parameters: 

    • The MCAL module doesn't exist in 4.3.1 AUTOSAR [I2C, DMA]
    • The in board IP offers more features than what AUTOSAR prescribes [ADC]
    • The IP doesn't adhere to basic AUTOSAR naming or functional constraints [PWM]
      Because of these, the modules don't qualify as MCAL, hence CDD

    zhentao Reply: Let's analyze it when we need to use it;

    Regards, 
    Pranav Siddappa

  • 0 in reply to zhentao gao
    TI__Intellectual 2426 points

    Hi Zhentao Gao, 

    zhentao gao said:
    zhentao Reply: does it mean that the allocation of peripherals to CPU cores requires manual setting through CDD code?

    -> As of v01.04.01 MCAL offers only CPU1 support via EB Tresos config. Hence the allocation has to be done manually for the other cores.

    zhentao gao said:
    zhentao Reply: Is the default lockstep implemented in CCS project? It's not related to the EB setting, right?

    -> Lockstep is supposed to be enabled and disabled in the start up code. The user must update the below register in the startup code to configure lockstep: 


    Regards, 
    Pranav Siddappa