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

ESP32-S2 RMT driver bug (IDFGH-6725) #8354

Closed
naffej opened this issue Feb 5, 2022 · 0 comments
Closed

ESP32-S2 RMT driver bug (IDFGH-6725) #8354

naffej opened this issue Feb 5, 2022 · 0 comments
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally

Comments

@naffej
Copy link

naffej commented Feb 5, 2022

Environment

  • Module or chip used: ESP32-S2
  • IDF version: from v4.3

Problem Description

#define SOC_RMT_SUPPORT_RX_PINGPONG (1) /*!< Support Ping-Pong mode on RX path */

The file above has a wrong define. According to esp32-s2 technical reference manual, esp32-s2 doesn't have RMT RX wrap mode aka Ping-Pong mode. So this define triggers false behavior when receiving with RMT. If I manually unset the define, receiving works as intended.

And

According to the formers, the following function in

static inline void rmt_ll_rx_enable_pingpong(rmt_dev_t *dev, uint32_t channel, bool enable)

static inline void rmt_ll_rx_enable_pingpong(rmt_dev_t *dev, uint32_t channel, bool enable)
{
    dev->conf_ch[channel].conf1.chk_rx_carrier_en = enable;
}

has no sense in esp32-s2. In fact it enables a complete wrong register value.

@naffej naffej changed the title RMT driver bug ESP32-S2 RMT driver bug Feb 5, 2022
@espressif-bot espressif-bot added the Status: Opened Issue is new label Feb 5, 2022
@github-actions github-actions bot changed the title ESP32-S2 RMT driver bug ESP32-S2 RMT driver bug (IDFGH-6725) Feb 5, 2022
@espressif-bot espressif-bot added Status: In Progress Work is in progress Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: Opened Issue is new Status: In Progress Work is in progress Resolution: NA Issue resolution is unavailable labels Feb 8, 2022
espressif-bot pushed a commit that referenced this issue Feb 10, 2022
espressif-bot pushed a commit that referenced this issue Feb 11, 2022
espressif-bot pushed a commit that referenced this issue Feb 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally
Projects
None yet
Development

No branches or pull requests

2 participants