Skip to content
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

Closed
3 tasks done
gabrielgvicente opened this issue Mar 31, 2024 · 3 comments
Closed
3 tasks done

RMT receive filter issue (IDFGH-12500) #13510

gabrielgvicente opened this issue Mar 31, 2024 · 3 comments
Assignees
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Type: Bug bugs in IDF

Comments

@gabrielgvicente
Copy link

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

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_receive_config_t receive_config = {
.signal_range_min_ns = 250000,
.signal_range_max_ns = 1250000

};
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

@gabrielgvicente gabrielgvicente added the Type: Bug bugs in IDF label Mar 31, 2024
@espressif-bot espressif-bot added the Status: Opened Issue is new label Mar 31, 2024
@github-actions github-actions bot changed the title Driver RMT Driver RMT (IDFGH-12500) Mar 31, 2024
@suda-morris
Copy link
Collaborator

@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.

@suda-morris suda-morris changed the title Driver RMT (IDFGH-12500) RMT receive filter issue (IDFGH-12500) Apr 1, 2024
@gabrielgvicente
Copy link
Author

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

@espressif-bot espressif-bot added Status: In Progress Work is in progress and removed Status: Opened Issue is new labels Apr 2, 2024
@espressif-bot espressif-bot added Status: Reviewing Issue is being reviewed Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: In Progress Work is in progress Status: Reviewing Issue is being reviewed labels Apr 3, 2024
espressif-bot pushed a commit that referenced this issue Apr 9, 2024
is always APB, independent to the channel clock selection

Closes #13510
@gabrielgvicente
Copy link
Author

Even so, the maximum filter I can apply will be 3uS?

espressif-bot pushed a commit that referenced this issue Apr 17, 2024
is always APB, independent to the channel clock selection

Closes #13510
espressif-bot pushed a commit that referenced this issue May 11, 2024
is always APB, independent to the channel clock selection

Closes #13510
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Type: Bug bugs in IDF
Projects
None yet
Development

No branches or pull requests

3 participants