CubeMX HRTimer config bug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-07-14 6:28 AM
Hello
I found bug in BurstMode Configuration in HRTimer. There is not possible to set Burst Mode Period lower than DeadTime. It is OK, but CubeMX compare numbers only and does not count with prescalers values. I think Burst mode period must be grater that deadtime in time domain. In reference manual for STM32f334 (RM0364) is said:
The burst mode period must not be less than or equal to the deadtime duration defined with
DTRx[8:0] and DTFx[8:0] bitfields.
But I think it is logical to compare it as time interval...
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-08-09 6:38 AM
Hello,
Last version 6.9.1 does not include a check on RM condition between Burst period and deadtime duration.
I agree with you that it is better to have such check in CubeMx and also based on time duration and not values.
We will proceed with a double-check on such condition and updates in future versions.
Thank you again for your finding,
Best regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-08-11 3:44 AM
Hello
I reported the issue internally, internal ticket number: 159087 (This is an internal tracking number and is not accessible or usable by customers
Best regards.
