-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RMT receive filter issue (IDFGH-12500) #13510
Comments
@gabrielgvicente Thanks for the report, I can confirm the issue. 🐛 For now, I would suspect the hardware maybe still using the APB (which is 80MHz) as the clock source for doing the filter, thus even you set 250us, the real bound may be 250/80 = 3.125 us, it only filter out 3us pulses... We will need some time to get some feedback from the digital team. |
Hello Suda-Morris, thank you for your reply, I will wait for the team's response. This filter is very important for the functioning of my application |
is always APB, independent to the channel clock selection Closes #13510
Even so, the maximum filter I can apply will be 3uS? |
is always APB, independent to the channel clock selection Closes #13510
is always APB, independent to the channel clock selection Closes #13510
Answers checklist.
IDF version.
ESP-IDF v5.1.2-dirty
Espressif SoC revision.
ESP32-WROOM-32E
Operating System used.
macOS
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
Personalized board
Power Supply used.
External 3.3V
What is the expected behavior?
I need to read a remote control and obtain signals above 250us.
What is the actual behavior?
but I am not successful when applying the RMT receiver filter, I receive signals below 50uS.
Steps to reproduce.
};
rmt_rx_channel_config_t rx_channel_cfg = {
// .clk_src = RMT_CLK_SRC_DEFAULT,
.clk_src = RMT_CLK_SRC_REF_TICK,
.resolution_hz = 1000000,
.mem_block_symbols = 64,
.gpio_num = rf_pin,
.flags.invert_in = true,
.flags.with_dma = false,
};
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: