Nucleo-U5A5ZJ-Q and RNG code generation

[DenzilDexter]

Hello Community,

I have a Nucleo-U5A5ZJ-Q development board and have generated code for it using CubeMX (version 6.12.0).  The generated code contains this for the user button:

void EXTI13_IRQHandler(void)
{
  /* USER CODE BEGIN EXTI13_IRQn 0 */

  /* USER CODE END EXTI13_IRQn 0 */
  BSP_PB_IRQHandler(BUTTON_USER);
  /* USER CODE BEGIN EXTI13_IRQn 1 */

  /* USER CODE END EXTI13_IRQn 1 */
}

 If I enable the RNG in CubeMX and enable its global interrupt and then re-generate the code the above changes to:

void EXTI13_IRQHandler(void)
{
  /* USER CODE BEGIN EXTI13_IRQn 0 */

  /* USER CODE END EXTI13_IRQn 0 */
  HAL_EXTI_IRQHandler(&H_EXTI_13);
  /* USER CODE BEGIN EXTI13_IRQn 1 */

  /* USER CODE END EXTI13_IRQn 1 */
}

Which doesn't compile as H_EXTI_13 is not defined anywhere that I can see in any file.  am I missing something or is this a glitch in CubeMX. If I restore line 6 to its original value then the code compiles.

Any help much appreciated.

[Mahmoud Ben Romdhane]

Hello @DenzilDexter ,

First let me thank you for posting and welcome to the ST Community.

For more investigation, I suggest that you provide your Ioc.File.

Thanks.

Mahmoud

[ELABI.1]

Hi @DenzilDexter,

I reproduced the same example that you did and I didn't have any problems after enabling RNG.

Here is a screenshot before enabling RNG:

and her is a screenshot after enabling RNG:

I think you should update the version of CubeMx that you are using (the latest version is 6.14.1).

Thank you.

ELABI.1

[DenzilDexter]

Hello Mahmoud,
Here's the IOC file. As an aside I can make things work by defining this:

#define H_EXTI_13 hpb_exti[BUTTON_USER]

in the file `stm32u5xx_it.c` in a user code section.  
Thanks for the help,
DD

[Mahmoud Ben Romdhane]

Hello @DenzilDexter ,

Let me thank you for your interaction.

I am currently investigation your request and I will get back to you ASAP.

Thanks.

Mahmoud

[Mahmoud Ben Romdhane · Accepted solution]

Hello @DenzilDexter ,

Thank you for bringing to our attention this issue.

An internal ticket is raised to the development team (Ticket Number: 210032)

Thanks.

Mahmoud

[DenzilDexter]

For anyone seeing the same issue here's what the result was from ST:

I have investigated the issue you reported and can confirm that it is not related to the RNG. I have been able to reproduce your issue and have observed that altering the pin state of pin PC13 from Reset_State to GPIO_EXTI13 results in the same behaviour you experienced.

Following our internal discussions, I would like to inform you that the issue you raised will be addressed in the upcoming release of STM32CubeMX, version 6.15.0.

Thanks to ST for figuring this out so quickly.