Skip to main content
waclawek.jan
Super User
February 10, 2026
Question

Display "functional" part number suffix in Cube Programmer

  • February 10, 2026
  • 2 replies
  • 245 views

There are STM32 models, where the suffix denotes a dramatic difference in the chip's pinout - either because of the USB-C PD -related variants, or because of SMPS variants. As the suffix is beyond the "lesser" parts of marking such as temperature range, sometimes distributors and vendors neglect/omit it, resulting in non-functioning products and frustration.

For these models, CubeProgrammer should display the suffix along with the model number; it even should display something like "no suffix" for the variant without suffix, to be explicitly clear about this.

This requirement stems from experiences like in this thread.

JW

2 replies

Aziz BRIGUI
Technical Moderator
February 11, 2026

Hi @waclawek.jan,

As hinted at by the user in the thread you mentioned, STM32CubeProgrammer is not able to access all the information of the part number (Even with debug interfaces). Target information section is only to display general and accessible information (Device ID, Size, etc ...). It's for the user to check the official ST documentation for any further information regarding their device.

Aziz

In order 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.
waclawek.jan
Super User
February 11, 2026

Hi @Aziz BRIGUI ,

I am not talking about *all* the information in the part number, but specifically about the suffix which distinguishes (sub-)models, which have different functionality but are outwardly identical, such as are the STM32G0B1xxxx (no suffix) and STM32G0B1xxxxN in the said thread.

This is important exactly because it's not outwardly obvious yet functionally vital (so unlike the package size/style and temperature range, which are encoded in the xxxx).

This information should be available for CubeProgrammer, as it's part of the Device Signature, as a field in the Package data register.

JW

Pavel A.
Super User
February 11, 2026

@Aziz BRIGUI Is there any way at all to retrieve this information? For example, from the unique ID of the chip, by querying some database? If yes, could ST provide online access to such database?