• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 193 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.

MSPM0G3519: MCAL modules schema issues

Ahmed Atwa
Prodigy 10 points

Part Number: MSPM0G3519

I found issues in Adc and Gpt schemas which result in generation issue with DaVinci tool. The schemas are located in "MCAL_MSPM0_01.00.00.00_RC\mcal_config\plugins\MSPM0G351x\AUTOSAR_431\Adc_TI_MSPM0G351x\config\Adc.arxml" and "MCAL_MSPM0_01.00.00.00_RC\mcal_config\plugins\MSPM0G351x\AUTOSAR_431\Gpt_TI_MSPM0G351x\config\Gpt.arxml".

For the Adc, there are multiple issues caused by invalid enurmation list for AdcGroupTriggSrc, AdcGroupConversionMode, AdcGroupAccessMode and AdcStreamingBufferMode parameters. For example AdcGroupTriggSrc shall have ADC_TRIGG_SRC_SW and ADC_TRIGG_SRC_HW enumartion values but the available is undefined option only.


Adc_Schema.png


For Gpt, GptChannelTickFrequency and GptChannelTickValueMax parameters are not available which cause an issues in Wdg module generation as it parses them in Cfg template files.

Gpt_Schema.png


  • 0
    Prodigy 10 points

    Hello,

    Another issue was detected in Pwm_Priv.c file because wrong allocation of non const variable to const section (Pwm_TimerInstancesData to PWM_CONST_32_SECTION) causing linking issues " Error[Lp005]: placement includes a mix of sections with content (example "ro code section .eraseLoadSram in Fls_ac.o symbols: [Fls_executeCommand]")  [suitable for placement in ROM] and sections without content (example "rw data section PWM_CONST_32_SECTION in Pwm_Priv.o symbols: [Pwm_TimerInstancesData]") [suitable for placement in RAM] ".


    Best regards,

    Ahmed Atwa

  • 0 in reply to Ahmed Atwa
    TI__Mastermind 26228 points

    Thanks for the patience, I need loop software team to support this.

  • 0 in reply to Helic Chi
    TI__Mastermind 26228 points
    Ahmed Atwa said:
    Another issue was detected in Pwm_Priv.c file because wrong allocation of non const variable to const section (Pwm_TimerInstancesData to PWM_CONST_32_SECTION) causing linking issues " Error[Lp005]: placement includes a mix of sections with content (example "ro code section .eraseLoadSram in Fls_ac.o symbols: [Fls_executeCommand]")  [suitable for placement in ROM] and sections without content (example "rw data section PWM_CONST_32_SECTION in Pwm_Priv.o symbols: [Pwm_TimerInstancesData]") [suitable for placement in RAM] ".

    Issue confirmed.

    At the same time, you can modify the source code to fix it.

  • 0 in reply to Helic Chi
    TI__Mastermind 30252 points

    Hi Helic,

    Thank you for this confirmation about PWM. Could you also give your feedback about ADC and GPT?


    Best regards,
    François.

  • 0 in reply to Francois Charlot
    TI__Mastermind 26228 points

    For 

    Ahmed Atwa said:
    For Gpt, GptChannelTickFrequency and GptChannelTickValueMax parameters are not available which cause an issues in Wdg module generation as it parses them in Cfg template files.

    Wdg module in EB requires changes of Gpt module:

  • 0 in reply to Helic Chi
    TI__Mastermind 26228 points
    Ahmed Atwa said:
    For the Adc, there are multiple issues caused by invalid enurmation list for AdcGroupTriggSrc, AdcGroupConversionMode, AdcGroupAccessMode and AdcStreamingBufferMode parameters. For example AdcGroupTriggSrc shall have ADC_TRIGG_SRC_SW and ADC_TRIGG_SRC_HW enumartion values but the available is undefined option only.

    It's a valid check box here.

    but for arxml file, do you means arxml file generate function of EB has issue?