2018-05-21 11:38 PM
Hi,
I am using STM32L053R8 controller.
I want to generate 100MHz, with 50% duty cycle.
Can you please share the code?
#stm32l053r8 #stm32l053r8-nucleo2018-05-22 12:18 AM
Hello,
parthasarthimalani
, I advise you to refer to the 'TIM_PWMOutput' example provided in package. It's found under the path below: STM32Cube_FW_L0_V1.0\Projects\STM32L053R8-Nucleo\Examples\TIMThe examples shows how to configure the TIM peripheral in PWM mode: It is configured to generate 4 PWM signals with 10 KHz frequency and duty cycles equal to 25, 3, 50 and 75%.
You may take the example as a reference to correctly configure your peripheral.
Khouloud.
2018-05-22 01:03 AM
I want to generate 100MHz, ...
Seems a bit out of spec, isn't it ?
2018-05-22 02:21 AM
I consider the 100Mhz as typo.
Even fast M7 do not support such high PWM frequencies - this is no use-case, for good reasons.
Try first to find switching elements (MOSFETs) that support such short cycle times. Magnetic losses in ferrite cores are substantial, with quite small permeability values. And not to mention the EMI issues, switching in the RF range.
2018-05-22 03:18 AM
Hi
meyer.frank
,Correct!
STM32L0 core frequency: from 32 kHz up to 32 MHz.Khouloud.
2018-05-22 04:00 AM
'
Any way I can do it?'
Two ways to do it.
1. The easy way: come back in 148 years. By then ST would have produced a chip capable of 100MHz.
2. The hard way : understand what you are trying to do
2018-05-22 04:51 AM
Hi , this is not typo, that is what my task.
I want to generate 100MHz PWM from same microcontroller.
Any way I can do it?
2018-05-22 05:06 AM
If you see data sheet of STM32L053R8 page number 101 --> table 70 --> Timer resolution time --> they have mentioned 31.25ns
2018-05-22 05:34 AM
>>If you see data sheet of STM32L053R8 page number 101 --> table 70 --> Timer resolution time --> they have mentioned 31.25ns
Ok, but in my part of the universe 100 MHz implies 5ns high, 5ns low
What part of your manual quote supports an argument for working at 100 MHz?
2018-05-22 05:38 AM
That is what my question, is it typo in datasheet? or we are not thinking in different way?