clock is the apb clock,and there is no prescale.
so the input frequency is apb_clk/Δ.
test is ok for 1k,500Hz and so on.

maybe we can close this issue.

i have find the reason of the interrupt error. and i don't call the api from the flash this issue can be fixed.such like this picture ... just for the calculation of the frequency, the input signal is 1kHz but we can see the result is 875 form the terminal log. so there is something wrong with this ...

when i call the api(current_cap_val = mcpwm_capture_signal_get_value(MCPWM_UNIT_0, MCPWM_SELECT_CAP0);) from the capture interrupt function, thie issue will appear by high frequence.

another question about the capture, see the picture for more details. 1. how can i fix this issue with picture 1 2. and i don't know the means about the value 10000,10000000000, this is from the example code. i want to calculate the frequence about the input signal. i need the max value of the timer...

i have saw that the mcpwm module can't perceive the DFS.
i need to call the function of esp_pm_lock_acquire(ESP_PM_APB_FREQ_MAX) when i use the mcpwm module, and need to call the function of esp_pm_lock_release(ESP_PM_APB_FREQ_MAX) when i stop the pwm.
is it right?

thanks for your comments. is it means that i can't enable the PM if i want to use the mcpwm module? or i can sellect the other clock for the mcpwm module? is there any way for us to don't modify the congfiguration and let the mcpwm module work fine. our product use the ESP32-WROVER-E module, and thi...

maybe i have found the reason.
for the same environment, the same code, the same idf version, if i enable the PM CONFIG the board will work wrong.

such like the picture, the left can work correctly and the right can't.
i want to know why the PM module can cause the issue.

this is our project's sdkconfig file, and i don't know what the config can cause this issue. # # Automatically generated file. DO NOT EDIT. # Espressif IoT Development Framework (ESP-IDF) Project Configuration # CONFIG_IDF_TARGET_ESP32=y CONFIG_IDF_TARGET="esp32" CONFIG_IDF_FIRMWARE_CHIP_ID=0x0000 #...

the pwm module can't work correctly with our project, but this demo can be run with default sdkconfig.
so, i think is there anything wrong with our configuration.