Skip to main content
Explorer II
February 8, 2026
Solved

RM0503 19.6.2: PS and DIV examples accidentally mix decimal and binary

  • February 8, 2026
  • 3 replies
  • 193 views

In section 19.6.2 LCD frame control register (LCD_FCR) of the STM32U0 RM0503 Reference Manual, the examples provided for PS and DIV initially count up in decimal, but finish in binary. This looks like an accident and is confusing to the reader.

bdom_0-1770532286787.png

 

https://www.st.com/resource/en/reference_manual/rm0503-stm32u0-series-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
All other examples further down in section 19.6.2 correctly count up in binary and do not mix in decimal numbers:

bdom_1-1770532344223.png

 

 

Best answer by Viktor POHORELY

Ah, I see the point, thanks!

I will ask for doc update. Please note it will be done during next regular update of the documentation.

3 replies

Technical Moderator
February 8, 2026

Hello @bdom and welcome to the Community

I raised your request to the internal team for review through Internal ticket number 226853 (ticket number is only for reference and not available outside of ST).

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"
Viktor POHORELY
ST Employee
February 9, 2026

Hello, I'm not sure to catch where the problem is?

ck_ps divider is calculated as power of two, thus 2^PS

0000 = 2^0 = 1

0001 = 2^1 = 2

0002 = 2^2 = 4

etc.

ViktorPOHORELY_0-1770601609546.png

 

DIV is also part of this formula, with range of 0 to 15, thus in the bracket will be values from 16 to 31 as in the register description.

Does this help to understand it?

Senior III
February 9, 2026

The problem is, as @bdom mentionned, the RM mixes up binary and decimal values.

To put it differently, the errors in the RM are the lines "0002: ck_...", they should read "0010: ck_..."

 

Viktor POHORELY
Viktor POHORELYBest answer
ST Employee
February 9, 2026

Ah, I see the point, thanks!

I will ask for doc update. Please note it will be done during next regular update of the documentation.