MSPM0G3507: Critical Issue: MSPM0G3507 ADC Driver Failure (MCAL_MSPM0_00.02.04.00) - Polling and Loop Conversion

Mohamed Abdelfatah

Part Number: MSPM0G3507

Dear Texas Instruments MCU Support Team,

I am integrating the provided TI MCAL (MCAL_MSPM0_00.02.04.00) for the MSPM0G3507 and encountering two issues that prevent reliable ADC operation. These issues are referenced in the official release notes as known defects, but I require clarification on workarounds or the status of the fix.

Issue ID	Description & Impact
[MSPMCAL-352]	ADCGroup DataAccessmethod: Group Polling access is not working. This prevents synchronous (polling-based) conversion results from being correctly reported and retrieved, forcing reliance on interrupts/notifications. I added a workaround in ADC.c in Adc_StartGroupConversion() to update the groupobj->status from Idle to Busy so that in Adc_ReadGroup() it can execute the Adc_groupPolling() in checking for groupObj->groupStatus.
[MSPMCAL-283]	ADC module StartGroupConversion does not work as expected in a loop. This means repeated software-triggered conversions fail to initiate or complete reliably when called repeatedly in a continuous loop.

I have confirmed the proper sequence of initialization calls:

MCU_Init(): Called successfully with two attempts at clock configuration: once with ULPCLK and once with MCLK.
Port_Init(): Called successfully to configure ADC pins (e.g., PA22) as PORT_PIN_IN with the appropriate MUX mode.
ADC_Init(): Called successfully to initialize the ADC module structures.

Could you please provide the following information regarding these known issues in the MCAL_MSPM0_00.02.04.00 package?

Workaround/Hotfix: Is there an official software workaround for issue [MSPMCAL-352] (Polling failure) that allows synchronous checking of the ADC status?
Loop Fix: What is the specific functional constraint or register that causes [MSPMCAL-283] (Loop Conversion failure), and is there an official sequence (e.g., adding a specific delay or status check) that should be implemented between loop iterations to ensure reliability?
Patch/Version Status: In which newer MCAL release version (if any) are these two defects officially resolved?