-
Notifications
You must be signed in to change notification settings - Fork 274
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 - added the ability to use extended RMT memory for a channel #3182
Comments
For which chip? |
The technical manual referenced was for ESP32 but all devices support this option. Here is a summary ESP32
ESP32-S2
ESP32-S3
ESP32-C2, ESP32-C3, ESP32-C6, ESP32-H2 (not 100% sure on C2)
|
@Dominaezzz Are you looking at implementing this feature? |
Nope! |
OK I think I will try to implement. |
I am getting close to submitting a PR. But I have a git question that I hope someone will answer.
|
You can (Git/GitHub will allow you) but imo you shouldn't, makes it harder to review. |
OK, I think I will wait a couple of days in hopes the RMT filter threshold fix PR will get pulled in. |
I have made changes to rmt.rs to implement the ability to use extended RMT memory. I have tested TX and RX on programs that I have written for ESP32 and ESP32S3 since I have these two boards. Now I would like to test for for the other boards. After looking at CONTRIBUTING.md I am still confused at how to run the xtask and HIL to just run test for rmt examples and HIL tests for only RMT and to run tests for ESP32S2, ESP32C2, ESP32C3, ESP32C6. Can some show me how to do this? Once I run these tests I will be able to submit PR. Will the PR I submit to resolve the issue I opened also resolve PR #3052? For the PR I submit I was going to use the following commit statement " Resolve #3182 extend RMT memory". Is this OK and the correct way to submit the PR? |
OK solved with help from esp-rs/element
|
Motivations
I would like to use all the RMT memory available for one channel.
Solution
See page 414 of the Technical Reference Manual
Alternatives
None
Additional context
The text was updated successfully, but these errors were encountered: