Here we go again with suffixed parts (STM32G474RET6U)

[waclawek.jan]

From the 'G4 DISCO UM2577:

This board features a specific STM32 device version, which allows the operation of any bundled commercial

stack/library available. This STM32 device shows a "U" marking option at the end of the standard part number

and is not available for sales.

In order to use the same commercial stack in his application, a developer may need to purchase a part number

specific to this stack/library. The price of those part numbers includes the stack/library royalties.

I can find no mention of the U suffix on the 'G474 product folder webpage, nor in the DS.

ST, can you please properly document it this time?

Thanks,

JW

[Amel NASRI]

Hi @Community member​ ,

I don't think that the "U" suffix is specific only for the STM32G4 Discovery board.

Look at UM1724: STM32 Nucleo-64 boards (MB1136), we have following table with several devices having U suffix:

In the datasheet, suffixes other than "TR" are described as "programmed parts".

-Amel

[waclawek.jan]

Hi @Amel NASRI​  ,

very well, and do those STM32's product folders and DS explain that suffix?

Jan

[waclawek.jan]

Okay now I also stumbled upon STM32F091RCT6J .

It took us months back then to persuade somebody at ST to explain the suffixes of 'F407 (and thanks to the lazyness of those who migrated the forum and didn't care to preserve the links or make a static snapshot, I lost the link to that post and am not willing to find it again) how hard is to do this for all STM32? How hard it may be to write an appnote explaining these?

These are publicly traded parts, you can find them at distributors. You don't want to sell them, or what?

JW

[waclawek.jan]

OK so I dug it out

https://community.st.com/s/question/0D50X00009XkiOHSAZ/new-chips-with-u-suffix

and the link to presentation you've mentioned is still leading to 404. [EDIT] I dug it out from archive_dot_org (the autoidiotic salesforce editor inserts links where I don't want to) it was not worth the hassle, in the context of the long forgotten STM32Java mentions only U as "for sampling" and J as "for production"[/EDIT]

And in the thread which is linked there

https://community.st.com/s/question/0D50X00009XkgahSAB/stm32f405rgt6-part-numbering-mystery-u-v-w

there is another rotten link to

http://www.stm32java.com/products/java-ready-stm32-mcus/

I understand ST does not support these parts anymore, but then it should say so clearly, loudly, publicly.

JW

[EDIT[ for more laughs, https://export.farnell.com/stmicroelectronics/stm32-java/kit-java-software-dev-stm32-ide/dp/2311378?ost=STM32-JAVA&ddkey=https%3Aen-EX%2FElement14_Export%2Fsearch -- ST might consider working with the distributors dealing with the long obsolete stuff; but yeah, the dead bug policy is much simpler.

[waclawek.jan]

More weird and undocumented suffix: E

JW

PS. Parallel thread https://community.st.com/s/question/0D50X0000BXn5PJSQZ/what-is-the-difference-between-stm32h743zit6-and-stm32h743zit6u

@Amel NASRI​ 

[waclawek.jan]

Okay, so one more. Just for the fun, ST obviously won't comment these in any useful way.

STM32F303xB/C Errata DocID023637 Rev 9 dated July 2016 says this (and it appeared in that latest revision, in July 2016):

2.2.8 Imprecise V REFINT calibration values

Description:

The STM32F303xx devices not having “K�? at the end of the marking may have imprecise

V REFINT calibration values.

Workaround:

None. The parts marked with “K�? such as STM32F303xxTxK do not have the limitation.

Anybody seen these K-suffixed 'F303 in the wild?

JW

PS. Oh, and it would be nice to know how exactly is the VREFINT_CAL imprecise in the non-K-suffixed parts.

[waclawek.jan]

STM32L552 have -P and -Q suffixes, for external and internal SMPS, respectively.

This is at least properly documented in the DS.

JW

[EDIT] the related Nucleo has a -QU suffixed part, though, and that's presumably again the -U suffix with "licenced content", with no documentation whatsoever...

[waclawek.jan]

https://community.st.com/s/question/0D53W000000YqdISAS/stm32f20xxx-ordering-reference

Interestingly enough, the current UM1974 rev.7 has no mention of STM32F207ZGT6U .

JW

@Amel NASRI​ 

[waclawek.jan]

OK so ST *is* listening, just does not care to answer...

ES0204 Rev 10, dated 02-Jul-2020:

Updated Section 2.3.8: Imprecise V REFINT calibration values.

Imprecise V REFINT calibration values

Description:

The devices with a data code less than 628 may have imprecise V REFINT calibration values.

Workaround:

None.

JW