ESP-IDF 6.0 compatibility: legacy RMT driver removed

[swoboda1337]

Description

NeoPixelBus fails to compile on ESP-IDF 6.0 because driver/rmt.h (the legacy RMT driver) has been removed.

NeoEsp32RmtMethod.h:49:10: fatal error: driver/rmt.h: No such file or directory
   49 | #include <driver/rmt.h>

Background

In ESP-IDF 6.0, the legacy RMT driver (driver/rmt.h) was removed entirely. The replacement is the new RMT driver introduced in IDF 5.0:

• driver/rmt_tx.h — transmit channel
• driver/rmt_encoder.h — encoding
• driver/rmt_types.h — common types

The ESP-IDF RMT migration guide describes the API changes.

Affected file

src/internal/methods/NeoEsp32RmtMethod.h / .cpp

Environment

• ESP-IDF 6.0.0-rc1
• NeoPixelBus 2.7.3 and 2.8.4
• ESP32 targets

[swoboda1337]

I know there is a core3 branch but nothing has happened with that in long time. NeoPixelBus will no longer be usable once IDF 6/Arduino 4 is out.

[blazoncek]

Instead of complaining one should provide a patch/PR with a fix and not wait for @Makuna. It will take enough of his time to review and test changes.

Do not forget NeoPixelBus supports platforms other than ESP and if Espressif is constantly changing API then it may not be feasible for a (one man) library to support that (unless users start contributing back to library).

[swoboda1337]

The core3 branch has existed for a very long time. It needs to get merged. Not sure what PR would be helpful.

[blazoncek]

You can PR to core3 branch.

[swoboda1337]

I can open a PR to merge CORE3 into master but that doesnt seem like it would save anyone that much time.

[blazoncek]

You are missing the point.
PR proposed changes to core3 branch and then use core3 branch after your changes are merged.

[swoboda1337]

What changes? Just need CORE3 merged.

[blazoncek]

core3 will be merged once it is ready (and also compatible with previous Arduino cores if possible).
Use it as is and report any bug found. If you don't know how to use core3 branch in your projects, please consult your IDE documentation.