MSPM0G3519: MCAL modules schema issues

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


  • 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

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

  • 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.