Skip to main content
Andrea Canepa
Andrea Canepa
Senior
November 27, 2018
Question

STM32CubeMX Version 5 bugs: missing TIM20 and wrong clock in TIM2 Clock Configuration

  • November 27, 2018
  • 6 replies
  • 4319 views

I have created a project for STM32F303REtx.

1° BUG: TIM20 is missing from the list of available timers. Instead in the "reference manual" and in the internal registers visible in debugging the TIM20 timer is present. See attached picture: 0690X000006CUUJQA4.png

2° BUG: In the clock settings, for the TIM2 timer I have selected PLLCLK*2 in order to have 144 MHz (as is the case for TIM3/4 visible in the image).

At the time of setting, the correct indication (144MHz) occurs in the rectangle next to the word "TIM2". After saving the project, closing the project and opening the same project again, going to see in the clock configuration I always find "72MHz". In truth, the true clock at TIM2 is 144MHz, so it's just a data display problem, in fact the generated code is right.

0690X000006CUUsQAO.pngRegards,

Andrea

This topic has been closed for replies.

6 replies

W
WBOUG
Visitor II
November 29, 2018

Hello @Andrea Canepa​ 

Thank you very much for your feedback.

  • About 1° BUG it will be corrected in next CubeMX version .
  • About 2° BUG you are working with an MCU whose default frequency is not very important, however if you use a Board it is mandatory a default freiquece

Best regards,

Wael

Andrea Canepa
Andrea CanepaAuthor
Senior
November 29, 2018

About 2° BUG: as I wrote, the actual frequency at TIM2 is 144 MHz, so the generated code is right. It is only a display defect that occurs after saving and reloading the project. Made myself clear?

W
WBOUG
Visitor II
November 29, 2018

Hello @Andrea Canepa​ 

Yes you're right but it's not a real bug. You can change the manual frequency since you work with MCU.

Best regards,

 Wael

Andrea Canepa
Andrea CanepaAuthor
Senior
November 29, 2018

Ok, but to me it does not seem correct that if I select the 144MHz frequency, and I actually get 144 MHz, then the written one goes back to 72MHz. I consider it a BUG, otherwise it would remain with the writing 144 MHz as it happens for the other timers (see TIM3/4 in the same image); I do not think this was intended by programmers.

Regards,

Andrea

W
WBOUG
Visitor II
November 29, 2018

Hello @Andrea Canepa​ 

OK sir. I will do my best and I will always be at your service and availability at any time.

Best regards,

Wael

waclawek.jan
waclawek.jan
Super User
January 17, 2019

Hi @WBOUG​ ,

While in 'F303Rx - i.e. 64-pin packages - there are not TIM20-related pins - the timer may still be present internally and usable for all purposes which do not require pins - e.g. timing, DMA triggering, ADC triggering,

Can you please positively confirm that TIM20 is *not* present (or *not* supported, e.g. *not* tested, or may be removed in future revisions) in the Rx packages? If it is so, Table 1, and the note in chapter 20.1 TIM1/TIM8/TIM20 introduction in RM0316 should reflect this fact, too.

Thanks,

JW

W
WBOUG
Visitor II
January 18, 2019

Hi @Community member​ 

datasheet table 2 and its associated note 1 indicates the contrary.

refman supports all component of the series and does not distinguish F303Rx or F303Vx for example

SVD file is unique for all F303 devices. this is why you can find Tim20 for F303Rx.

Best Regards,

Wael.

waclawek.jan
waclawek.jan
Super User
January 18, 2019

> refman supports all component of the series and does not distinguish F303Rx or F303Vx for example

Yes, that's the problem I am complaining about. If there are missing modules in certain models, the reference manual should say so.

JW

W
WBOUG
Visitor II
January 18, 2019

Hi @Andrea Canepa​ 

You're right about your bug 2

it will be implemented in the next version

Best Regards,

Wael

Terms & ConditionsAccessibility statement