ESP-IDF 6 compatibility issues

[Maurizio1]

I'm encountering some compatibility issues while compiling with ESP-IDF 6.0.x a project that works correctly with ESP-IDF version 5.5.x.
AI agent Claude Sonnet 4.6, in order to solve the issues, suggests to modify some M5Unified source files which is not something wise to do (mine is a professional project).

I'm working on a Tab5 device (revision 1.0.0).
Specifically, the compatibility issues I’m currently trying to resolve regards managing the ESP32C6 coprocessor for Wi-Fi in light of the new approach adopted in ESP-IDF 6 for managing I2C channels, etc.

• Is there a scheduled release date for a next version of the library that will be fully compatible with ESP-IDF 6?
• Any other suggestions?

Thanks in advance,

Maurizio

[robertlipe]

Bump. IDF warnings are getting louder that it's time to leave the IDF4-era driver model behind:

espressif/v6.0.2/esp-idf/components/driver/i2c/include/driver/i2c.h:29:103: note: '#pragma message:
================================ CRITICAL WARNING ================================
This legacy I2C driver (driver/i2c.h) is officially END-OF-LIFE (EOL) as of ESP-IDF v6.0.

1. NO SUPPORT: ESP-IDF will not provide updates, bug fixes, or security patches timely.

2. PLANNED REMOVAL: This driver WILL BE REMOVED in ESP-IDF v7.0 (next major release).

3. ACTION REQUIRED: Migrate to 'driver/i2c_master.h' or 'driver/i2c_slave.h' immediately.

   • If you are a library maintainer, please update your code.
   • If you are using 3rd-party libraries, contact the authors for updates.

4. SUPPRESS WARNING: Set Kconfig 'CONFIG_I2C_SUPPRESS_DEPRECATE_WARN=y' to silent
   this warning. However, by doing so, YOU ASSUME ALL RISKS including potential
   security vulnerabilities, system instability, and future incompatibility.

For API reference of the new I2C driver, see: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/i2c.html
For other items about migration, see: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/migration-guides/index.html

There's another similar complaint in the rtc driver.

The speaker driver goes splat here:

.../esp_driver_i2s/include/driver/i2s_types.h:18:29: error: expected unqualified-id before numeric constant
18 | #define I2S_NUM_0 0 /*!< I2S controller port 0 */
| ^
.../m5stack__m5unified/src/utility/../utility/Speaker_Class.hpp:79:39: note: in expansion of macro 'I2S_NUM_0'
79 | i2s_port_t i2s_port = i2s_port_t::I2S_NUM_0;
| ^~~~~~~~~
In file included from .../m5stack__m5unified/src/utility/../M5Unified.hpp:63:
.../m5stack__m5unified/src/utility/../utility/Mic_Class.hpp:95:27: error: 'i2s_port_t' is not a class, namespace, or enumeration
95 | i2s_port_t i2s_port = i2s_port_t::I2S_NUM_0;
| ^~~~~~~~~~

I tried to shim that up because i don't really even care about the speaker but then I run into issues with RMT

.../led/LED_Strip_Class.hpp:27:11: fatal error: driver/rmt_types.h: No such file or directory
27 | #include <driver/rmt_types.h>
| ^~~~~~~~~~~~~~~~~~~~
compilation terminated.

This stuff was all deprecated a year ago or more. The needed changes are pretty mechanical:

https://docs.espressif.com/projects/esp-idf/en/latest/esp32s31/migration-guides/index.html

I've just pinned my M5Tab builds to IDF5, which still has the IDF4 compatibility layer, but even if you turn on the "SHUT_UP_ABOUT_I2C_AND_GIVE_ME_THE_OLD_ONE_ALREADY" define, that's not enough because drivers beyond I2C changed and there's not a corresponding "CHANGE_IS_BAD_GIVE_ME_THE_OLD_ONE" :-) flag for all the changed drivers. M5Unified just doesn't work with the current IDF.

Please do track current IDF releases. Thanks!