Skip to main content
CVerh.2
Associate
December 23, 2022
Question

On STM32U585 the GPIO G are not driveable (while others are fine)

  • December 23, 2022
  • 2 replies
  • 804 views

Hello,

While trying to setup an UART connection with a STM32U585ZIT6, we realized that it was not possible to drive the G connectors. To isolate the issue we tried to drive others GPIOs and they are totally fine while GPIOs G remain stuck at GND.

We created a new project from STM32Cube and only activated some GPIO to ensure that they are all working except the GPIOs G.

We added the following lines to the output of STMCube :

while (1)
 {
	 HAL_Delay(1000);
	 HAL_GPIO_WritePin(GPIOG, GPIO_PIN_6, GPIO_PIN_SET); //does not drive
	 HAL_GPIO_WritePin(GPIOB, GPIO_PIN_6, GPIO_PIN_SET); // drive
 
	 HAL_Delay(1000);
	 HAL_GPIO_WritePin(GPIOG, GPIO_PIN_6, GPIO_PIN_RESET);
	 HAL_GPIO_WritePin(GPIOB, GPIO_PIN_6, GPIO_PIN_SET);
 
 
 /* USER CODE END WHILE */
 
 /* USER CODE BEGIN 3 */
 }
 /* USER CODE END 3 */
}

Best regards,

Corentin

This topic has been closed for replies.

2 replies

Tesla DeLorean
Guru
December 23, 2022

Sounds like you need to enable VDDIO2​

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
CVerh.2
CVerh.2Author
Associate
December 23, 2022

Hello,

Thank you for the quick reply. I forgot to precise that we checked that VddIO2 is well enabled through SystemPower_Config that is called in the main (as in the output of STM32Cube).

static void SystemPower_Config(void)
{
 HAL_PWREx_EnableVddIO2();
 
}

I just observe that I also forgot to precise that a colleague is able to drive the GPIOG on the same hardware by using an anterior version of STM32IDE.