Skip to main content
Associate II
September 25, 2025
Solved

Reading STM32U5A5 Rev. ID returns 0x3003 that is not listed in Reference Manual

  • September 25, 2025
  • 10 replies
  • 966 views

Reading STM32U5A5 Rev. ID returns 0x3003 using STM32Cube HAL API that is not listed in Reference Manual (RM0456). What is the revision of this product? The Reference manual lists only 0x3001 as revision X and 0x3002 as revision W.

Thanks.

Best answer by Viktor POHORELY

Hello, I confirm that revision W provides reading of 0x3003. RM/ES will be updated (for RM, the update is taking usually longer time).

10 replies

KDJEM.1
ST Technical Moderator
September 26, 2025

Hello @omniwiz and welcome to the community;

 

To check the issue, could you please share a photo of STM32U5A5 device and a screenshot of DBGMCU identity code register (DBGMCU_IDCODE) contents?

 

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on "Best answer" on the reply which solved your issue or answered your question.
omniwizAuthor
Associate II
September 26, 2025

Thanks for the response, @KDJEM.1 !

The DBGMCU_IDCODE content is 0x30036481. Also attached is the photo of the STM32U5A5 device.

omniwiz_0-1758910713393.jpeg

 

KDJEM.1
ST Technical Moderator
September 29, 2025

Hello @omniwiz ;

 

Thank you for sharing the MCU photo.

Could you please connect the your device using STM32Cubeprogrammer toolchain and share screenshots of the values at addresses 0XE0044000 (DBGMCU identity code register) and 0x0BFA 0700 (Unique device ID register) as shown in the below figures.

 

KDJEM1_3-1759133588648.png

KDJEM1_4-1759133740830.png

 

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on "Best answer" on the reply which solved your issue or answered your question.
ST Technical Moderator
September 26, 2025

Hello @omniwiz 

I checked the HAL_GetREVID() function and confirmed that it reads the upper 16 bits of the DBGMCU_IDCODE register, as specified in the reference manual.

uint32_t HAL_GetREVID(void)
{
 return ((DBGMCU->IDCODE & DBGMCU_IDCODE_REV_ID) >> 16);
}

 

Saket_Om_0-1758893314127.png

 

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Saket_Om
omniwizAuthor
Associate II
September 30, 2025

Hello @KDJEM.1 ,

Do you have an update? Thanks!

KDJEM.1
ST Technical Moderator
October 1, 2025

Hello @omniwiz ;

 

Thank you for sharing these screenshot.

I reported this issue internally for checking.

I will get back to you with more details as soon as possible.

 

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

 

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on "Best answer" on the reply which solved your issue or answered your question.
Viktor POHORELY
Viktor POHORELYBest answer
ST Employee
October 2, 2025

Hello, I confirm that revision W provides reading of 0x3003. RM/ES will be updated (for RM, the update is taking usually longer time).

Tesla DeLorean
Guru
October 3, 2025

Is this a second source fab for the die?

Can you list all the current DEVID?

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
omniwizAuthor
Associate II
October 2, 2025

Thanks, @Viktor POHORELY and @KDJEM.1 !