cancel
Showing results for 
Search instead for 
Did you mean: 

ADC do not work with 1.10 after migration.

GerHebert
Associate II

The clock "to ADC (MHz)" is grey in clock configuration. Don't see prescaler field in configuration. Plus it remove PLL **** configuration in main.c.

  /* Configure the system clock */
  SystemClock_Config();
 
//****** This below have been remove from my last commit! *********
/* Configure the peripherals common clocks */
  PeriphCommonClock_Config();
// ******
 
//****** And this:
/**
  * @brief Peripherals Common Clock Configuration
  * @retval None
  */
void PeriphCommonClock_Config(void)
{
  RCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0};
 
  /** Initializes the peripherals clock
  */
  PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_ADC;
  PeriphClkInitStruct.PLL2.PLL2M = 4;
  PeriphClkInitStruct.PLL2.PLL2N = 9;
  PeriphClkInitStruct.PLL2.PLL2P = 2;
  PeriphClkInitStruct.PLL2.PLL2Q = 2;
  PeriphClkInitStruct.PLL2.PLL2R = 2;
  PeriphClkInitStruct.PLL2.PLL2RGE = RCC_PLL2VCIRANGE_3;
  PeriphClkInitStruct.PLL2.PLL2VCOSEL = RCC_PLL2VCOMEDIUM;
  PeriphClkInitStruct.PLL2.PLL2FRACN = 3072;
  PeriphClkInitStruct.AdcClockSelection = RCC_ADCCLKSOURCE_PLL2;
  if (HAL_RCCEx_PeriphCLKConfig(&PeriphClkInitStruct) != HAL_OK)
  {
    Error_Handler();
  }
}
 

What is the workaround?

9 REPLIES 9
TDK
Guru

Attaching an IOC that replicates the problem would be helpful. Might be a bug, might be some other explanation.

Which ADC? Which chip?

If you feel a post has answered your question, please click "Accept as Solution".
GerHebert
Associate II

I attach the ioc.

Chip: STM32H750VBTx

Since 6.5.0 (FW 1.10), all ADC's into the chip do not have their clock configured correctly.

With CubeMX 6.4.0 (FW 1.9), the To ADC was blue and ADC's clock were configured correctly.

0693W00000KdTrwQAF.png

GerHebert
Associate II

I just started a project from scratch with STM32H750VBTx, I haven't been able to activate ADC clock yet. Pretty easy to reproduce...

Amel NASRI
ST Employee

Hi @GerHebert​ ,

This seems to be the same issue as reported in the following 2 questions:

Internal ticket number: 124251 (This is an internal tracking number and is not accessible or usable by customers).

@Khouloud OTHMAN​ can confirm or clarify more this issue.

-Amel

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hi @GerHebert​ ,

You're right, the issue is reproduced and confirmed.

Actually, a regression was detected with the latest STM32CubeMX 6.5.0 version: Clock Prescaler parameter removal from the GUI and the non-activation of ADC Clock Mux although the ADC is configured.

As mentioned by @Amel NASRI​ , this misbehavior was already reported internally to be fixed as soon as possible.

I'll keep you posted with the updates.

Sorry for any inconvenience that this may cause.

Khouloud.

R Piacenzia
Associate III

I have the same issue. Is there an ETA for this fix?

TDK
Guru

Historically, it has been several months between CubeMX releases, and one just came out recently.

If you feel a post has answered your question, please click "Accept as Solution".
Tim Goll
Associate II

36 days have passed and this is still broken, wow. I just spent two days trying to figure out why my project is suddenly broken.

For anyone wondering: downgrade to version 1.7.0. You have to change you ioc file version though:0693W00000LydZsQAJ.png

ADunc.1
Senior

I just came across this problem... Any idea when a fix will be released?