Skip to content

Commit 7bc89de

Browse files
committed
Document ESP-IDF >=5.0 support and drop v5.1 caveat
1 parent 37c3486 commit 7bc89de

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -143,9 +143,8 @@ Some NFC-A examples are shared with [M5Unit-RFID](https://github.com/m5stack/M5U
143143

144144
### For ESP-IDF settings
145145

146-
> **NOTE:** The library itself works with ESP-IDF **5.x** (>=5.0).
147-
> The provided examples additionally pull in `M5Unified` / `M5GFX` for display output, which depend on the `esp_mm` component introduced in v5.1 — so **building the examples requires ESP-IDF >=5.1**.
148-
> `M5Unified` / `M5GFX` do not yet support ESP-IDF 6.x; stay on the latest 5.x release until upstream support lands. If you don't need M5GFX, the library can be consumed on v5.0.x in your own project.
146+
> **NOTE:** The library and examples target ESP-IDF **5.x** (>=5.0).
147+
> `M5Unified` / `M5GFX` do not yet support ESP-IDF 6.x; stay on the latest 5.x release until upstream support lands.
149148
150149
On ESP-IDF native builds (`idf.py`), the unit/board is selected via Kconfig instead of editing the source `#define`. Each example exposes the same choice through `main/Kconfig.projbuild`, which sources one of the family-specific Kconfig files in `examples/UnitUnified/common/`:
151150

0 commit comments

Comments
 (0)